[UPDATE 3/18] Thanks for everyone’s patience while we've investigated the issues regarding errors 0 and 31048. I know that these bugs have caused a lot of player frustration, and the process of figuring out, fixing, and testing the bugs took longer than we would ideally like to see. The multiple bugs causing Error 31048 and 0 were complex, but we have managed to zero in on what we believe will fix these issues.

With the 1.0.7a patch, we deployed a partial fix. This fix corrected a problem where some players were erroneously receiving the wrong error (0) instead of the correct error (31048). After the patch, players no longer receive Error 0 and instead receive the correct error (31048) when the bug is encountered.

We have now completed fixing and testing the rest of the issue -- the error 31048 itself -- and we are currently scheduled to deploy this fix with tomorrow morning's (3/19/13) maintenance. If you continue to experience this problem after tomorrow's maintenance, please post on the forums to let us know.

We are very sorry for the inconveniences these errors have caused and once more thank you for your continued patience and understanding.


There are active investigations as to all of the causes of these errors, and we are working as fast as we can to deduce and fix any possible causes for these errors. We're aware that a good number of posts on this forum specifically have been posted regarding these issues, but I just want to put this post up here to make sure you all know that we are looking into fixing them asap.

I cannot give specific times as to when these fixes will be implemented and/or patched/hotfixed into the game. Please do not post asking for updates on the progress of fixing this issue. I will keep you updated as often as possible as to the statuses of these issues.

Thanks everyone for the reports!
Edited by Liogela on 3/18/2013 6:06 PM PDT