Of every TCF concept, this is the one that trips people up most. Get it right early and the whole framework clicks. Get it wrong and you'll fight the system for weeks.
🎯 The 30-second answer
A state is what your character is broadly doing right now. An ability is the specific thing it's doing within that state.
Attacking is a state. Light combo #2 is an ability. Dodging is a state. Forward dash and backwards roll are abilities. Idle is a state with no ability attached at all.
🧠 The mental model
Picture a character through a third-person camera. From that vantage point you can describe their behaviour at two levels of zoom:
Zoomed out — what is this character doing? Attacking, dodging, blocking, idle. Those are states. There are only ever a handful of them, and only one is true at any moment.
Zoomed in — with what move? A heavy overhead, a parry, a shield bash, a riposte. Those are abilities. There are dozens or hundreds of them, and they're contextual to the state.
A state hosts the abilities that make sense inside it. The Attacking state hosts every attack ability the character knows. The Dodging state hosts every dodge variant. The Idle state usually hosts no abilities at all — idle is just idle.
📊 Side-by-side
State | Ability | |
|---|---|---|
Scope | Broad — overall character behaviour | Specific — a single move or effect |
Active count | Exactly one at a time | One active, plus many passive |
Lives on | Character/Pawn/Actor | Character/Pawn/Actor |
Driven by | Input, events, anim notifies | Almost always fired from inside a state |
Has cooldown? | No | Yes (built-in) |
Has interrupt/cancel? | No (state ends when superseded) | Yes (interrupt and cancel are first-class events) |
Passive variants? | Yes (passive states, used rarely) | Yes (passive abilities, used commonly for buffs) |
Inherits from |
|
|
🎮 Concrete examples
The clearest way to internalize the split is to map a few real combat moments:
A normal attack press. Input asks the State Manager: can we enter the Attacking state? If yes, the Attacking state starts and immediately fires the appropriate ability — say, Light Attack #1. The state is one; the ability is one of many.
A combo. The player presses attack again mid-swing. The Attacking state is already active, so the State Manager doesn't change states. The state itself decides whether to fire Light Attack #2 as the next ability or Light Attack #1 again. The state stays the same; the ability changes or gets retriggered.
A deflect. The Deflecting state activates. Inside it, a Deflect ability fires with its own VFX, sound, and timing window. When the deflect window closes, the state ends, the ability ends, and the character returns to Idle.
Walking and sprinting. Both are states. Neither has an ability attached. Movement is broad enough that no further specificity is needed.
🔁 The relationship
Three things to remember about how the systems hand off to each other:
States usually fire abilities. Abilities almost never fire states directly.
A state ending automatically ends its active ability.
Passive abilities don't care about states — they keep running through state changes.
🤔 When in doubt
Ask yourself: can I describe this with a single broad verb? If yes — attacking, dodging, blocking, executing — it's a state. If you'd describe it with a noun or specific verb phrase — light attack, heavy launcher, sidestep dash, mid-air slam — it's an ability.
Ask yourself: would more than one of these ever happen at once? If yes, it's probably a passive ability. If no, it's a state or an active ability.