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

"/spawnpoint" command fails directly on Pressure Plates, Cobwebs, Signs, Open Fence Gates

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Minecraft 1.4.1, Minecraft 1.4.2, Minecraft 1.4.3, Snapshot 13w07a, Snapshot 13w10b, Minecraft 1.5, Minecraft 1.5.1, Snapshot 13w16b, Minecraft 1.5.2, Snapshot 13w17a, Minecraft 1.6.1, Minecraft 1.6.2, Minecraft 1.6.4, Minecraft 13w38c, Minecraft 13w42a, Minecraft 13w42b, Minecraft 13w43a, Minecraft 1.7.1, Minecraft 1.7.2, Minecraft 1.7.5, Minecraft 14w11b, Minecraft 1.7.9, Minecraft 14w17a, Minecraft 14w18a, Minecraft 1.7.10, Minecraft 14w30b, Minecraft 14w30c, Minecraft 1.8, Minecraft 1.8.1-pre3, Minecraft 1.8.1, Minecraft 1.8.2-pre4, Minecraft 1.8.2-pre5, Minecraft 1.8.2-pre6
    • Vista 32-bit, vanilla 1.4.2 prerelease client
    • Confirmed

      For a simple pressure-plate & command block setup, when /spawnpoint @p (without coordinates) is operated by a command block, the command will fail after setting. /kill or dying says that the the home bed is obstructed, and returns the player to the original spawnpoint. This makes pressure plates and tripwires unreliable for setting a new spawn.

      When the coordinate is set, it is within a block- namely the pressure plate or tripwire string. This is probably why the spawnpoint command fails. If the player's hitbox brushes the edge of the pressure plate or string, there's a higher chance setting spawnpoint will work.

      To reproduce- place a pressure plate above the command block. Jump or land directly on the pressure plate. Type "/kill".

      Nov. 1st: I tested this today. Still get the same issue landing directly on a pressure plate. This is not fixed.

            searge [Mojang] Searge (Michael Stoyke)
            nirgalbunny David Warner
            Votes:
            22 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: