Guild Wars 2

I was playing in a server borderland today, waiting to get into eternal battlegrounds. My turn in the queue came up, I hit travel and when I arrived to fight for my server I was….. dead!

I was in combat so I’m assuming it killed me via the alt+f4 fix that went in a few patches ago? I know it was intended to stop people from logging out, but was it also intended to kill people traveling in the queue?

Yes, yes, there’s a timer and I could try to finish the fight/run/get out of combat before I hit “travel”, but what’s the point of trying to do that with a huge pop-up in your face. Not sure if many people are really willing to leave or re-enter the queue after waiting for so long, so I guess the price for that is death

Yup, price is death or find a way to get out of combat before the timer expires. Your choice.

Folk.2093:

Yup, price is death or find a way to get out of combat before the timer expires. Your choice.

You’re right, I mean it’s not like the OP had a point and we could think of a cooldown system or look at adjusting the UI notification.

This issue has been raised before and if I recall correctly someone from Anet acknowledged it and said it shouldn’t work this way. Obviously they haven’t fixed it yet.

if in combat do not change maps/wp/log out … not difficult. Also as pointed out above this has all been covered in previous threads.

yeah i agree this is a little lame but its goes hand in hand with alt-f4ing therefore makes sense to me, you could be in a borderland and get a queue for another while in combat and if this wasent in place its basically the same as alt-f4ing so, just deal with it

If it didn’t behave like this, wouldn’t this just be used as another (albeit less effective) alt-f4?