Context
When a player disconnects while the object has an AE2 Growth accelerator, the server spits out errors about Rapier3D_getPose and no entry found for key.
I found this out in survival by removing every block of my AE2 system in a game of elimination and landed on the Growth accelerator, causing the crash. I suspect it has to do with the position the player is in relative to the airship (I'm playing with aeronautics right now) when the airship unloads; however, I cannot be sure, as I'm not familiar with this codebase.
If this is not an issue with Sable, I'd be happy to bring this to the AE2 Developer's repo instead, and vice versa if this is an aeronautics bug and not a Sable bug, same story.
I have to include a partial log as the default Minecraft (or neoforge, I don't know who writes the log stuff) crash, and normal logs don't produce the debugging information seen in the console, but as this is an LXC PVE under an xterm.js environment, my terminal has a maximum text log length.
I will also post below this my latest.log so you understand the server further (the mods on it, etc.) (Although this log does not show the crash, it gives insight)
https://mclo.gs/rt0Dbrt
Crash Report
https://mclo.gs/rkl90pq
Context
When a player disconnects while the object has an AE2 Growth accelerator, the server spits out errors about Rapier3D_getPose and no entry found for key.
I found this out in survival by removing every block of my AE2 system in a game of elimination and landed on the Growth accelerator, causing the crash. I suspect it has to do with the position the player is in relative to the airship (I'm playing with aeronautics right now) when the airship unloads; however, I cannot be sure, as I'm not familiar with this codebase.
If this is not an issue with Sable, I'd be happy to bring this to the AE2 Developer's repo instead, and vice versa if this is an aeronautics bug and not a Sable bug, same story.
I have to include a partial log as the default Minecraft (or neoforge, I don't know who writes the log stuff) crash, and normal logs don't produce the debugging information seen in the console, but as this is an LXC PVE under an xterm.js environment, my terminal has a maximum text log length.
I will also post below this my latest.log so you understand the server further (the mods on it, etc.) (Although this log does not show the crash, it gives insight)
https://mclo.gs/rt0Dbrt
Crash Report
https://mclo.gs/rkl90pq