During emulation you can force a step active or inactive directly from the visual editor. This lets you jump into a specific branch without having to drive every preceding transition to get there.
A step forced active lights up exactly like a normally active step. On the next scan cycle the engine evaluates its outgoing transitions normally, so the program resumes standard token flow from that point.
Forcing a step active does not clear other active steps. If more than one step is active at the same time, the sequence behaves as if those steps were activated by normal divergence. Use this carefully when testing OR branches.