mojira.dev
MC-187408

Game crashing with Nether portals - java.lang.NullPointerException: Ticking player

Moderator Note

Worlds newly generated in 1.16 Pre-release 1 are corrupted beyond simple repair. The part of the level.dat file that stores dimensions has gone missing, meaning that these worlds do not have a Nether or End. @unknown has a full explanation in this Pre-release 2 video here, along with some potential ways on how to fix it - though we thoroughly recommend to instead just discard the world.

Built a portal, game crashed before loading Nether.

Stack trace

1.16-pre1\: [^crash-2020-06-04_16.23.07-server.txt]

Description: Ticking player

java.lang.NullPointerException: Ticking player
	at ze.a(SourceFile:651)
	at aoj.bg(SourceFile:1900)
	at aoj.ad(SourceFile:437)
	at aov.ad(SourceFile:320)
	at aoj.j(SourceFile:419)
	at aov.j(SourceFile:2181)
	at bdy.j(SourceFile:275)
	at ze.w_(SourceFile:418)
	at zv.b(SourceFile:206)
	at me.a(SourceFile:234)
	at zu.c(SourceFile:171)
	at net.minecraft.server.MinecraftServer.b(SourceFile:885)
	at net.minecraft.server.MinecraftServer.a(SourceFile:812)
	at eov.a(SourceFile:93)
	at net.minecraft.server.MinecraftServer.v(SourceFile:671)
	at net.minecraft.server.MinecraftServer.a(SourceFile:256)
	at java.lang.Thread.run(Thread.java:745)

Linked issues

MC-187413 Game crashes when entering the nether Resolved MC-187427 Nether Crashes upon Generation Resolved MC-187441 No nether or end dimension Resolved MC-187500 Nether not accessible Resolved MC-187511 Game crashing when entering nether Resolved

Attachments

Comments 9

Did you use any special custom world gen settings? If so, please attach them to this ticket.

MC-185004 is caused when the nether doesn't exist, which could be caused by MC-187364.

I Tried To Reproduce This Glitch By Creating New Worlds, However The Nether Would ALWAYS Spawn In And The Game Would Not Crash

I Think That Either 1. This Is A Datapack Issue Or 2. A Custom Worlds Issue

Creating a new world and then relogging before going to the Nether triggers the crash. Going to the Nether in a fresh world without relogging first works. Looks like dimensions are not saved or loaded correctly.

No custom settings or data packs installed. Completely fresh hardcore world. There were some generation errors within the world as well - i.e. biomes cut off along chunks and such.

Yep, I did relog before visiting the nether.

I found two possible solutions to this issue.

 

Option 1 (easier):

I simply created a new world with the same seed as the corrupted world. I then moved the level.dat from the newly created world's save folder to the corrupted world's save folder overwriting the data. This allowed me to enter the nether with no problem.

 

As far as I am aware of this should not change any blocks. It does however delete all items in your inventory, so you should place them in a chest before attempting this method. It's also worth mentioning that this method transfers gamerules, difficulty, time, gamemode, and some other information, so make sure your newly created world has the same world options as the corrupted one.

 

This wiki contains exactly what data transferred.

 

Option 2 (better option, requires NBT editing):

Create a new world with the same seed as the corrupted world. Transfer the NBT data from "Data.WorldGenSettings.dimensions" in the newly created world's level.dat to the corrupted world's level.dat.

 

This method will not change anything except dimensions.

 

Make backups!

Benjamin Cooper

(Unassigned)

Confirmed

Crash

1.16 Pre-release 1

1.16 Pre-release 2

Retrieved