Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- [3:05:57 PM] Searge: ok, so let's use CB = command_block, CCB = chain_command_block and RCB = repeating_command_block
- [3:06:26 PM] Searge: place a CB or RCB and feed it into a few CCB
- [3:06:38 PM] Searge: then place a redstone block next to the CB/RCB
- [3:07:23 PM] Searge: this happens:
- [3:08:54 PM] Searge: assuming CB/RCB was not powered already, the CB/RCB will be scheduled to execute next tick and the chain of CCB is travelled along and each CCB that doesn't have an execution tick scheduled already will be scheduled to also run the next tick (same time as CB/RCB)
- [3:09:11 PM] Searge: now next tick starts...
- [3:10:16 PM] Searge: CB/RCB is being run, it will execute its command, in case of RCB immediately schedule to execute again next tick, then the chain is travelled along and all CCB are also schedule to run next tick
- [3:10:40 PM] Searge: only then are all the CCB in that chain executed (still in the same tick as CB/RCB)
- [3:11:06 PM] Searge: CB -> execution ends because everything only runs once
- [3:11:47 PM] Searge: RCB -> repeat the whole execute RCB, schedule RCB, traverse CCBs, execute CCBs
- [3:12:22 PM] Searge: as you can see, the initiator (CB/RCB) runs before the next ticks are scheduled
- [3:12:34 PM] Searge: ^ use that for advanced contraptions
- [3:17:02 PM] Searge: changing the powered tag does not automatically schedule execution ticks
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement