Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-175186

Respawning doesn't check if the "respawn block" is the correct one for the dimension

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: 20w12a
    • Fix Version/s: 20w17a
    • Labels:
      None
    • Confirmation Status:
      Confirmed
    • Category:
      Block states
    • Mojang Priority:
      Important

      Description

      The bug:
      When you set your respawn location with either a bed or an respawn anchor and dies there is a check to check if the bed / respawn anchor still exists.
      The "bed / respawn anchor check" checks both for beds and respawn anchors no matter what dimension you are trying to respawn in. Meaning that if you go into the nether and place a respawn anchor, set your spawn point and then replace the anchor with a bed the next time you die you will respawn in the nether beside the bed.

      Expected:
      You will only be able to spawn beside beds in the overworld.
      You will only be able to respawn beside respawn anchors in the nether.

       

      Recreate (nether):
      Place respawn anchor.
      Fill anchor with glowstone.
      Right click the anchor to set respawn point.
      Break the anchor.
      Place bed in same location.

      Next time you die you will respawn beside the bed in the nether.

       

      Recreate (overworld):
      Place bed.
      Right click the bed to set respawn point.
      Break bed.
      Place anchor in the location the bed's head was at.
      Fill anchor with glowstone

      Next time you die you will respawn beside the anchor in the overworld.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mgatland [Mojang] Matthew Gatland
              Reporter:
              Vilder50 Vilder50
              Votes:
              8 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                CHK: