-
Notifications
You must be signed in to change notification settings - Fork 13
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
Minecraft crashing when opening skill tree #115
Comments
Thanks for reporting. I have seen such crash before, and somehow it was fixed after the person who reported it updated the mod, even though nothing related to it was changed. In your case I would say to verify if server and clients have the same version of the mod, but since you said it worked for some time, this is unlikely to be the reason. The problem is that the crash report you send and the one I got earlier give no information what actually causes issue, but it is definitely a mod conflict. The fact that it happens after some time make is even harder, so unless you or someone else have or find steps to reproduce this crash, I think I won't be able to help. |
Does this mean that now each time someone opens skill tree the client crashes? If so, could I join that server to experience and analyze this crash myself? You can message me on Discord, my nick is |
So restarted the server this morning and everything has seemingly fixed itself? I haven't changed a single thing since last night when we were playing the whole day. I will keep your discord at hand and if it happens again ill keep the server up send you the ip and mod list just incase its an underlying issue or isolated to me . |
Using the modpack "DarkRPG" on my own server (fabric 1.20.1). At first it was completely fine . However a few hours in opening the skilltree screen will crash anyone who does it on the server. On single player acts as normal, pressing the keybind opens up the overlay and there are no issues. Issue might fix after a restart on server but that has not been done yet.
crash-2025-01-06_20.53.25-client.txt
The text was updated successfully, but these errors were encountered: