Guild Wars 2

Gaile Gray.6029:

MRA.4758:

Nicca.3057:

But, the reason for it not being implemented is because it has not been tested? If I am wrong in my understanding please feel free to recalibrate my logic.

Crytal Reid stated that “the code changes were too risky to get checked in and tested properly” which means that the fix has already been implemented (most likely “locally” in a programmers development environment), but it has not been integrated in the code of the live production servers (“checked in” for the new build of today) since it has not been tested thoroughly.

Changes to a software system always bear the risk of creating unforeseen problems in other (and seemingly unrelated) components of the system. Hence, if ANet didn’t have the time to test the fix properly, then they are doing the right thing in pushing the changes back to the next release build.

~MRA

Thank you for understanding and for explaining this so clearly. This is an issue that the team actively is working on, but as Crystal explained, it will be fully addressed in a future build. We thank you for your patience while the best possible resolution is developed, tested, and then implemented into the game.

I genuinely appreciate the clarification MRA.

The point I am trying to get across here is that the responses we have been getting as a community of users are not adequate. I have been made to understand that this fix is complete and ready to publish. While the “fix” may be completed, since it is not tested it can hardly be considered a fix. A proposed fix perhaps, but as you said, unforeseen consequences may arise.

At some point, an honest straightforward answer to a legitimate question or concern would be appreciated. I have to answer similar questions and deal with these concerns on a daily basis. I personally do not say something is “ready” or “fixed” unless I am 100% sure and prepared to show it to be so.

I have no issues with allowing the team to take all the time they need to ensure this and any other matter is being handled and corrected properly, but that needs to be communicated more effectively.

Hopefully this will be resolved with the next build as Crystal has stated.

Maybe I’m confused here, but the way I read your response from Feb. 21 lead me to believe that a fix was in fact worked out, but could just not be implemented into a hotfix because it required code changes. So, today we got an actual content update, not just a hotfix, in which the fix could have/should have been implemented. Instead we are now told that the code changes were too risky to get checked in and tested. My confusion then is that I was under the impression the “bug” was fixed but required an actual content update to get it published. When I hear something is fixed I would assume that to mean the fix was already tested. But, the reason for it not being implemented is because it has not been tested? If I am wrong in my understanding please feel free to recalibrate my logic.

Have been noticing tons of server side lag here as well. Initially started during Frozen Maw right after reset. After taking a break to eat dinner my wife and I started leveling new chars in Mount Maelstrom. Not events going on, and the lag has been terrible. My wife has died from falling twice without ever actually falling at all.

Game is unplayable like this.

• Update ** Changed zones to Iron Marches and the lag still persists, so it is not zone exclusive.

I am Siobhan’s husband. I have gotten all the same copy/paste responses she did save this last “personal” response.

“Hello Nicca,

Thank you for contacting the Guild Wars 2 Support Team.

The Support Team does not have the available to grant these type of items. That is why the Developer Team is working in this situation. What we can do is provide you with information of the resolution of them.

Hoping this information was helpful, please do not hesitate on contacting us again.

Regards,

GM *******
Guild Wars 2 Support Team
http://support.guildwars2.com/"

I’m not entirely sure what I’m being told here, so I had no response.