Guild Wars 2

Toker and I have been trying to duo queue for unranked for 10 minutes now. As soon as the last person accepts the queue invitation, it abandons us.

This has happened over 5 times in the last week. You just have to say: “Okay. ” and do something else.

I don’t see a lot of complaints about this issue, post here if this is affecting you as well, and perhaps some kind of reasoning as to why this is happening can be discovered.

this has happend to me a few times aswell, relogging worked for me. give it a try if you havent.

It has not happened for that long, but once or twice a night for me it does this. I have also seen it do this when the ready box comes up, my whole team excepts, a couple of the opposing team do not and it abandons. We are on coms and can guarantee we all accepted.

Yeah this has happened a lot of for me and my friends too. I’ve spent 10-15 mins of changing characters, maps, logging in and out (the other party members doing the same), just to attempt to queue with my party. Then sometimes 5-10 mins later you’ll get a queue pop and you won’t even be in the same match as your party.

At least with the old roster system you could generally know what the status of your queue was and which of your party members had accepted. But somehow the removal of the roster was touted as a ‘feature’?

Realistically, have the December updates done anything positive for PvP? (Major tournaments aside…which are independent of all of this)

Anet doesn’t have a ladder system so they implemented a temporary way to stop top tier players from absolutely crushing little plebs!

Wahoo! Bye frands!

Celtus.8456:

Then sometimes 5-10 mins later you’ll get a queue pop and you won’t even be in the same match as your party.

YES. Then after this forced abandoning of the queue happens, one person in the party gets a match even though they weren’t in the queue. And they usually accept, not knowing the rest of the party isn’t with them, and the group is further divided.

Chaith.8256:

Celtus.8456:

Then sometimes 5-10 mins later you’ll get a queue pop and you won’t even be in the same match as your party.

YES. Then after this forced abandoning of the queue happens, one person in the party gets a match even though they weren’t in the queue. And they usually accept, not knowing the rest of the party isn’t with them, and the group is further divided.

The last time I logged on Guild Warts 2, 10 seconds after the HotM loading screen it put me into a match when I didn’t even queue! Maybe these issues are related!

Wahoo! Bye frands!

Chaith.8256:

Celtus.8456:

Then sometimes 5-10 mins later you’ll get a queue pop and you won’t even be in the same match as your party.

YES. Then after this forced abandoning of the queue happens, one person in the party gets a match even though they weren’t in the queue. And they usually accept, not knowing the rest of the party isn’t with them, and the group is further divided.

Yep, that happened too. 2 out of 3 of us went into match and the 3rd player got a Q pop 30 seconds later and went into a different one.

i queued for ranked. then i left the queue to go do some bank rearranging. after 2 minutes being NOT queued I got a ranked match pop. i played and won so I ain’t mad yet haha but still, I can confirm this is happening.

ive seen this happen. i think it stems from the broken leave queue function in that the system pukes when it thinks someone in the party is already in queue and you try to enter queue. relogging (alt-f4, not char select) may fix if matchmaking hard kills your queue request on disconnect. disbanding the party, leaving queue, and waiting for a q pop and cancelling should also work but prolly will take longer and be unreliableish.

Happens sometimes. Sometimes it doesn’t.

How it happened for me and a guildie today. He was solo queue-ing, I joined his party and he left queue. We reentered queue, and the game gave me some “can’t join queue” message (I don’t remember the exact words). Then he got a pop up and joined a match, solo, with me still in party. After that match queue-ing worked perfectly fine.