Guide

Game okizeme, meaties and frame trap systems explained

Harbor Brawl's knockdowns looked dramatic — screen shake, a long hitstun tumble — but offense stopped there. Defenders mashed fastest wake-up attack and won because every meaty attempt was a raw guess on timing. Okizeme damage sat at 9% of round damage; most knockdowns were neutral resets with extra animation. Players described wake-up as “coin flip,” not a skill layer.

The refactor introduced explicit okizeme (oki) tools: meaty active-frame alignment against wake-up invulnerability, frame-trap strings that catch mashing, safe-jump timing off hard knockdowns, and fuzzy-guard options that respect delayed stand-up. Oki damage share rose to 31% without longer combos or higher single-hit damage. This guide covers oki taxonomy, meaty math, frame-trap construction, defensive counterplay, the Harbor Brawl wake-up refactor, a technique decision table versus damage-only knockdown tuning, pitfalls, and a production checklist grounded in frame data.

What okizeme is

Okizeme (Japanese: “waking attack”) is offensive pressure applied while the opponent is knocked down and must stand up. Unlike neutral footsies where both players can move freely, oki compresses the decision space: the defender has a small menu of wake-up actions (block, mash, reversal, delay, roll, jump) and the attacker chooses setups that favor or punish each option.

Good oki is not infinite pressure. It is informed pressure: the attacker sacrifices some options to condition the defender. A low meaty conditions stand block; a delayed meaty baits early mash; an empty jump baits reversal. The attacker's reward is continued advantage — another knockdown, corner carry, or resource drain — not guaranteed damage every time.

Core oki setup categories

Setup type	What the attacker does	What it tests
Meaty	Times an attack's active frames to hit on first wake-up frame	Reversal timing, fuzzy guard, delayed stand
Frame trap	Leaves a gap after a plus move; next hit catches button press	Mashing, auto-combo habits
Safe jump	Jump attack lands so late that reversals whiff before block	Wake-up DP, invuln reversal
Shimmy / empty jump	Approaches without attacking or feints throw range	Reversal, throw tech, panic block
Cross-up / ambiguous jump	Jump timing that changes block direction	Block direction read, auto-block systems

Oki interacts with high/low mixups at stand-up: a meaty overhead after two low meaties is stronger than the overhead alone because the defender's habit is already loaded.

Meaty timing and frame math

A meaty attack is timed so its active frames overlap the opponent's first actionable wake-up frames. The attacker benefits in two ways: more active frames connect (higher damage or stronger stun), and the move's recovery ends closer to the defender's blockstun end — often yielding plus frames on block that enable frame traps.

Meaty math uses knockdown duration, wake-up animation length, and travel distance. If a hard knockdown lasts 30 frames and stand-up animation is 4 frames before the defender can block, a jab with 3 active frames must start so that active frame 1 lands on frame 34 of the knockdown sequence. Designers publish oki charts per knockdown type: soft vs hard, face-up vs face-down, techable vs untechable.

Meaty variants designers author

True meaty — hits on earliest possible wake-up; beats slow reversals and lazy block.
Delayed meaty — intentionally late; baits early mash and reversal, then catches stand block.
Meaty throw — throw attempt timed in throw range at wake-up; beats hold-block, loses to reversal or jump.
Frame-kill meaty — uses a whiffed move or micro-dash to adjust timing without changing the meaty move itself.

Harbor Brawl added per-knockdown okiOffset tables: designers set frame-kill routes (dash, whiffed light) that align each character's kit to universal knockdown lengths. Without frame-kills, only characters with matching dash speeds could meaty consistently — a hidden roster imbalance.

Frame traps on wake-up and in strings

A frame trap is a sequence where the first move is safe enough that the defender wants to act afterward, but a gap in the string catches their button press. On oki, the classic pattern is meaty jab (plus on block) followed by a second jab or throw: if the defender mashes after blocking the meaty, the second attack counter-hits during their startup.

Frame traps require honest frame advantage numbers. A meaty that is only plus-one on block cannot trap a 3-frame jab unless the defender is already in recovery from a mistimed button. Traps that are minus on paper but work because players mash are lazy design — they collapse once the community learns the counter (hold block, then jab).

Building trap strings that stay fair

Publish advantage after meaty on block in training mode frame display.
Ensure at least one respect option beats each trap (delay, reversal with invuln, backdash out of throw range).
Vary gap length between trap beats so one counter does not shut down all oki.
Cap trap damage so a failed read costs less than a full combo — traps are mindgames, not execution checks only.

Frame traps overlap with counter-attack systems but are authored as strings, not global counter-hit flags. A trap is a designed gap; a counter-hit is often emergent from any plus situation.

Defensive tools: fuzzy guard, delay and reversals

Oki stays healthy only if defenders have structured answers. Without them, meaties become unstoppable and players avoid knockdowns entirely — shrinking the combat space you just built.

Common defensive answers

Fuzzy guard — hold down-back during knockdown, then switch to stand block one frame before meaty contact; avoids low meaties and high meaties that assume stand block on frame 1.
Delayed wake-up — extend lie-down animation (where your game allows) to dodge true meaty timing; loses to delayed meaty.
Reversal invulnerability — DP or get-up attack with i-frames; beats meaties and throws, loses to safe jumps and blocking.
Roll / tech — changes spacing and knockdown timing; must be readable and punishable on wrong read.

Harbor Brawl's wake-up refactor standardized fuzzy guard as a first-class input: defenders in knockdown state can hold a fuzzy block stance that auto-transitions to stand guard without releasing block. Telemetry showed fuzzy adoption correlated with longer rounds but higher rematch rates — players felt knockdowns were playable, not helpless.

Safe jumps and ambiguous oki

A safe jump is a jump attack timed so that if the defender reversals on wake-up, the reversal's active frames whiff while the jumper lands into block. Safe jumps require calculating reversal startup plus invuln length against jump arc and attack landing frame. Hard knockdowns with longer grounded time enable safer jump setups than soft knockdowns where the defender rises faster.

Ambiguous cross-ups use jump trajectories that look identical until the last frames when the attacker passes over the defender's head. Auto-block systems (common in casual fighters) need explicit cross-up detection windows; otherwise ambiguous oki becomes unfair rather than readable. Document which jump attacks are true cross-ups versus same-side jumps in your move list.

Harbor Brawl wake-up refactor

Before the refactor, Harbor Brawl used one universal knockdown duration and no meaty validation in training mode. Designers tuned oki by feel in isolation; online play exposed that dash-speed differences broke meaty routes for half the roster.

Changes shipped

Knockdown taxonomy — soft, hard, wall-splat, and slide knockdowns each with published oki frame budgets.
Frame-kill library — per-character micro-routes (dash, whiff, jump land) that align meaties without bespoke code per matchup.
Training mode oki overlay — shows meaty window, plus-on-block after meaty, and trap gap frames live.
Fuzzy guard input — standardized defensive option with clear animation tell for spectators.
Oki damage telemetry — tagged hits during knockdown advantage state; used to verify 25–35% target share.

Result: round length increased 8% (more decisions per knockdown) while rage-quit rate on knockdown-heavy characters dropped 14%. Oki became a readable layer instead of a frustration spike.

Technique decision table

Your situation	Prefer	Avoid
Fighting game with frequent knockdowns	Meaty tables + frame traps + fuzzy guard answer	Universal knockdown timer with no oki tools
Casual audience, low execution ceiling	Simple true meaties, clear reversal window, training overlay	Pixel-perfect frame-kill routes required to compete
Large roster with varied dash speeds	Per-character frame-kill routes to shared knockdown lengths	Assuming one meaty timing works for everyone
Defenders always mash on wake-up	Frame traps after plus meaties; delayed meaty baits	Infinite true blockstring with no respect option
Reversal-heavy meta	Safe jumps, empty jumps, delayed meaties	Only true meaties every knockdown
Action RPG with occasional knockdowns	One or two boss oki patterns with telegraphed escape	Full fighting-game oki depth on rare knockdowns

Common pitfalls

Meaty without plus-on-block. A meaty that is minus on block gives the defender their turn immediately — oki fails before traps start.
One knockdown duration for all moves. Launchers, sweeps, and throws need distinct oki budgets or meaty routes break.
Traps with no respect option. If blocking always loses to throw or trap, players avoid knockdown gameplay entirely.
Ignoring wake-up invulnerability frames. Meaties that hit during invuln feel broken; meaties that never threaten invuln end feel pointless.
Safe jumps that are not actually safe. Miscalculated reversal windows destroy trust — verify per reversal move, not averages.
Ambiguous cross-ups on auto-block. Without cross-up detection, same-side jumps read as unfair mixups.
Oki damage uncapped. Full combos off every meaty remove defender agency; oki should open sequences, not always end them.

Production checklist

Define knockdown types with grounded duration and tech rules.
Publish oki frame budgets per knockdown type in designer docs.
Build per-character frame-kill routes to align meaties on hard knockdowns.
Verify meaty plus-on-block in frame sheets before authoring traps.
Author at least two meaty timings (true and delayed) per key knockdown.
Implement fuzzy guard or equivalent delayed-block answer.
Validate safe jumps against every reversal in the roster.
Expose oki overlay in training mode (meaty window, advantage, trap gaps).
Tag oki-state hits in telemetry to measure damage share targets.
Playtest respect options: each trap family needs a documented counter.
Cap oki opening damage so knockdowns encourage reads, not helplessness.
Document cross-up vs same-side jump attacks in the movelist.

Key takeaways

Okizeme is knockdown offense that compresses defender choices into readable setups — meaties, traps, jumps, and shimmies — not random guessing.
Meaty timing aligns active frames with wake-up; plus-on-block meaties enable frame traps that punish mashing without removing block as an option.
Defensive tools (fuzzy guard, delay, reversal, roll) are mandatory — oki without answers feels unfair and shrinks knockdown usage.
Frame-kill routes let diverse rosters share knockdown lengths; without them, dash-speed differences silently break oki balance.
Harbor Brawl's oki overlay and fuzzy guard raised oki damage share to 31% while cutting rage-quits — transparency and defense made pressure fun.