-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
NullPointerException crash from Totem Base ticking #226
Comments
Another related crash: https://gist.github.com/CelestialAbyss/98245181190896f4a88ad2bb3e9a6fbc |
I'm sorry for not fixing it earlier, life has been a mess and I've had no motivation. |
I was about to remove your mod in the next modpack update that I was going to publish due to the crashes occurring more and more often with the same cause, but good to see the bug actually patched after being ignored on the Discord after asking about it... I'll release an update for my players hopefully later today or two days from now and see if my personal server no longer crashes with this. More importantly, take care of yourself first and foremost. |
Okay, it seems like the error has yet to re-occur so it seems fixed... though there's a new issue that only happens with Malum's signs. |
The malum signs have been a problem for a while, they straight up do not have a proper renderer. |
MC version: 1.19.2
Forge: 43.3.2
Malum version: 1.5.0.3
Lodestone version: 1.4.2
I was not on while players were doing Malum related things, but it might be conflicting with chunk claims from Open Parties & Claims but I'm not too sure.
Edit: It is due to moving the totem base with Carry On, see here: Discord CDN
Edit 2: It also seems that a server restarting while a totem is in progress also causes the same issue to occur.
Gist is attached here: https://gist.github.com/CelestialAbyss/d058d3774cb6da590437907103da9c75
The text was updated successfully, but these errors were encountered: