Can you post some client logs. Also, did you ever set Tcpfallback=true in pirates_local.ini?

We've spent a lot of time thinking about and discussing this issue over the last couple of days. I wanted to stop by and bring you up to date on our plans:

Our ultimate solution to Attack Target is to teach our AIs to spread themselves out a bit more realistically between multiple targets. So when an AI is deciding what target to attack, he will consider how many attackers are already engaged with the target, and prefer to attack targets with less attackers. Doing this is a non-trivial amount of code work. It’s something we are doing, and soon, but it’s not something we can do Now. Our interim solution is to disallow Attack Target on other players. So, in the short term we will make it impossible to use the Attack Target skill on another player, and in the long term we will make AIs spread themselves among multiple targets more evenly. When we do the latter, we will rescind the former.

Having attack target only effect a limited number of allies in range is another option, but it's about the same amount of work as teaching our AIs to spread themselves out more naturally. We may do both eventually.

That's a bug. I'll try to get it fixed in v1.1, but depending on where we are in the process, it might slip to v1.2.

That's the requirement: A Dev sees and approves your flag/sail for the game. Ratings only help prioritize what devs look at first.

You can always, always post a preview before submitting in this forum That's the best way to get started making good (and technically acceptable) flags and sails.

To let people know you have something ready to vote on (once you're happy that it meets the guidelines), you can post in the Flag and Sail Votes! sticky. That's what it's there for. You can also add links in your signature, provided you stay within the 3-line limit (at normal font sizes).

Please file a support ticket.

If isildur ever smiles, I expect to see 4 horsemen heading toward the lab.

We're working on an official policy to share publicly, but this is indeed not welcome behavior. Please report it directly to the 2D Steering Committee for now (Emwsand, Sadet, Toshiro, or myself). Include direct links to any affected submissions.

Some fine designs, but you'll need to keep the following points in mind:

* You'll want to avoid pure, fully saturated colors. Pure black isn't possible to achieve in nature Try a black around RGB 50, 40, 30 instead.

* For the sail, you'll need to remove the textures and use a transparent background instead. Decals and sails can be colored separately in-game. If your design covers about 50% of the sail or more, you'll also want to make it partly transparent, e.g. with an opacity betweeo 50-70%, so some of the underlying sail texture shows through.

* Text on flags is perfectly fine, though as noted, it will always appear backwards half the time, no matter what you do.

Looking forward to your next revisions

We are still trying to fix this internally. It does seem to correlate to your desktop reolution and your antialias settings. In our internal tests, we've found that lowering your anti-aliasing settings in the NVidia control panel (to 4x or less) seems to correct it. To do this, right click on your desktop, open up the NVidia Control panel, change your 'Antialiasing-Mode' to 'override application', and set 'Antialiasing - Setting' to '2x' or '4x' or 'off'. We have people here and at NVidia frantically trying to get a fix to you, but if you could try changing your antialias settings in the meantime, and report back, we'd be eternally grateful.

Have you tried overriding the application settings in the NVidia control panel? That has worked for us internally, but it'd be good to confirm from outside as well. We set ours down to '4x' '2x' or even 'off'.