Guide

Game wake-up and getup combat systems explained

Harbor Siege's first duel build treated knockdown as a timeout: the attacker backed off, the defender stood up with a generic rise animation, and neutral reset. Knockdowns felt like a random pause, not a payoff. Data showed only 11% of rounds included a meaningful interaction within three seconds of a floor hit — most damage came from standing exchanges. The refactor introduced a wake-up state machine with quick rise, delayed getup, directional tech rolls, and a single invincible reversal per round. Attackers gained okizeme tools: meaty lows, safe jumps, and throw beats on delayed wake. Knockdown share of total damage rose from 18% to 31% without increasing combo length.

Wake-up and getup systems govern what a knocked-down fighter can do while rising and how attackers pressure that vulnerable window. They sit between knockback (how you hit the floor) and standing melee (what happens after feet touch ground). Done well, knockdown creates a readable mind-game: defender picks among safe, risky, and deceptive rise options; attacker times pressure to cover each branch. This guide covers knockdown states, wake-up option taxonomy, frame advantage and okizeme, reversals and invincible rises, PvE vs PvP tuning, the Harbor Siege duel refactor, a technique decision table vs standing-only combat, pitfalls, and a production checklist alongside our parry and block and dodge roll guides.

What wake-up and getup mean

A knockdown occurs when a hit or force event puts a character into a grounded state: lying, crumpled, or sliding. Getup (or wake-up) is the recovery phase from that state back to a standing or actionable neutral pose. In fighting games the term oki (short for okizeme) describes attacker pressure applied during the defender's rise.

Wake-up design answers three questions:

When can the defender act? Fixed timer, button mash, or animation-driven wake frames.
What can they do? Block-only rise, attack, roll, reversal, or character-specific options.
Where do they end up? In-place rise, back roll, side tech, or corner trap geometry.

Without authored wake-up branches, knockdown is just a long hitstun with a camera cut — attackers learn to ignore it. With branches, every slam to the floor opens a second decision tree that rewards preparation on both sides.

Knockdown state machine

Production code usually models knockdown as a small finite-state machine (FSM) layered on your combat graph:

Airborne / hitstun — victim in juggle or knockback flight.
Hard knockdown — impact on ground; OTG (on-the-ground) rules may apply for follow-up hits.
Downed idle — lying state; duration sets minimum time before any rise input is accepted.
Getup branch — quick rise, delayed rise, roll, or reversal selected by input and timing.
Standing recovery — vulnerable frames after feet plant before full neutral (block, walk, attack).

Key flags to expose in data:

Hard vs soft knockdown — soft allows immediate air recovery or air tech; hard forces ground wake.
OTG eligibility — can attacker hit the body on the floor? Limits infinite loops.
Invincibility on wake — full, throw-only, or none; usually front-loaded on rise animation.
Corner push — does tech roll respect wall collision and leave victim in the corner?

Telemetrize transitions: time-in-downed, option distribution, and round wins conditional on who had knockdown advantage. If 90% of players pick one rise, your other options are decorative.

Wake-up option taxonomy

Quick rise (fast getup)

Minimal down time; victim stands in place with brief vulnerability. Best default for action games that want pace. Attackers answer with meaty attacks timed to hit on the first actionable frame.

Delayed getup

Hold down or delay button to extend lying time, then rise later than the quick option. Beats impatient meaties and jump-ins that assumed early wake. Costs corner position if the attacker can close distance during the delay.

Directional tech roll

Roll backward, forward, or sideways on wake with invincibility through part of the roll. Creates spacing resets and escape from corner oki. Forward roll can be punishable if the attacker reads it and whiffs a slow move into your recovery.

Reversal / wake-up attack

Invincible or armor startup move usable only while rising (classic “DP” or getup uppercut). High risk if blocked or baited; essential for fighting games so defenders are not helpless in oki. Cap uses per round or meter cost to prevent spam.

Block-only rise

Defender must hold guard during getup; no reversal. Simpler for PvE or casual modes. Attackers use throws or guard-break moves to punish passive rises.

Air recovery / air tech

After a soft knockdown or juggle end, victim flips upright in the air with brief invincibility. Distinct from ground wake but part of the same “recovery option” design space.

Okizeme: frame advantage and meaties

Okizeme is attacker pressure that covers multiple defender wake branches. The core timing tool is the meaty: an attack timed so its active frames overlap the defender's first vulnerable frames after rise.

Frame math (simplified):

Knockdown duration D frames until quick-rise action.
Attacker move with startup S and active window A.
Meaty hits if S lands so active frames cover frame D through D + A.

Common oki layers:

Meaty low — beats quick rise into attack; loses to delayed getup or jump.
Meaty throw — beats block-only rise; loses to reversal or jump.
Safe jump — jump attack that lands meaty then attacker blocks or evades reversal; beats delayed getup if timed.
Shimmy — walk forward then back to bait forward roll into whiff punish.

Publish oki setup tables in design docs: knockdown type × spacing × recommended meaty. QA should verify each setup on both quick and delayed wake. For combo routes that end in knockdown, see combo systems.

Reversals, invincibility and fairness

Reversal wake-ups exist so defenders are not stuck in infinite oki loops. Design constraints that keep them fair:

Distinct VFX and SFX — attackers must see reversal startup; no invisible invincible jabs.
Recovery on whiff — full combo punish if baited; reversals are gambles, not free escapes.
Resource gate — meter, once-per-round, or stamina prevents reversal spam in long PvE fights.
Throw immunity window — some games make throws beat reversal on wake to avoid rock-paper-scissors confusion; document clearly.

Interaction with super armor: armor on wake can feel fair in PvE bosses but oppressive in PvP unless heavily telegraphed and punishable on block.

PvE vs PvP tuning

Dimension	PvE bias	PvP bias
Down time	Short; keep action flowing	Long enough for meaty setups
Wake options	2–3 with UI prompts	4+ with strict frame data
Reversal	Generous i-frames vs boss oki	Punishable; meter-gated
OTG damage	Allowed for juggle fantasy	Often limited or scaled
AI oki	Boss uses 1–2 telegraphed meaties	N/A; human reads required

Harbor Siege duel refactor

The pre-refactor knockdown was a 45-frame lie-down with a single stand-up animation. Attackers had no frame advantage on wake; defenders had no mixup. Changes shipped in three passes:

Wake menu: quick rise (frame 28), delayed getup (hold to frame 42), back tech roll (i-frames 10–22), forward tech roll (spacing + punish risk).
One reversal per round: invincible uppercut frames 3–12 on rise; blockable; full punish on whiff.
Oki toolkit: three knockdown enders with documented meaty timings at near/mid/far spacing; training mode overlay shows “meaty window.”
Corner rule: back tech stops at wall; delayed getup becomes dominant option in corner — attacker must respect throw.

Post-patch, average duel length rose 8% but player satisfaction on knockdown interactions jumped 19 points in surveys. Spectator clarity improved: casters could call “delayed wake” and “reversal beat” with visible tells.

Technique decision table: wake-up systems vs alternatives

Approach	Best when	Watch out for
Full wake-up / oki layer	Fighters, duelists, competitive PvP, high knockdown rate	Frame data explosion; netcode sensitivity
Quick rise only + meaties	Fast brawlers, co-op horde modes	Shallow mind-games; oki becomes one timing
Stand-up invulnerability bubble	Casual action, mobile titles	Attackers ignore knockdown entirely
Executable oki (cinematic)	Story bosses, spectacle fighters	Not reusable in symmetric PvP
No knockdown (stagger only)	Shooters, continuous movement combat	Misses floor-game depth; see stagger guides

Common pitfalls

Invincible stand-up with no oki. Knockdown becomes a free reset; attackers avoid knockdown moves.
Identical timing on all wake options. Delayed getup must actually change meaty timing or it is useless.
Reversal beats everything. If reversal is safe on block, oki degenerates to guessing.
No training mode oki display. Players cannot learn meaty windows without frame overlays.
Roll through walls or allies. Tech roll collision must be explicit.
OTG infinite. Unlimited floor hits after knockdown break competitive integrity; cap OTG hits or damage scale.
Netcode desync on wake frame. Authoritative down timer on server; cosmetic roll on client.
Boss oki without telegraph. PvE meaties need wind-up; silent frame-perfect boss hits feel unfair.

Production checklist

Define hard vs soft knockdown and OTG rules in combat spec.
Build knockdown FSM with logged state transitions for QA.
Author at least two rise timings: quick and delayed.
Add directional tech rolls with i-frame table and wall collision.
Gate reversal with meter or per-round limit; document block punish.
Create meaty setup sheet per knockdown ender at standard spacings.
Training mode: show down timer, meaty window, and wake option on input.
Separate PvE and PvP down-duration config tables.
Telemetry: wake option %, oki damage share, reversal success rate.
Playtest: can attacker loop the same meaty forever? Add answers.
Accessibility: longer meaty windows in easy mode; visual wake countdown.
Regression-test after knockback or hitstun patches.

Key takeaways

Knockdown is a second fight. Wake-up options turn floor time into readable offense and defense.
Oki rewards preparation. Meaties, throws, and safe jumps cover different rise branches.
Reversals need teeth and risk. Invincibility without punish kills the mind-game.
Delay and roll change timing. Without timing variance, oki is solved in a week.
Publish frame data internally. Wake systems are unshippable without setup tables and training tools.