Status shows in "CO-OP Queue" when probably not

BUG: Status shows in "CO-OP Queue" when probably not

Probably not because:

• I waited 10 minutes;
  
• Somebodyelse said was in queue & cooperative did not start (it would start immediatly for Somebodyelse if I was really in queue);
  
• I restarted game, got in queue again & instant start with Somebodyelse;
  
• The 'instant start' is good evidence that I was not in queue earlier & no-one else was either; that I had to restart to get in queue & start game with Somebodyelse
  

I've had the same thing happen to me before when I went afk from battles for a really long time and then i tried doing a coop and when i asked one of my guild mates to fight with me, he said that no one else was in queue so I had to refresh the client in order for the game to see me and find a match. This was a while ago so I don't remember full details

This bug has also happened to me, though I have no clue what the cause is. I think I just left queue and reentered and it worked though. But at one point I was in queue for some time while it said "1" without getting a match until I left and reentered queue.

Greetings all,

Venumuse's post may indicate a connection issue with the battle server. Has anyone maybe tried to enter a solo battle after failing to get matched in coop?

Xargos wrote:

Greetings all,

Venumuse's post may indicate a connection issue with the battle server. Has anyone maybe tried to enter a solo battle after failing to get matched in coop?

Yes, this was working for me.

Without a refresh, 9999?

Xargos wrote:

Without a refresh, 9999?

Yes.

I apologize for lots of split questions, 9999.

Had you also been in the queue for over 5 minutes, seeing that one person is in the coop queue, while others would see zero?
And after failing to match up, without a refresh, you tried to do a solo battle and it worked?

This is rather weird since every time a players joins a queue, the count is updated.   

A side note: There is a case when a person cannot see another person in queue when they are under a war treaty.

Xargos

Xargos wrote:

I apologize for lots of split questions, 9999.

Had you also been in the queue for over 5 minutes, seeing that one person is in the coop queue, while others would see zero?
And after failing to match up, without a refresh, you tried to do a solo battle and it worked?

This is rather weird since every time a players joins a queue, the count is updated.   

A side note: There is a case when a person cannot see another person in queue when they are under a war treaty.

Xargos

The last days it happens several times.
1. I go in queue -> 2. another player joins (counter to 1) -> 3. nothing happens -> 4. a second player joins (counter to 2) -> 5. they match -> 6. i am still in queue -> [points 2-6 repeat several times] -> 7. i have enough -> 8. quit queue -> 9. making solo without refresh

Ok, many thanks for your information.

I'll take a look at it,
Xargos

I think this is currently the second most annoying bug (after the temporarily invisible army banners)

I have to frequently restart the game, to  be sure I am in the cooperative queue properly.

Related to this:

• It often shows '0' people in cooperative queue, when you are in it.
  

Pearl wrote:

Related to this:

• It often shows '0' people in cooperative queue, when you are in it.
  

You don't see yourself in the queue

lightshield wrote:

You don't see yourself in the queue

Yes, see above example.

---

History:

• It used to always show you in the queue - and there was no problem matching.
  
• Then this bug appeared on October 10th, 2013: Coop queue not showing "1" when I am in queue;
  
• Its quite common to see a '0' while you are in the queue now.
  
• Sometimes, it will match you up (after a normal wait of 0 to a few minutes);
  
• Sometimes (as per above) its is bugged - and will never match you up - you need to restart the game (we know this for a fact, as when this happens, other people talk & say they are in queue & then they said they did a cooperative, and also you can see the number go from 0, 1, 2 & then back to 0, as it picks two others).
  
• This latest bug started appearing on December 29th, 2013 (as per the bug report).
  

No idea if the two bugs are related ... I only mentioned it as they might be.