ArenaNet Explains What Goes Wrong in Guild Wars 2 WvW Restructuring Beta, Sets New Dates
When ArenaNet launched the first beta of Guild Wars 2WvW’s overhaul, the event was halted after just two hours. Now the team has released a postmortem on what went wrong and what will follow for the WvW.
Although it only lasts two hours, the beta gave the team some data to work with, so there are at least a few bright spots. Major issues started showing up almost immediately right after the Friday reset and the initial opening of the WvW Beta on September 24. They began to see reports of players paired with completely bogus teams. Since the usual server reset time kicks everyone and starts again, this theoretically should have been the clean slate that a beta needed. However, some players had incorrect partition data remaining when they logged in, and the client was using this data to try to join, thus sending them to the wrong place. This, however, was only the first problem.
Then they noticed that the demand on their server was increasing due to the duplicate Edge of the Mists instances, taking up about 30 times the normal resources. a mistake. The log server in question is also part of the Guild Wars 2 overall so they have ended the beta.
ArenaNet has identified 10 bugs that need to be fixed before the next beta can take place. Although there were also some positives. The WvW restructuring technology has worked on a large scale, so that was a good sign. The new matchmaking algorithm has also grouped players in a balanced way.
With all of that, they are planning a new beta week that will begin on November 12. For the full update, with all the details that went wrong and their work to fix it, read it here at Guild Wars 2 to place.