Create

Create

86M Downloads

Belt Funnel Server Crash

NielsPilgaard opened this issue ยท 6 comments

commented

One of my players was using some belt funnels and some chests, he removed the chest and this immediately crashed the game, now he can't log into that world without crashing the game.

Versions

  • create-mc1.14.4_v0.1.1a
  • Forge-1.14.4.28.1.109

Logs

https://gist.github.com/NillerMedDild/51e97a35d5c250925dd183c21de30b07

Original issue: EnigmaticaModpacks/Enigmatica4#285

commented

Thanks for the report. As we're getting repro and sorting this out, I recommend, in an effort to get your player unstuck, to watch the server messages and have a teleport command ready to teleport the player to you in another chunk.

When you see the connection message, fire it off. The player won't be loaded into the game fully (model is not there and they can't see), and they will be immediately kicked off again, but the next time they login, they should be able to get in. This avoids you having to delete the player data on the server (which would get rid of levels, inventory, etc).

You should be able to still revisit this chunk without further problems. Let us know if you can't, but for all bugs that have popped up like this for any mod I've worked with, this little trick usually unsticks a player.

commented

It's not a rendering crash, so that wouldn't help I'm afraid.

What he actually did was he tried to push a belt with a piston.

commented

The crashes I've experienced that this worked on were not rendering crashes either.

commented

Hi,
this happened due to Create not being prepared to deal with push-able TileEntities. We have it fixed at the frontier, and will roll it out with an upcoming release.
For recovering your player's world, I suggest they either use something like McEdit to kill the block, or contact us on the feedback channel directly for a patched jar. Waiting for an update may take a while, sadly we still cannot estimate a specific date for 0.2.

commented

No worries, he fixed it :)

commented

This should be addressed in the new version that went live just now.
Thanks for the Issue and feel free to re-open if need be.