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
Attachments
Comments 5
Maybe you are causing so much lag by killing all the silverfish in a that large area that the clock seems to freeze whilst you are actually delaying ticks.
I think you are delaying ticks by letting Minecraft calculate and execute a command with such a huge effect as it can't do extremely much at a time.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Unable to reproduce.