Guild Wars: 2 WvW Queue Is Having “Timeout” Changes
For now, these changes shouldn't affect a players wait time while in a queue.
Some new changes are arriving to Guild Wars: 2 World versus World. Starting tomorrow, June 2, as a part of an ongoing investigation with the WvW queue bug, some numbers will be changed regarding queue times.
As of right now, the issue plaguing players is that when players reach the end of the queue, the system attempts to move a player’s character to the WvW map. During that time there is a 60 second "timeout" window to allow for transferring and load times. Starting this week, that time will be increased to 90 seconds. The reason behind the extra 30 seconds will be in order to allow more data to be gathered regarding the queue bug which sometimes causes players to be reset to the back of the queue after reaching the first spot and have to wait all over again.
Currently, the plan is to increase the value to 120 seconds the following week, provided that no problems arise from the change to 90 seconds. These changes will possibly result in longer queue times than normal, but the team says that seems unlikely at these early stages.
Related Articles
- Get A Look At Blade & Soul NEO's Plans Through Summer, Starting With A Moonwater Plains Update Next Week
- The Next New Map Arrives In Guild Wars 2 Next Week As Just One Part Of The MMO's "Repentance" Update
- Deep Dive Into Throne And Liberty's Telandre Expansion In What Is Probably One Of Their Best-Formatted Videos
About the Author

Aspen is an avid gamer and Twitch streamer currently residing in Japan. She is most attracted to games narrative design and is a huge fan of player choice in games. If Aspen is not playing games, she is most certainly writing about them.
More Stories by Aspen PashRead Next

It won’t be much longer now.
You May Enjoy

The PoE2 laptop prize look pretty snazzy.

However, the game is Web3-based.

The ranged magic user has a very cool look and can ward of death.

There’s also an AI chatbot and the workbench is being updated.
Discussion (0)