
Bug: "...boss.Slider.getEntityData()" is null" error causing crashes
NateClarkTech opened this issue ยท 2 comments
What Feature Types Apply to This Bug?
Entity
Other Type
No response
What Type of Bug Is This?
Crash
Mod Loader
NeoForge
Mod Loader Version
21.1.92
The Aether Version
1.5.1-beta.4
Is This Bug a Conflict With Another Mod?
No response
Client Log
https://gist.github.com/NateClarkTech/e81b74b816835d57df567a912807543d
Crash Report (if applicable)
https://gist.github.com/NateClarkTech/3403626b4f3e6bc7f291c7f489328d64
Steps to Reproduce
I run a modded server and from what the players are telling me this is what seems to be happening:
Player will be near a dungeon and the game will crash.
After this crash any future attempts to log in will have a crash, and from the several crash logs I have looked it the cause is always similar with the
com.aetherteam.aether.entity.monster.dungeon.boss.Slider.getEntityData()" is null
error.
What You Expect To Happen
Game not to crash when approching an area with an Aether boss.
What Actually Happened
Game crashes when near an area with an Aether boss sometimes.
Additional Details
The server is a modded server, the server has no errors from what I can see on the console, the bug doesn't seem to always occur but when it does it continues crashing the client when attempting to reconnect.
The crash doesn't happen immediately after crashing so I have enough time to TP players out of the Aether when they are connecting to the server.
Please Read and Confirm The Following
- I have confirmed this bug can be replicated without the use of Optifine.
- I have confirmed this bug is on the most recently supported version of Minecraft.
- I have confirmed the details provided in this report are concise as possible and does not contain vague information (ie. Versions are properly recorded, answers to questions are clear).
- I have confirmed this bug is unique and has not been reported already.
- If playing on a modpack, I have reported this bug to their issue tracker already.
- I have confirmed that I'm reporting a bug in The Aether I, not The Aether II.
Didn't notice that when I was reading the log, thank you for redirecting me.