LoliKingdom / LoliASM

The lolis are now preparing to bytecode manipulate your game.
GNU Lesser General Public License v2.1
105 stars 23 forks source link

[1.12.2] Exception in world tick - "recheckGapsGetLowestHeight" - Need help #74

Closed aking4125 closed 2 years ago

aking4125 commented 2 years ago

Hello,

I understand that this issue isn't related to LoliASM at all but I am running out of options and I cannot pinpoint the exact cause of this problem but here is the gist.

This only applies to the client. Upon exploring the world, the client would crash with below crash error. Upon reloading into the server or world 80% of the time the client is stuck on a crash loop until the player TP's out of that position. For some reason this seems to affect only a few players at a time in random locations but those locations become "Crash zones" for the players until the server restarts. Once it restarts, they are free to enter the area, but then crashes upon entering another random chunk. Sometimes it's right next to their base.

The only clue I got is upon entering the kill command to destroy all entities. The crash stops for a bit. So it might just be an entity though only once did this not fix the problem. However the kill command must be performed while in a world. So a second player is required to save the other each time. Restarting the server is the temp fix but random locations gets affected again. This is a very annoying problem and I never experienced this in 1.12.2 before. Any ideas or a clue or a point in the right direction would be greatly appreciated. This occurs in both Single player and Multiplayer but the server itself doesn't crash. Only the client.

Client Crash Report: crash-2022-04-24_09.56.18-client.txt Client Debug Log Modpack files

Again, any ideas or a clue or a point in the right direction would be greatly appreciated!

Rongmario commented 2 years ago

Thanks for the report, this is actually a crash from Fluidlogging API: https://github.com/jbredwards/Fluidlogged-API/issues/75, I believe a fix is being worked on.

aking4125 commented 2 years ago

Thank you for the instant response!