Stop
Not a pause but the end of work: after stop the processor runs nothing
stop has no fields either, and it does the simplest thing that can be done to a processor:
it halts it.
Press “run” and wait: loops stays at one and afterStop never appears. The processor ran the
first line, hit stop — and that was that.
How it works
Section titled “How it works”stop puts the counter back on itself and gives up the tick — like wait, only for ever: the
time it is waiting for never comes. On the next tick the processor hits the same line again.
In the game such a processor looks switched off, and that is not a metaphor: it really does nothing until something wakes it from outside.
How to wake it
Section titled “How to wake it”| What to do | What happens |
|---|---|
| edit the program | the edit starts it over: variables cleared, counter at zero |
| “Edit…” → “Restart” | the same, without editing |
| demolish and rebuild | a new block with an empty program |
What it is for
Section titled “What it is for”There are exactly two cases, and both are rare.
The program has done its job. A one-off setup when a map starts, laying out a display,
handing out flags to units — things that make sense to do once. Without stop that would spin
sixty times a second for nothing.
The program has realised it cannot go on. The data does not add up, the block is missing, the link is wrong — stopping is more honest than carrying on doing who knows what. And the variables table then shows which line everything stopped at.
Unofficial fan project, not affiliated with Anuke. Mindustry sprites, fonts and translations © Anuke, used under GPL-3.0; Fira Code under OFL-1.1. Site code is GPL-3.0.