[BUG] java.lang.NullPointerException
LiliumTragedies opened this issue ยท 1 comments
Is there an existing issue for this?
- I have searched the existing issues
Are you using the latest MineColonies Verison?
- I am running the latest alpha version of MineColonies for my Minecraft version.
Did you check on the Wiki? or ask on Discord?
- I checked the MineColonies Wiki and made sure my issue is not covered there. Or I was sent from discord to open an issue here.
What were you playing at the time? Were you able to reproduce it in both settings?
- Multi Player
Minecraft Version
1.18
MineColonies Version
1.19.2-1.0.1541-ALPHA
Structurize Version
1.19.2-1.0.492-ALPHA
Related Mods and their Versions
No response
Current Behavior
I have connected a framed block to a sticky piston - upon activating & deactivating the piston, the block wasn't pulled back as it should. From there on out, the skin slightly changed colors permanently, the small preview picture in the top changed colors randomly and the textures looked broken, and when I touched the block, the server crashed - with or without tools as well as in creative mode. I did not notice the change immediately as the color change of the block was subtle, but I believe I picked up the actual block either later or right in that moment. I tried to move the block with pistons to avoid problems, but ended up stepping on it. Now the server immediately crashes when I join, but I'm technically able to join.
We have attempted to change my player position in the playerdata-files, which resulted in the changed position being overwritten by the broken position. We tried copying the save to the computer of another player of the server both with my playerdata-file untouched as well as deleted and he ended up being teleported to the broken spot, crashing the server immediately upon joining as well.
We are unable to join the world in Singleplayer as well (we use the Essential Mod for Multiplayer so it's technically a Singleplayer-World I invited my friends to).
Reproduction Steps
Create a cross-framed block (it was one of the purely wooden ones needed for the Byzantine pack level one, most likely some spruce/oak combo)
Stick it onto to a sticky piston on the even dirt floor so it will be moved across the dirt (I had 3 pistons with a framed block each in a straight line above each other but only activated the lowest one)
Lay some redstone parallel to block & piston one block underground
Activate and deactivate the piston with a lever
-> the block should not be pulled back and now be broken
(I might have already fiddled around with the redstone at that point and might have activated and deactivated the piston quite a lot and/or quickly)
Logs
https://1drv.ms/f/s!AkNkz5CLYGBNhKFdxdAjdBDswIEzcA?e=tJEe9A
Anything else?
2023-07-17-4.log / crash-2023-07-17_23.16.34-client relate to the session during which the issues arose and the first crash happened (the log's so big it crashed github so I uploaded it to OnDrive)
crash-2023-07-18_00.14.01-client relates to the first immediate crash after rejoining after I stepped on the broken block
- Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
- Add a comment if you have any insights or background information that isn't already part of the conversation.
crash-2023-07-17_23.16.34-client.txt
crash-2023-07-18_00.47.58-client.txt
crash-2023-07-18_00.14.01-client.txt