@Unisonkid
A couple of things to consider:
It is often better to have multiple simple FSMs than one complex FSM. If a State is doing X and also doing Y only if Z, it's a good indication that Y should be it's own State, maybe in a separate FSM just managing that state. For example maybe you have a Rotation FSM that just manages rotation.
Or, another option, you can run through multiple states in a single update. So you can do X in one state, test a condition, then do Y in another state and loop back to the X state with a Next Frame Event. That way you can loop through a whole set of decisions and states in a single update. Think of a flow chart where each action and decision is broken down into a single block.
Both of these strategies keep the logic explicit in the graph, instead of hiding an important behaviour switch in the action stack. Does that help any? I'll try to document these strategies on the wiki to make them clearer.