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

Redstone Clock malfunctions when connected to a /kill @e {r=100000,type=entity}

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • None
    • Minecraft 1.7.5, Minecraft 14w11b
    • None
    •  Windows 8, 1.7.0_45
    • Unconfirmed

      Put the summary of the bug you're having here

      *What I expected to happen was: Killing the selected entity within the radius of 100,000 blocks outside the command block

      *What actually happened was: The redstone clock froze and was unable to restart the clock until a few seconds later. I took off the redstone connecting the clock to the command block and it functions. I attached the redstone dust between the gap and the bug triggered again.

      Steps to Reproduce:
      1. Create a repeating redstone clock
      2. get a command block and place it down on a floor (I put mines down on a stone floor.
      3. Write (/kill @e [r=100000,type=ex Silverfish]

      4. When the redstone clock is at least one tick per second, connect the clock to the command block with the /kill command written in step 3
      5. Perfect, my redstone clock stopped working

            Unassigned Unassigned
            MCintelligence Destin Cloudius
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: