-
Notifications
You must be signed in to change notification settings - Fork 276
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
[1.16.5] Client-crash after putting living armor #1853
Comments
Tried the downgrade, that didn't work, so as admin of the server I spammed /clear [playerName] bloodmagic:livingplate over and over as my player joined the server. It finally caught him, so now he can play. |
Putting on the full set of living armor completely breaks the game... had to roll back the server. enigmatica 6 [05.11 16:54:22] [Server] Caused byjava.lang.NullPointerException: Cannot invoke "wayoftime.bloodmagic.core.living.LivingStats.getLevel(net.minecraft.util.ResourceLocation)" because the return value of "wayoftime.bloodmagic.core.living.LivingStats.fromPlayer(net.minecraft.entity.player.PlayerEntity)" is null |
the bug isn't from 2017 - it was introduced in version 19(?) or so, with the Elytra upgrade, and only occurs on modpacks with the Caelus API, or other APIs that interact with Elytra flight. A fix has been PRd and will be included in the next version. |
I got the same crash in the same modpack. It crashes the first time I put on the full set of living armor, and it crashes again after restarting the game and re-entering the (single-player) world. I tried a custom build of the mod with #1856 applied, and confirmed that it fixes the crash for me. |
Soooo, when can we expect this one to drop in an update? it seems like quite a big one for those budding blood magic enthusiasts and probably worth the triage hotfix update... and it happens in my own pack also. A friend got hit by it just the other night. Glad it's know and has been slapped out though. |
When Way has time to do a release. We have lives outside of this hobby. |
shoulda expected that kinda response honestly, and I didn't mean to insinuate that you don't have lives, but I guess big mod takes more time to build a release than others and theres probably devvy-tester things still enabled in dev that would slow that down... :V |
Issue Description:
Client-crash after putting the 'living armor' in Valhesia 3.4.4 on a server (linked the crash report to Val3 team and they asked me to put it here).
Cannot relog 'internal server error' .
What happens:
I just crafted the full set of 'living armor' and the moment I put it on I crashed.
After that I'm not able to connect to the server 'internal server error' but others can and they can play normally.
What you expected to happen:
Steps to reproduce:
Don't know if Valhesia 3 has an impact here (didn't test the mod alone)
...
Affected Versions (Do not use "latest"):
Valhesia 3.4.4 launched via Curseforge
Link to log + crash report :
https://gist.github.com/Tristan-LeBras/188c165e08d8e117d43edce40c22d1a3
The text was updated successfully, but these errors were encountered: