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

Spawnpoint set on respawn anchor using /spawnpoint depletes glowstone charge, and doesn't stay on respawn anchor if its charge is depleted


    • Icon: Bug Bug
    • Resolution: Fixed
    • 22w42a
    • 20w14a, 20w15a, 20w16a, 20w17a, 20w18a, 20w19a, 20w20a, 20w20b, 20w21a, 20w22a, 1.16 Pre-release 2, 1.16 Pre-release 3, 1.16 Pre-release 4, 1.16 Pre-release 5, 1.16 Pre-release 6, 1.16 Pre-release 7, 1.16 Pre-release 8, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w27a, 20w28a, 20w29a, 20w30a, 1.16.2 Pre-release 1, 1.16.2 Pre-release 2, 1.16.2 Pre-release 3, 1.16.2 Release Candidate 1, 1.16.2 Release Candidate 2, 1.16.2, 1.16.3, 1.16.4 Pre-release 2, 1.16.4 Release Candidate 1, 1.16.4
    • None
    • Confirmed
    • Commands
    • Normal

      The bug

      When you set your spawn to a bed or respawn anchor with a command, the respawn block behaves as if you used it, with the exception of you respawning there even after the respawn block is destroyed. However, charge a respawn anchor and then use /spawnpoint on it, and you will deplete the charge until it is gone, and then the respawn anchor will not let you spawn there but destroy the respawn anchor and you can spawn there just fine.

      The bug is either that setting a spawnpoint at a respawn anchor with a command depletes the glowstone charge, or that setting a spawnpoint at a respawn anchor with a depleted charge does not allow you to spawn there.

      I think that the bug is the fact that the glowstone charge is depleted when you use /spawnpoint on the respawn anchor because it makes sense that the respawn anchor with a depleted charge would not spawn you because the block would be considered obstructed.

            slicedlime [Mojang] slicedlime
            TriWonder81 [Mod] Chandler
            4 Vote for this issue
            3 Start watching this issue