Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dungeon Browser Queue sorting issue #5825

Open
balleny opened this issue Jun 23, 2023 · 2 comments
Open

Dungeon Browser Queue sorting issue #5825

balleny opened this issue Jun 23, 2023 · 2 comments
Labels
Needs Triage Needs to be checked by a contributor.

Comments

@balleny
Copy link

balleny commented Jun 23, 2023

What client do you play on?

enUS

Faction

Both

Content Phase:

Generic

Current Behaviour

  1. 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.

  1. 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

  1. when an attempt to create a group fails, you should be moved back to your original position instead of being moved down the waitlist.

  2. 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

@github-actions github-actions bot added the Needs Triage Needs to be checked by a contributor. label Jun 23, 2023
@Wosser
Copy link

Wosser commented Aug 17, 2023

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.

@emuduck
Copy link

emuduck commented Dec 9, 2023

bump. on a low pop server an insanly annoying bug that deserves some prio.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Triage Needs to be checked by a contributor.
Projects
None yet
Development

No branches or pull requests

3 participants