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

1.7.4 Door setblock placement bug [Resolved]

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Works As Intended
    • Affects Version/s: Minecraft 1.7.2, Minecraft 13w48b, Minecraft 13w49a, Minecraft 1.7.3, Minecraft 1.7.4
    • Fix Version/s: None
    • Confirmation Status:
      Unconfirmed
    • Game Mode:
      Creative

      Description

      Well, if Chrome hadn't crashed on me, this would be a lot more descriptive...because I haven't ever seen someone spawning doors regularly anywhere, so I figured not too many people know about it...

      In previous versions of the game, I was able to spawn a door in a specific position, but I noticed in 1.7.2 that was not possible.

      To duplicate this glitch, you'll need 2 command blocks, one on top of the other. In the top one place this code:

      setblock ~ ~ ~2 64 8 destroy {DropItem:0}

      And on the bottom place this code:

      setblock ~ ~ ~2 64 4 destroy {DropItem:0}

      The damage value of the upper door must be 8 or 9, and the DV on the bottom half of the door determines its position. In previous versions, IDS 1-4 would give 4 separate positions, but after 1.7.2, I was unable to get position 4, it would just move to position 1. I tested ID 5 and it moved to position 2.

      This bug prevents me from progressing any farther in the tech of the map. A vote up would be nice.

      Additional details: persists even with exact coords, command blocks that were in the level before 1.7.2 still spawn correctly,

      If someone would confirm this it would make me happier. Seriously, the silence gets to you after some time... .-.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                aerotactics Aerotactics
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: