Joining the dots... The Mission System in Developer Articles Posted March 22, 2018 Wait, if it's truly an FSM with only one active node at a time, doesn't that mean that activating a "Catch All Node" should break the program and prevent it from continuing, because it can't fork the path into two simultaneously active nodes? But the main pathway does seem to resume afterward. How? Let's say you have a catch-all-node, that starts a chain of 2 other nodes, and then the path just stops without any mission end node or any explicit path linking back to the main program. It appears to return back to the main pathway after finishing that chain of 2 nodes, continuing from right where it got interrupted, as if it was returning from a subroutine. How does it remember where to go back to? Wouldn't a true FSM forget that? If the Catch-all-node behaves like a subroutine that returns to where it got called from, that wasn't made clear by the UI text explaining things.