Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Duplicate
    • Affects Version/s: Minecraft 1.9.2
    • Fix Version/s: None
    • Labels:
      None
    • Confirmation Status:
      Unconfirmed

      Description

      Bug in the pick_block with new command_block

      What I expected to happen was...:
      that put a pick_block new.command_block work as a command block, not as a command_block set as "Impulse","Unconditional","Needs_redstone"

      What actually happened was...:
      put a chaine_command_block with a commande inside [ctrl + mouse_3 in creative, the ctrl + Pick_block] creat a basic command_lock not a nex command block.

      Steps to Reproduce:
      1.Create a command block in mod repeat,uncondtionnal,need_restone with the command "
      effect @a minecraft:speed 1 1"
      2.put a redstone_block beside this command_block
      3.the command_bloc work
      4.pick in creative the command block [ctrl + mouse3]
      5.destroy the 1st command_block
      6.put the block picked any other place
      7.put a redstone_block beside this 2nd command_block
      THAT DOESN'T WORK

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                scadiv Arnaud LEVEQUE
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: