Release Notes - December 14, 2011

[Captain Del]

Originally Posted by leo

I said i wont judge the update to early and i think this is the best addition to the game yet. My point was, in the last test release notes there were knows issues meaning that they are not fixed yet but being worked on, Why add the known issues to the game? there were still possible fixes on test. There was still room for fixes on test and the ones above did not just come up right now because they were known issues on test. Considering that the game is closed, they might be working on them but why not finish it on test where you have more time and a better chance for perfection. I am pro fixes even if it takes a week of no game as long as the job is done. Again, time will tell how good the end product is.

I understand that this has been on test longer than any other content. But once a job is started, why not finish it?... Pirates did grow impatient but no reason to rush it when the chance of the content going to live is 100%. Those who played the game since it's release, hardly waited for this the entire time and until 4 months ago, it was still just a rumor. After 4 years, anything should be done right considering the potential, size of content, and the desire for it are so great. A lot of players did help on test, to come to disappointing result due to a early release, would not be so great news.

Human nature, I know. The closer it gets, the more impatient every one grows. BUT stay calm Pirates, Ship Customization is here but don't interrupt them while working on it. This is the final step. Let it end in peace.

As I stated before, not every bug can be fixed on the Test server because updates tend to act differently between Open and Test. After fixing the problems that they had on Test, they moved the update to Open to see how it would react with the game so they could fix anything that was left over that went to screw around on the live servers. Just because the Known Issues were posted with the Release Notes does not mean that they neglected them on Test; rather, it was the result of the coding of the update clashing with that of the Open server, and as with every update, they could only be fixed ON the Live server.