• Latest Updated Guilds
  •  
Recruitment
RSS Feed
Source [BUG] Randomly queueing to a saved dungeon

Consume		It is possible to be randomly queued for a 5 player dungeon you are already saved/locked to for that day.

I was locked to a Forge of Souls instance from a few hours earlier, and then randomly got into a group for it later. I was able to proceed with the instance just fine, everything was alive on a new, separate instance ID.

At the first boss we wiped and the tank dropped and was vote-kicked, When trying to queue for a new tank the leader got a message saying one or more players is not eligible for this instance (because I was technically locked to a previous instance).

Obviously it shouldn't be possible to run the same dungeon twice per day. I don't know for sure if this is a legit bug or a special paramter for testing or even intended.

Occured on build 10772.
Dresorull
Blue Poster




    

 Source
# 4 - November 6, 2009, 7:17 pm
When you queue for a random dungeon, it will effectively ignore your lockouts for that random selection. If you are locked to an instance though, you still cannot manually go to or queue for that specific dungeon alone.
Dresorull
Blizzard QA
Dresorull
Blue Poster




    

 Source
# 10 - November 6, 2009, 9:55 pm
Q u o t e:


The second part of his feedback seems crucial

Q u o t e:
When trying to queue for a new tank the leader got a message saying one or more players is not eligible for this instance (because I was technically locked to a previous instance).


That seems like a problem, especially in situations when someone leaves, etc. If the system is going to ignore it when it selects you for a random dungeon, it should ignore this fact when looking for new players.

Unless it was just the error message that was given, and they could find someone else just fine. I probably misread it. Either way, it just seems odd.


I reread the original post, and want to clarify a bit. The portion that you've singled out would be considered a bug. We've made some changes to the system, and they should be in the next build that goes to the PTR. If you could watch for these sort of errors again, and make sure to get a screenshot showing the error it would be very helpful.

Thanks for the reports.
Dresorull
Blizzard QA