What I expected to happen was...:
Command Block would buffer, so commands could not be run too quickly. This would be similar to Dispensers and Pistons.
What actually happened was...:
Command Block can be activated as quickly as it can run commands. If setting a block adjacent to it as a block which produces redstone current, it will activate itself. If this is done by replacing the block currently in this location, it can be used to rapidly place Redstone Blocks, which can make commands run extremely fast.
Steps to Reproduce:
1: Obtain a Command Block. (/give @p 137 1)
2: Place it in an open space
3: Enter the command "setblock ~ ~1 ~ 152 0 destroy" into it
4: Power it from above
5: It will begin rapidly creating and destroying redstone blocks above it. When setting the redstone block, it becomes powered for a single instant, before it places another redstone block and reactivating itself. This cycles until the block receives a sustained signal to prevent it from detecting others. While allowing commands quickly should be kept, this quickly is definitely unintentional.
The above can be done without the block destroying particles and block items by changing "destroy" to "replace" and adding two command blocks adjacent to the redstone block which both set the redstone block space to air. It will still cycle as before.
Comments 6
I've been trying to think of a good word to describe it. Buffer is the best I have. Dispensers, Pistons, etc. buffer so you can't activate them too quickly/rapidly, buffers them. Command Blocks have no buffer, so they can go much faster than probably intended.
The reason I believe this might be unwanted is that other redstone-triggered blocks have a buffer or such to prevent them from activating too rapidly. I have found this useful for making rapid fire arrows, but considering how this can not only infinitely run but at extremely high speeds, it doesn't seem preferable with all their optimizations they are adding. I'd understand if they decide to keep it - Just seems like in theory this could end up being a bad thing.
Honestly, I wanted to try making pigs ride those arrows, but they died instantly, so I decided "I'll just make them invulnerable." without thinking about it too much. Long story short, I had to clear a TON of entities manually with MCEdit... Although launching tons and tons of villagers outside the loaded chunks and then flying over was amusing. Too many to kill manually, though. And a bit laggy.
This site is for bug reports only. Feature and improvement suggestions are not currently being tracked here. It can run commands infinitely fast in redstone terms.
I consider this unintentional and correctable due to the nature of redstone verses the results observed. Other activated blocks have buffers to prevent activation at this speed, and even before some were implemented could not be done at such a speed. This behavior definitely defies the logic presented by other blocks. I would find this invalid as a purposeful feature, but at the moment that has no confirmation.
Can you please clarify this report by following the Bug Report Guidelines Here. It is not clear what part of your report is a bug.