Timeline for Why remove redstone dust from my command block contraptions?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8 at 11:13 | history | edited | CommunityBot |
replaced https://minecraft.gamepedia.com/ with https://minecraft.wiki/w/
|
|
| Dec 29, 2023 at 11:48 | history | edited | Fabian Röling | CC BY-SA 4.0 |
repaired link
|
| May 6, 2020 at 15:50 | comment | added | Fabian Röling | Thanks, I added that to my answer. It was so long ago that I watched that video that I forgot that it was possible at all. That video is even included in one the playlists I linked here. :D | |
| May 6, 2020 at 15:50 | history | edited | Fabian Röling | CC BY-SA 4.0 |
looping possible with cmdBlocks
|
| May 6, 2020 at 11:46 | comment | added | MBraedley | It was a Slicedlime video from the 1.12 snapshots. You have some command blocks that conditionally clone themselves. The newly cloned blocks haven't been run this tick, so the loop continues to execute. | |
| May 6, 2020 at 7:20 | comment | added | Fabian Röling |
@MBraedley No, a command block at one position can only execute once per tick. Some of the things I've just tried: Setting it to auto:0 and auto:1 executes it in the next tick again, changing the direction does not schedule it again, pointing two repeatCMDblocks into one chain only executes that chain once, cloning a chain forwards multiple times does indeed work, but of course you then have many command blocks again.
|
|
| May 5, 2020 at 18:29 | comment | added | MBraedley | Actually, you can do loops with command blocks, it's just not nearly as elegant as using functions. I think it involves changing the output direction of a command block to end the loop, but it's been so long since I've watched the video demonstrating it that I can't be sure. It's also possible (and very easy) to run loops over multiple ticks, but that's obviously not what you meant. | |
| May 5, 2020 at 17:53 | history | answered | Fabian Röling | CC BY-SA 4.0 |