Turn Order & Action Queue Visualizer

Tool · state machine + ActionQueue · step-through mode

See the DuelController state machine from Module 5 in action. Step through a duel one transition at a time. Watch the ActionQueue fill and drain. This is the mental model you want before your own implementation starts feeling like a mystery.

What you're seeing

• The state machine on the left is the exact enum from scripts/duel_controller.gd in Module 3. Only one state is active at a time.
• The action queue on the right is the ActionQueue from Module 5. Actions drain one at a time; each awaits its own animation.
• The log prints state transitions and action resolutions. In Godot, these would be print() lines — they're invaluable for debugging a new state machine.

Key insight

Notice how the state machine is high level — 7 states capture the whole duel. The action queue is low level — it sequences the individual animations and damage applications within a state. Don't conflate them. One answers "where in the flow are we?", the other answers "what's happening right now?"