Hi @Nawrot, such a control flow node would effectively be equivalent to an general purpose goto. While it may be interesting and I agree that it would simplify large FSMs, its usage would not be restricted to FSMs. If Epic wanted to have this kind of flow control primitive, I believe they would have added it themselves long time ago. I can imagine they won’t do that because it’s a feature that can too easily be misused. Please notice that your example could be easily approached with a WhileLoop node, but you actually can’t do that because the compiler (incorrectly, IMHO) detects an infinite loop… I don’t know the blueprint compiler internals well enough to exclude that, if I were to implement the feature as you described it, it wouldn’t actually be unusable because of automatic infinite loop checks.