Description by [~Auldrick]:
The logic used in Bedrock to set and use player respawn points results in different behavior from Java Edition under certain circumstances. It also provides an opportunity for other players to grief a target player and create an infinite death loop.
Griefing/Infinite Death Loop
Steps to reproduce:
1. Player 1 places a bed and uses it to set their respawn point.
2. Player 2 notes where player 1 was standing and digs there a hole deep enough, or builds an obsidian-topped pillar high enough, to kill an unequipped player from fall damage. The pillar could also be used for extortion instead.
3. Player 1 dies for any reason.
Expected results:
Player 1 respawns either at another block near the bed or at world spawn.
Actual results:
Player 1 respawns at the set respawn point and falls to their death again. This repeats infinitely or until someone breaks the bed.
Java Parity Breaks
Breaking a bed does not reset the respawn points of players who last used the bed. Because of this, if you break a bed and place a new one in the same position, your respawn point remains in effect. Note that after replacing the bed, using the new bed will not change your respawn point or display the message, even if you're standing at a different place when you use it. This is unintuitive and could be confusing, particularly if you took your bed on an expedition but never actually used it to set your respawn point until you came back home, at which time you would find you cannot reset it. Another unintuitive situation would be if you break your bed and independently, another player places his bed in the same spot. This would prime you to respawn unexpectedly in a different player's bed, one that perhaps has a different color and orientation than your own had,
The game saves a player's bed position, but not its orientation. Because of this, if you break a bed and place a new one in the same position but with a different orientation, your respawn point remains in effect. This is also unintuitive and could be confusing.
The game always respawns a player at the player's last bed position if a bed exists there, even if the respawn position is obstructed. In Java Edition, the player is respawned at world spawn under these circumstances.
If a player's respawn point, from either a bed or world spawn, is obstructed, the game respawns the player on the block with sky access at the same X and Z coordinates. This can cause the player to be spawned on a sky island or an overhang from which it's impossible to return without dying, yielding an unintended infinite death loop. In Java Edition, I think the player is respawned at a horizontally nearby block under these circumstances.
Original description:
Occasionally, when trying to set your spawn point by clicking on a white bed, it will simply not work.
This of course needs to be done during the day, but normally when clicking on a bed during the day, it will tell you that your spawn point has been set.
I have only seen this happen with white beds, and it has happened to me several time, in both creative and survival. Very frustrating when you realize after you die that it didn't work🙂
Video footage of this bug in action. Skip to 8:22
https://www.youtube.com/watch?v=9AgSEVfJicE
Related issues
is duplicated by
Comments
Auldrick
silentwisperer
Thanks for all the info, certainly some interesting and weird differences between java and bedrock mechanics here. And i do agree, its not very intuitive at all haha. If you don't go out of your way to test something, then you will never figure out how it actually works from normal gameplay.
Thanks again for the clarification on this one!
[Mojang] Mega_Spud (Jay)
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? It looks as through the repro steps are quite different to the originally mentioned "bug".
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
silentwisperer
This report can be closed, have not been able to reproduce.
There is no logic that treats a white bed differently from other colors. That was just a coincidence of the order you tested things. What you were actually seeing was the effect of clicking on the same bed repeatedly, of breaking the bed and placing a new one with its head in the same position (though not necessarily with the same orientation), and of the game's logic with respect to respawn points, which may be considered buggy in some respects. The aspects of this logic are:
The game remembers each player's bed position and last respawn point. The bed position only includes the coordinates of its head block; the orientation isn't saved,
When you right-click on a bed, the game compares the bed position to your saved bed position. If different, it saves the bed position, saves the coordinates you're standing at as your respawn point, and issues the"Respawn point set" message.Otherwise it does not update your respawn point or issue the message. The intent here is to suppress the message when all you want is to sleep.
When you click the Respawn button after dying, the game checks whether there is a bed at your saved bed position. If not, it sets your respawn point to the world spawn point. In either case. if your respawn point is obstructed it spawns you on the block with sky access at those coordinates.
Note that your respawn point is set to the coordinates you're at when you click the bed. The northwest adjacent block behavior you mention in the video only applies to the point you're placed at when you wake up, not to your respawn point.