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

Bug: Worldserver.exe crashed if the MOD is enabled #43

Open
pagimu opened this issue Jul 31, 2024 · 5 comments
Open

Bug: Worldserver.exe crashed if the MOD is enabled #43

pagimu opened this issue Jul 31, 2024 · 5 comments

Comments

@pagimu
Copy link

pagimu commented Jul 31, 2024

Current Behaviour

Worldserver.exe closed instandly if I have enabled the SOLO LFG Mod. If I disabled the mod, all works fine. My LOG shows no error message or an other info about that. I have checked with step by step activated one by one module.

Expected Behaviour

worldserver.exe have to start with activated Solo LFG Mod

Steps to reproduce the problem

start worldserver.exe with enabled MOD

Extra Notes

No response

AC rev. hash/commit

fccfe51594b4+ 2024-07-29 23:49:58 -0300 (master branch)

Operating system

Windows 11 x64

Custom changes or Modules

No response

@gabrielveras
Copy link

I'm thinking maybe this is a problem with the azerothcore server because I tried to the original milestorm mod and the worldserver also restarts.

@pagimu
Copy link
Author

pagimu commented Jul 31, 2024

OK. I will try the original MOD. Thx

@gabrielveras
Copy link

gabrielveras commented Jul 31, 2024

Hi @pagimu I've made this module work with the following changes to the azerothcore-worlk source code:
File LFGMgr.cpp:
[1742] if (true || !m_Testing)
[1837] if ((true || !m_Testing) && !allAnswered)
File LFGMgr.h:
[579] [[nodiscard]] bool IsTesting() const { return true || m_Testing; }

@pagimu
Copy link
Author

pagimu commented Jul 31, 2024

Thank for your message. I will try that asap.

@pagimu
Copy link
Author

pagimu commented Aug 4, 2024

Hi @gabrielveras, with your changes the solo-lfg works. I hope that will be fixed for futured updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants