So, let's say that we have a redstone block in the middle of nowhere and I want to power as many command blocks as possible using that one redstone block. No repeaters are allowed, and there are infinite space and redstone(but still, no repeaters). What is the maximum number of command blocks possibly powered by this singular redstone block? And, if you can find it, what is the layout of this efficient design?
-
Could you instead tell a command block to setblock a redstone block and then have another remove it?– PenguinCommented Apr 16, 2021 at 15:47
-
No, because I want this to be hooked up to a fast clock.– KorogueCommented Apr 16, 2021 at 15:48
-
1and that wouldn't work because...?– PenguinCommented Apr 16, 2021 at 15:49
-
also you might wanna consider repeating command blocks instead– PenguinCommented Apr 16, 2021 at 15:49
-
no, I don't wanna... wait! Chain command blocks! I'm dumb :(– KorogueCommented Apr 16, 2021 at 15:50
3 Answers
With chain command blocks, infinitely many, since you can just set them up back-to-back, and powering the first one triggers the whole chain (assuming the rest are set to not need redstone).
Without chain command blocks, still infinitely many, because you can invert a redstone signal twice to refresh its power. This is more or less that a repeater does, if you think about it - it's crafted from two RS torches. Without a repeater, you can cheat and just put down two NOT gates :P
Without those, you still have a lot of options for extending a redstone signal like probably using hoppers and comparators or something silly like that; I'm not too sure, but the above definitely works.
For what you want to do, chain command blocks are... probably what you want?
-
1
/fill 0 0 0 100 0 100 redstone_block
, there, 20,000 command blocks activated by command from one redstone block. And you can put as many minecarts with command block onto a single piece of activator rail.– SF.Commented Apr 17, 2021 at 3:37
If chain command blocks is not allowed either then the answer is still infinite. We can still move the redstone block to power the next command block. Besides, we can still use "execute if" to simulate chain command blocks.
If that is not allowed then we can still use the first command block to create more command blocks with the "require redstone" flag turned off. Naturally, these new command block would be configured to spawn more command blocks ad infinitum.
If using fill commands to move the redstone block is not satisfactory then we can still create a piston with a command block that will move the redstone block to the next command block and repeat ad infinitum.
The answer is simply infinity.
-
This sounds more like a "well technically.." answer. I might be mistaken, but the wording suggests that the application has no in-game value– user228576Commented Jul 8, 2021 at 7:55
-
Most of the proposed methods that I discussed have valid applications. Such as by passing fill limitations. The author did not state what the specific purpose was and therefore we cannot establish what would constitute in-game value for him. This was an honest attempt to address the question given specific parameters in absence of a stated purpose. Commented Jul 8, 2021 at 8:37
As a partial answer, I would put Redstone dust off the block and then have it power a command block that makes the signal stronger. This will allow you to power more command blocks than before.
-
? This doesnt really seem like an answer, but more of a suggestion for what the answer should have– PenguinCommented Apr 16, 2021 at 23:38