-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing when switching dimensions and loading different saves. #17981
Comments
there isn't the NullPointerException in the log that you provided, can you give the crashlog instead please ? |
crash-2024-10-27_14.40.31-server.txt |
thanks! |
do you have the config "machineWireFire" off ? |
Posted the wrong discord username, and I will check to see if so |
No, I have machineWireFire on, and I updated the discord username so you can message me on that. |
To top that all off as well, I have every single wire covered by some kind of block. |
I can confirm this, happens frequently when loading into my single player worlds. I'm not sure how wires might be related, but the world is in the stone age, so there are no wires. |
As of 2.7.0 beta-4 this issue with a java.lang.NullPointerException has appeared to resolve itself. I cannot replicate this crash in beta-4. |
Your GTNH Discord Username
Starcluster#3252
Your Pack Version
2.7.0-beta 3
Your Server
SP
Java Version
Java 21
Type of Server
Single Player
Your Actions
I tried to travel to the nether, and crashed. This issue however also occurs when traveling to other dimensions, and when switching from one save to another. This has occurred when loading my main save, then quitting, and loading a test world save. This crash also occurs when traveling to and from the twilight forest at times. The specific reason sited for the crash is:
"A fatal error has occurred during the network handshake, this connection is terminated. Check the log for details. The exception caught was: java.lang.NullPointerException: Cannot read field "field_147371_a" because "player.field_71135_a" is null".
Crash Report
fml-server-latest.log
crash-2024-10-27_14.40.31-server.txt
Final Checklist
The text was updated successfully, but these errors were encountered: