Answer 211 assumes that Packeteer is the source of your connection issues. Living in a res hall makes that very likely. I recommend that you send your IT staff an email to politely and cheerfully verify that your school uses Packeteer, and provide them the instructions from Answer 211. You can tell them that this is a manual solution that will eventually be made official and pushed out by Packeteer. They can contact us to confirm.

Definitely file a support request explaining the situation. At this point in time I can't guarantee that we'll be able to extend your subscription. But I agree that it's unfair for you to pay for a service that you can't use.

Check the original post in this thread for a work around that has proven fruitful for the folks who have used it. Let us know how it works for you!

Best,
Aether

1.2.x should arrive in March, I think. The next 1.1.x patch is hitting Testbed very soon, I believe. Should go live early next week.

It's free. Think of it as a toy that extends the playstyle of the Dromedary. It's supposed to be worse than the player-crafted ships at the same level.

With over 80 ports and a town taking the entire environment team and some of ConCo for a month or two, we'd have never shipped.

LOL! But mimes don't talk. That's the joy of 'em.

We continue to investigate the lag issue as reported by our customers. At this point it appears to be a problem for Vista users, though we are confident that we are closing in on a resolution to the problem.

If you are experiencing lag issues, you are invited to share additional information in this thread. We will continue to share updates throughout the evening.

We thank you for patience as we work to remedy this situation, and we apologize for the inconvenience.

Best,
Aether

It works fine. The target isn't in your firing arcs and the requirement displayed is relative to the guns you have facing the target. In this case, that would be the swivels - which aren't loaded with dismantling shot.

Besides, it'd say the target's immune instead of wrong ammo type if there was anything career-specific.

Nope, just an oversight. Fixed!

That, and the huge disparity between the OS and the battle. At first glance, it makes sense to attempt to have the battles mirror the OS. However, it completely breaks when you have such as huge disparity in time and travel distance. What it means is that a battle effectively starts the second one side engages, but the team that abuses the OS wins. During that first 60 seconds of the battle, it's like having a warp drive and being able to position yourself perfectly for the battle. It creates a situation where you either abuse the spawns or you lose.

The new system assumes you are traveling as a convoy. If you're sailing out in the ocean and spot hostile ships, they're generally going to be in their own convoy. You're not going to suddenly spot then coming from four different directions towards your location. Neither can you order your own ships to appear behind the enemy. It's a spatial impossibility, but one that the current system allows. If I get attacked and my group joins in, then (according to the game rules) they are playing the game wrong. If they spend a few more seconds moving on the open sea, they can cut out minutes of travel in the battle. They can guarantee themselves a position that makes it impossible for anyone to escape. That's just not right.

Transferring all the angles adds some strategy, but it does so in a way that leads to degenerate gameplay. It creates situations where groups that are sailing together get spread all over the instance, and enemies can spawn ships right on top of you. We do not want the spawn system to determine the outcome of the fight. Right now, a good group that abuses the spawn system should always beat a good group that doesn't use the same tactics.

I expected negative reactions to the removal of angle for reinforcements, but there are two unacceptable flaws: 1) It does not work with the scale of the open sea, 2) it's a giant exploit.