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

Issue using the "auto" data tag with setblock.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • Minecraft 16w02a
    • None
    • Windows 8, Java jre 1.8.0_25
    • Unconfirmed

      I am attempting one-command-block contraptions, but I am having trouble using /setblock to place a command block with the data value "auto:1b". The command I used was as follows: /setblock ~ ~-1 ~ command_block 1

      {auto:1b}

      . The console would say block placed but when the command block was opened, it would say "needs redstone" instead of "always active". This is also the case with repeating_command_block, but it works properly with a chain_command_block. When /setblock ~ ~-1 ~ chain_command_block 1

      {auto:1b}

      is used it works as it should, with "always active" being displayed when it is first opened. I first discovered the issue on my server I was running for the snapshot. I then tried it on a single player world with the same result. I also got the same result when summoning falling sand that is set to command block using this command in an impulse command block: /summon FallingSand ~ ~1 ~ {TileID:210,Time:1,Data:1,auto:1b,Passengers:[

      {id:FallingSand,TileID:211,Time:1,Data:1,auto:1b}

      ]}. The result is a repeating command_block pointing upwards to a chain_command_block, also pointing upwards. The same data is used for both blocks aside from the TileID, however, the repeating_command_block displays "needs redstone" while the chain_command_block displays "always active". The same thing occurred when I tried nesting the "auto:1b" inside BlockEntityTag:{} as follows: /setblock ~ ~-1 ~ chain_command_block 1 {BlockEntityTag:{auto:1b}}. It was successful for the chain_command_block, but not the other two command block variants. I did some research on the Minecraft wiki and found that the "auto:1b" tag should be applicable to all three command block variants.

      I am sure you can imagine how annoying this could be for us redstone enthusiasts. Your work towards amending this issue is much appreciated. Thank you.

            Unassigned Unassigned
            McGill25 Tanner McGill
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: