-
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: Getting stuck in a group. #40
Comments
Not stuck for good though. You can use command |
Works a few times then, Internal LFG Error. |
I can confirm this is the same issue I am experiencing. |
This does not work for me. We were able to correct the issue without a server reset using the following steps: .gm on The affected player(s) had to relog for the clear to take effect. The LFG option does work for 1-2 dungeons before bugging. So, I'm wondering if the fix could be to implement some sort of a timer that would clear queues after a certain period of time? |
I wrote a Windows PowerShell script that runs in the background that will automatically clear the LFG queue every 15 minutes as a temporary fix. Attached is my code if you'd like to try implementing. |
The first random dungeon can be entered correctly, but there is no reward after beating the boss. |
Is that topic still valid? The problem is that if we eliminate the group, you would lose the progress, in case you have to leave the dungeon for some reason. I suppose that for that reason, the group is preserved. Otherwise, when you leave, you would not be able to enter again. In fact, in case of death, I don't remember what happens, I think the group is eliminated. |
It is still valid yes |
Current Behaviour
When you join a LFG solo and use port out, char get stuck been in a group. Server need a restart to fix it.
Expected Behaviour
Should not be in a group if you use port out.
Steps to reproduce the problem
Join a LFG solo and use port out.
Extra Notes
No response
AC rev. hash/commit
azerothcore/azerothcore-wotlk@f46cf867ad10
Operating system
Debain 12
Custom changes or Modules
The text was updated successfully, but these errors were encountered: