[MC-175988] Dying without a valid spawnpoint causes a softlock

Workaround

Run /spawnpoint, and then close and reopen the world.

The bug

After dying and respawning in 20w13a without a valid spawn point, the game is in a softlocked state. The player will have a duplicated version of themselves standing at the same location, and they won't be able to move or interact with the world in any other way. This even persists after closing and reopening the world. This affects all game modes.

When this happens, the following will be printed into the game console:

Error executing task on Server
java.lang.NullPointerException
	at bns.l(SourceFile:173)
	at bns.d_(SourceFile:421)
	at aav.a(SourceFile:495)
	at zc.a(SourceFile:1216)
	at qv.a(SourceFile:30)
	at qv.a(SourceFile:8)
	at na.a(SourceFile:21)
	at ug.run(SourceFile:18)
	at akx.c(SourceFile:144)
	at alb.c(SourceFile:23)
	at net.minecraft.server.MinecraftServer.b(SourceFile:749)
	at net.minecraft.server.MinecraftServer.c(SourceFile:142)
	at akx.w(SourceFile:118)
	at net.minecraft.server.MinecraftServer.bc(SourceFile:731)
	at net.minecraft.server.MinecraftServer.w(SourceFile:725)
	at akx.c(SourceFile:127)
	at net.minecraft.server.MinecraftServer.v(SourceFile:710)
	at net.minecraft.server.MinecraftServer.run(SourceFile:662)
	at java.base/java.lang.Thread.run(Thread.java:835)

Error executing task on Server
java.lang.NullPointerException
	at yd.b(SourceFile:201)
	at xw.a(SourceFile:904)
	at yi.a(SourceFile:478)
	at zc.a(SourceFile:845)
	at ri.a(SourceFile:122)
	at ri$b.a(SourceFile:18)
	at na.a(SourceFile:21)
	at ug.run(SourceFile:18)
	at akx.c(SourceFile:144)
	at alb.c(SourceFile:23)
	at net.minecraft.server.MinecraftServer.b(SourceFile:749)
	at net.minecraft.server.MinecraftServer.c(SourceFile:142)
	at akx.w(SourceFile:118)
	at net.minecraft.server.MinecraftServer.bc(SourceFile:731)
	at net.minecraft.server.MinecraftServer.w(SourceFile:725)
	at akx.bm(SourceFile:103)
	at net.minecraft.server.MinecraftServer.v(SourceFile:709)
	at net.minecraft.server.MinecraftServer.run(SourceFile:662)
	at java.base/java.lang.Thread.run(Thread.java:835)

To reproduce

Run /spawnpoint @s ~ ~ ~ while in spectator mode somewhere underground (so that the spawnpoint would be blocked
Switch into Creative, Survival, or Adventure mode
Die
Respawn
→ ❌ Your game is in a softlocked state

Linked issues

is duplicated by 60

MC-176005 Using /kill ceases most if not all functional gameplay Resolved

MC-176009 My character had been duplicated Resolved

MC-176013 After dying in a creative world in the nether while on survival, respawned with a buggy game Resolved

MC-176016 You cannot move, destroy and place blocks after you die. Resolved

MC-176021 20w13a Camera disjoins from player when dying Resolved

55 more links

relates to 1

MC-176004 Cannot interact with the world after dying in the end or the nether without a valid spawn point Resolved

Attachments

Minecraft 2020.03.26 - 00.16.53.01-1.m4v

Screen Shot 2020-03-25 at 11.00.48 AM.png

Screen Shot 2020-03-25 at 11.00.57 AM.png

Comments 31

NEVERBRICK 2020-03-25T17:52:49Z

It's a bug that makes this snapshot impossible to play. One death and your game is lost... Something like hardcore ;]

gaspoweredpick 2020-03-25T17:55:01Z

Confirmed. This frozen state is literally impossible to escape, even with commands, making the snapshot practically unplayable. This needs to be fixed ASAP.

gaspoweredpick 2020-03-25T17:59:45Z

You can also punch and kill yourself when in survival mode in this state.

PR0CESS 2020-03-25T17:59:51Z

All worlds are hardcore...

violine1101 2020-03-25T18:01:51Z

I wasn't able to confirm, does this only happen if the spawnpoint is blocked / not set / something like that?

21 more comments

Cosmic306 2020-03-25T18:03:09Z

Yeah, this only happens if your respawn point is blocked/not set.

gaspoweredpick 2020-03-25T18:09:59Z

It happens unless you have a valid spawnpoint it seems. Useng the /spawnpoint command in a valid position will prevent this bug from happening in a particular world.

Nickolas Azylanmik 2020-03-25T18:14:25Z

I also had it happen to me, I wondered what the heck was wrong.
I think this is serious enough to release 20w13b.

No 20w13b needs to be released to fix this gamebreaking bug.

Virang Raman Patel 2020-03-25T18:24:06Z

You can start a new world, do /kill, that it will work as well. This is confirmed

violine1101 2020-03-25T18:32:54Z

If you want to recover your singleplayer world, you'll need to edit your level.dat file. Inside of Data.Player, set Health to 20 and DeathTime to 0. This will allow you to load the world again.

Nickolas Azylanmik 2020-03-25T18:38:17Z

Thanks for that.

phigraz 2020-03-25T18:49:01Z

The same bug also happens when returning to the overworld via end portal (which attempts to place you at your spawnpoint), but since this doesn't involve death you can just reload the world without getting softlocked into the death screen. So it seems any attempt to respawn a player will cause this bug.

Interestingly, when triggering the bug this way you can still run around but the internal server won't register anything you do (breaking/placing blocks, going through portals etc.). So for instance, if you break a block, it'll become a "ghost block" as the server still thinks it's there, and when you quit and reload the block magically comes back.

W_V 2020-03-25T19:06:09Z

Also confirmed. Hope I will not die in my favorite SURVIVAL world.

ItsDaCreeper 2020-03-25T19:09:38Z

Happened on stream: https://www.twitch.tv/cubfan135/clip/FineSparklingLocustPJSalt

anthony cicinelli 2020-03-25T19:11:03Z

If you punch while soft locked you do damage to yourself.

Pista Snake 2020-03-25T19:14:07Z

Using the /tp command causes your camera to teleport, yet your player model still stays

Sedew 2020-03-25T19:38:25Z

This is the most terrifying, cursed and extraordinary bug I have ever seen. If I reload the world, the death screen appears again and I’m stuck again. It would amazing if something like this became a feature in another difficulty.

Like I’m now the soul watching my body.

I can’t break blocks, I can’t do anything.

Sniper1.1 2020-03-25T19:50:30Z

Oh my god! This just happened to me and I was unbelievably confused. Glad you posted it. I was just sitting here trying to figure out how to word this bug. My title was going to be "I'm Beside My Self With this Minecraft Bug". I also want to mention that I never changed the spawn point. It should have just been the world spawn.

Ben Lewis 2020-03-25T20:18:21Z

The comment about hitting blocks causing damage is incorrect.

From my observations, a ghost/duplicate of the player is created/not properly removed where the player died. Thus, mobs will attack that ghost player, or if in somewhere like lava, it will continue to take damage and kill the still living (newer) player.

McModknower 2020-03-25T20:24:23Z

This bugging around is also affecting you when you exit the end.
If you exit the end, you can move, but not place or break blocks.

FaRo1 2020-03-25T20:45:57Z

You don't need any third party software as a workaround for this, the method at the end of the report works as well: "/spawnpoint" in a valid location, "/kilL", relog.
Here is a video showing some of the effects of this "paralysis", it's pretty crazy: https://www.youtube.com/watch?v=rBH-sreoJg0
This is how I described the effects in my duplicate report: Moving the camera works, but it doesn't turn the character's head. Walking does not work at all. Teleporting works, but it does not move the character, just the camera position. Teleporting with "^ ^ ^1" teleports to the view direction from before the previous teleportation. Chunks do not load past the render distance away from the character. Items thrown appear in front of the character. Blocks broken or placed are ghost blocks or re-(dis)appear. …

Francis 2020-03-25T20:54:06Z

I found out how to fix it. (at least it worked for me idk lol) what i did was reload, start tp'ing around with /tp ~ ~ ~1. then i relogged into my world and i was back lol

Pista Snake 2020-03-25T21:38:22Z

Actually, this bug happens by just dying normally in a newly created world without having ever set your spawn... You don't need to do the spectator mode stuff to reproduce it. It basically makes survival mode a bit dangerous knowing that dying without using a bed can softlock your world.

Adrian Ratajczak 2020-03-25T21:48:15Z

I can't connect to a server agian. I found out that if you delete playerdata folder in world folder you can connect to the server and move 🙂.

Paul Bühne 2020-03-25T21:54:23Z

I played the new snapshot with a few friends. After all of us died, I tried to fix the problem. Deleting the playerdata worked for my friends, but I still was hold in place. I needed to copy the region files over to a new world.

Aidan 2020-03-26T00:33:11Z

this also happened to me and is currently unfixable a creeper killed me and blew up my bed

Nixinova 2020-03-26T02:38:16Z

Literally the weirdest bug I have ever experienced.

Dylan Rivero 2020-03-26T03:24:51Z

This also happens in Multiplayer. For a workaround I have decided to downgrade to 20w12a.

Here is a YouTube video.

https://www.youtube.com/watch?v=pWF7oveGx2Y&feature=youtu.be

[Mod] ManosSef 2020-03-26T08:50:33Z

This happens because the health of the player is not set to 20 after respawning and stays 0.

Henners Jenkies 2020-03-26T10:02:37Z

Same happened to me, you can even kill yourself

Tom Boehmer 2020-03-27T03:31:53Z

Had this problem in a multiplayer server I host. Was unable to fix through setting the affected players spawnpoint. Eventually had to manually delete their .dat file to allow them to keep playing.