-
Bug
-
Resolution: Invalid
-
None
-
Minecraft 1.8.7
-
None
-
Unconfirmed
When I take the command "/testfor @p[-23,10,0,65536]" and put into a command block constantly being activated from a /fill clock, it reduces the tick speed of MineCraft drastically, leaving the frame-rate at it's normal rate, 40-60 FPS. Normal tick speed: Four ticks=About a second. Tick speed after /testfor @p[-23,10,0,65536] is constantly being run: Four ticks=About four seconds.
What I expected to happen was...:
The tick speed remains the same.
What actually happened was...:
Tick's time taken to run is multiplied by four.
Steps to Reproduce:
1. Type "/give @p command_block" and place it on the ground.
2. Program that command block to run "/fill ~ ~1 ~ ~ ~1 ~ air"
3. Place a command block two blocks above the first command block, as shown in Picture One.
3. Program the second command block to run "/fill ~ ~-1 ~ ~ ~-1 ~ redstone_block"
4. Place a redstone block inbetween the two command blocks.
5. Break the redstone block, if it remains, the clock is working. If it goes away, the clock isn't working.
6. Place a command block adjacent to the redstone block.
7. Program the third command block to run "/testfor @p[-23,10,0,65536]"
8. Voila!
Steps to check tick speed:
1. Place three redstone repeaters in a line in which they activate each other, as shown in Picture Two.
2. Set all three redstone repeaters to take the longest amount of time, or the fourth setting.
3. Place a redstone torch at the beginning of the redstone repeater line.
4. Check how long it takes normally to get to the end.
5. Reproduce the bug.
6. Destroy the redstone torch.
7. Check how long it takes for the repeaters to unpower.
Note: The command actually works.