Flip Flop
Overview
Flip Flop takes the input flow and toggles it between two output paths. Each pulse of the input causes an inversion.
Using this with an event that happens each frame, such as Event Tick, will cause an inversion on every frame.
Limitations
This node will not work correctly inside Functions, Macros, and Collapsed Graphs.
Since the state of the node is held internally, the only place it will work is in a top level Event Graph.
This seems to have been a limitation from the start.
There are, however, ways to accomplish the same effects while still using blueprints.
Blueprint Alternatives
This method is very similar to the C++ implementation. A branch node handles the execution flows while an inverting boolean drives the branch state.
If flexibility is needed, you can control when the inversion happens by relocating the NOT and SET nodes elsewhere.

Examples
Input Toggle
Pulses from a Toggle Input are switched with the Flip Flop and routed to the current pin.



