mojira.dev
MC-207819

Respawn Anchor cancels out respawning at a bed after fully discharged

I found this glitch recently while playing on my single player world.

How to replicate:

  1. Place a bed in the Overworld and set your respawn point.

  2. Go to the Nether, place a Respawn Anchor, and charge it up fully with 4 glowstone.

  3. Do /kill 4 times until the Respawn Anchor is out of charge.

    • You will continuously respawn at the anchor as expected.

  4. Do /kill one last time

  5. You will now respawn in the Overworld at the original world spawn point as opposed to spawning by your bed.

I believe that as soon as a Respawn Anchor is used, it cancels out any other spawn points which makes sense. However, once there is no charge and the player dies one more time, the game no longer recognizes the players bed as the intended spawn point. This makes gameplay after dying in the Nether repeatedly a hassle if your base isn't close to the original world spawn.

Linked issues

Comments 5

This is because you set your spawn point at the respawn anchor not the bed.

Yes, but wouldn't it make sense for the game to set your spawn point back to your bed after the Respawn Anchor is out of charge?

Nope, this still makes sense. Once you click the respawn anchor, any logs of your bed being the spawn are deleted.

Respawn Anchors were created to set your spawn in the Nether as beds are not able to be used. Beds remain the sole way to respawn at your desired location within the Overworld.

Respawn Anchors deal with the Nether, thus it makes no sense as to why the Respawn Anchor should continue to have control of your Overworld spawn after it has been fully used. The bed should then be set as the default spawn point for the Overworld.

Additionally, upon dying using my provided method, the game says: "You have no home bed or charged respawn anchor, or it was obstructed". I'd say it's a fair argument for Mojang to consider allowing players to respawn at their originally set bed spawn after their Respawn Anchor is out of charge.

Thank you for your report!
We're tracking this issue in MC-175245, so this ticket is being resolved and linked as a duplicate.

That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit

MrPhantomEyez

(Unassigned)

Unconfirmed

(Unassigned)

1.16.4

Retrieved