You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have a dungeon group forming being cancelled or unsuccessful aborting, you receive the notification
... you have been placed at the top of the search queue
but actually, you arent placed back to your "top position" but are instead dropped further down the line.
In a similar manner, when you queue with a group that is already inside an dungeon (hence a group which already formed successful once) because you have to fill up the group again, you are supposed to be sorted on top of already waiting groups. this might be off, too - but I couldnt confirm it yet.
=> called Looking for More
Expected Blizzlike Behaviour
when an attempt to create a group fails, you should be moved back to your original position instead of being moved down the waitlist.
if you queue from an existing group, from an unfinished dungeon, you are supposed to be moved on top of the current stack. if a second group is queuing too, it would be sorted after the first group (or practically, you would have 2 separate queues (prio and regular).
dont have the right sources at hand right now - just generic ones - will add later
Steps to reproduce the problem
queue with 2 heals (= h1, h2) and 6 damage dealers (d1, d2, d3, ...).
then queue with a tank (=t1).
h1, d1, d2, d3, t1 should receive a popup. accept the queue with h1, d1, d2, t1 and then let the queue (via d3) expire.
Now, h1, d1, d2, d4, t1 should receive a popup. But, instead it seems that h2, d4, d5, d6, t1 receive the popup.
in a similar manner, successful queue and enter a dungeon with h1, d1, d2, d3, t1.
Next queue with h2, d4, d5, d6
then leave the dungeon with t1.
requeue the dungeon group consisting of h1, d1, d2, d3
now, queue with t2.
t2 should get grouped with h1, d1, d2, d3 and not with h2, d4, d5, d6
Extra Notes
this report is based on ingame experience and may contain errors. the steps to reproduce should help verifying behavior
It feels really shitty to have RDF pop after waiting for a while only for a DPS to be AFK and decline and then have the tank and/or healer be put into a different group and you have to wait again for an unknown time, being punished for someone else not accepting the queue.
What client do you play on?
enUS
Faction
Both
Content Phase:
Generic
Current Behaviour
=> called Looking for More
Expected Blizzlike Behaviour
when an attempt to create a group fails, you should be moved back to your original position instead of being moved down the waitlist.
if you queue from an existing group, from an unfinished dungeon, you are supposed to be moved on top of the current stack. if a second group is queuing too, it would be sorted after the first group (or practically, you would have 2 separate queues (prio and regular).
Source
https://wowpedia.fandom.com/wiki/Dungeon_Finder
dont have the right sources at hand right now - just generic ones - will add later
Steps to reproduce the problem
queue with 2 heals (= h1, h2) and 6 damage dealers (d1, d2, d3, ...).
then queue with a tank (=t1).
h1, d1, d2, d3, t1 should receive a popup. accept the queue with h1, d1, d2, t1 and then let the queue (via d3) expire.
Now, h1, d1, d2, d4, t1 should receive a popup. But, instead it seems that h2, d4, d5, d6, t1 receive the popup.
in a similar manner, successful queue and enter a dungeon with h1, d1, d2, d3, t1.
Next queue with h2, d4, d5, d6
then leave the dungeon with t1.
requeue the dungeon group consisting of h1, d1, d2, d3
now, queue with t2.
t2 should get grouped with h1, d1, d2, d3 and not with h2, d4, d5, d6
Extra Notes
this report is based on ingame experience and may contain errors. the steps to reproduce should help verifying behavior
AC rev. hash/commit
chromiecraft/azerothcore-wotlk@fb7164b
Operating system
Ubuntu 20.04
Modules
Customizations
None
Server
ChromieCraft
The text was updated successfully, but these errors were encountered: