-
Notifications
You must be signed in to change notification settings - Fork 37
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
Bug: Wrong dungeon type 0 for dungeon 0 #39
Comments
407538200_7016151298444734_1094486024455989933_n.mp4A player on our server sent this recording of the issue happening on their end. |
Same issue found today, AzerothCore rev. 38fc22da375a+ 2023-12-23 09:34:08 +0700 (npcbots_3.3.5 branch) This happen on one character, but not problem to LFG with others. Is there a workaround on the database ? |
I had the same issue except mine was while in a party with bots. A temporary fix for me: Leave the party you are in with bots then re-group with them |
Does the error occur when, while inside a dungeon, you want to score another one? |
Hi, having same issue here. I started server fresh, my character was outside of a dungeon, but my character was in a group with bots already. I tried to physicly enter the dungeon when i got this error. Then i tried to launch LFG but to no avail either. Then i ungrouped myself from my bots, then regrouped - still got error (on both cases - lfg and physicly entering dungeon). Even if i ungroup myself and try to get to dungeon solo i still get error.
Versions: |
Current Behaviour
After using the Dungeon Finder tool, subsequent dungeons result in the error "Wrong dungeon type 0 for dungeon 0" in the worldserver console. Will also see something similar to "LFGQueue::AddToQueue: Queue data not found for [GUID Full: 0x1f5000000000000b Type: Group Low: 11]" pop up in the worldserver console.
Expected Behaviour
Subsequent queues should allow player to queue with less than 5 players. This feature was previously working, but after updating AzerothCore with the most recent updates on 12/3, the LFG tool has been generating these errors.
Steps to reproduce the problem
Extra Notes
Restarting the worldserver fixes the issue, but it is unrealistic to do this every time it happens, especially on a server with other players playing.
AC rev. hash/commit
azerothcore/azerothcore-wotlk@eb1ecc38a5a3
Operating system
Windows Server 2022 Standard
Custom changes or Modules
The text was updated successfully, but these errors were encountered: