Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-177771

Respawn point set with sleeping in bed not saved if bed is removed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • None
    • 1.20.51 Hotfix
    • None
    • Unconfirmed
    • Windows

      I took a bed with me so that I could set a respawn point while on a long journey (see screenshot).  When I woke the next morning, I battled some nearby pillagers and they killed me (see screenshot).  When I respawned, it did not take me to the previous nights bed sleep coordinates (see screenshot) or any of the previous beds I had slept in.  Instead, it took me to my initial (world creation) spawn point.  It should not have done this.  It should have taken me to where I slept that night.  Or at the very least, one of my previous places I had a bed to sleep in.
      Not the world creation spawn point.

      Update:

      In case you need the world seed, it is 683559959776750046.  I worked to reproduce the issue and it seems that the respawn point shows blocked (see screenshot), even though it isn't.  The bed isn't there anymore since I take the bed with me.  However, the coordinates for the respawn point are not blocked.  This never happened prior to the latest patch.  I have Minecraft for Android as well and the same issue exists there too (patch 1.20.51).

      Update:

      I have found that if the source of the respawn point is destroyed (in this case the bed is destroyed so that I can take it with me), that is when the issue occurs.  If the source of the respawn point (the bed) is left in place, then the issue does not occur.  As a side note, I don't always pick up my bed.  So this issue might have been in previous patches/versions, I just didn't know.  But the bottom line is that if a respawn point is set, it should stay.  Unless the respawn point has been filled with something that the player cannot regenerate there.

            russpurg russpurg
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: