I have been doing computational redstone, and the /tick command is extremely useful for working out issues in the things I make. Computational redstone can get extremely massive really fast, and it can be tricky to step through to the exact place i want sometimes.
My idea: Allow the tick command to listen to a block update at a specific coordinate on top of it's current functionality. Like, say i want to freeze the game and get to a point where a line of redstone wire switches on. It could be something like `/tick step until-update x y z` or `/tick sprint until-update x y z` to get to the exact point where that happens.
Please sign in to leave a comment.
0 Comments