Closed Jack-0-Spades closed 1 year ago
The same thing happened to me on a server with friends for 1.12.2
investigated a bit and apparently it is because the entity in question is corrupted but it is not important now
Every time it happens I solve it in the following way: (because you are the cause of the crash because you are in the chunks where the error is generated you should tell someone else to do this, or just log in with another account, In case the error is not in the chunks of the start of the world) Anyway.
I put a command block on repeat that doesn't need redstone to work, this way it's always active
Then, inside the block I put the following command:
/kill @e[type=entity]
(the entity is the cause of the error)
For example, in my case the one that gives an error is the entity sea serpent bubble. In-game it appears as follows:
iceandfire:seaserpentbubble
So it would look like:
/kill @e[type=iceandfire:seaserpentbubble]
With that done, all that remains is to re-enter the world at the place where it crashed and the command block will remove the entity before it causes a crash. (The chunk where the command block is must be being used by a player for it to work, because if the chunk is not being generated, the command will not work, although I don't know much about the block So I don't know if that's true or not.) (also, before doing the command you should check how to do /kill correctly for your version as I don't know if it's different for yours)
1.12 isn't supported anymore
What happened?
Sea serpent causes crashes
Minecraft Version
1.16(CRASHES ONLY)
Ice and Fire version
1.9.1
Citadel version
none
Relevant log output
Other Information