Guide

Game tick throw systems explained

Harbor Brawl's grappler patch shipped strong grab and throw tools and a working throw break layer — yet ranked throw-loop win rate still sat at 61%. Telemetry showed the problem was not raw throw damage; it was tick throw conversion. After a plus-on-block light jab, grapplers walked forward and threw before defenders could jump, backdash, or mash a 3-frame normal. Jump attempts ate throws during jump startup; backdash lost to forward walk plus throw range. Neutral looked fair on paper; blockstring endings were a trap.

The refactor authored explicit tick throw windows: frame-advantage thresholds after specific normals, jump-invulnerability during the first airborne frames, kara tick routes with readable startup, and defender escape tools tied to input buffering. Throw-loop win rate fell from 61% to 44% without lowering throw damage. This guide covers tick throw taxonomy, plus-frame math, jump startup vulnerability, kara tick and shimmy interaction, defender option tables, the Harbor Brawl refactor, a technique decision table versus shimmy-only or grab-only pressure, pitfalls, and a production checklist.

What a tick throw is — and what it is not

A tick throw is a throw attempt timed immediately after an attack that leaves the attacker at frame advantage while the defender remains in blockstun or a short recovery state. The name comes from “ticking” the defender with a fast normal, then throwing before they can act. It is not the same as:

Shimmy — walk-back bait that punishes whiffed throw techs; spacing changes, not plus-frame coercion. See shimmy pressure.
Command grab — anti-block grab with its own startup and whiff risk; tick throws usually use regular proximity throws after plus lights.
Frame trap — baits a button during a gap; tick throws punish defensive options (jump, backdash) rather than mashing.

Tick throws sit at the intersection of blockstring pressure, throw mixups, and frame-data tuning. They are strongest when a character has reliable plus lights, forward walk speed, and throw range that exceeds the defender's backdash distance during the tick window.

Plus-frame math: when tick throws become inevitable

Frame advantage after block is the binding constraint. If a jab is +3 on block and throw startup is 5 frames, the attacker needs 2 frames of walk before throw active frames — but the defender needs 4 frames to jump (typical jump startup) or 3+ frames to backdash. The throw wins if walk speed closes proximity during those frames.

Defender option	Typical startup	Vulnerable to tick if plus ≥
Jump (no pre-jump invuln)	4 frames	+2 with walk + 5f throw
Jump (with 3f pre-jump invuln)	4 frames, invuln frames 1–3	+4 with walk + 5f throw
Backdash	3–5 frames before movement	+3 with forward walk
3-frame normal	3 frames	+1 if tick gap ≤ 2f
Throw tech (buffered)	Tech window dependent	Only if throw loses to tech priority

Designers should spreadsheet every plus normal in a blockstring against defender option tables. A single +4 light at the end of a string can convert 70%+ of blocks into throws if jump lacks early invulnerability and throw range exceeds backdash escape distance.

Tick throw taxonomy

Standard tick throw

Plus normal → forward walk (1–3 frames) → throw. The simplest loop. Tuning knobs: plus frames on the normal, throw startup, throw proximity box width, forward walk speed, and whether blockstun ends before or after the walk input registers.

Kara tick throw

A special or normal with forward movement during startup is canceled into throw before active frames, sliding the attacker into range with less visible walk. Kara ticks are harder to react to but more readable in replay if cancel windows flash. Pair with kara cancel systems for consistent displacement curves.

Tick command grab

Some games allow command grabs immediately after plus lights. These beat block but lose to jump if jump invuln starts early enough, and lose to fast jabs on whiff. Use sparingly — they remove the strike-throw mixup layer and feel oppressive when plus frames are generous.

Multi-tick chains

Repeated jab → walk → jab → throw sequences that condition defenders to stop jumping. Each tick resets blockstun and erodes mental stack. Cap chain length or add gravity scaling on repeated throws to prevent infinite loops.

Jump startup and the invulnerability question

Jump startup is the main counterplay to tick throws — if it works. Three design patterns appear across the genre:

No pre-jump invuln — jump is throw-vulnerable until airborne. Tick throws dominate; defenders must backdash or tech.
Partial invuln (1–3 frames) — first jump frames are throw-immune. Requires plus frames high enough that walk + throw cannot beat invuln end. Most tournament fighters use this band.
Full throw immunity on jump input — jump always beats throw if input on first actionable frame. Tick throws collapse unless ticked normals are slow enough that mash jabs beat throw startup instead.

Harbor Brawl added 3-frame pre-jump throw invulnerability and reduced jab plus from +4 to +2 on the grappler's fastest tick normal. Jump escape rate after tick setups rose from 12% to 38% without buffing jump damage or air normals.

Defender option select table

Defenders need at least two viable answers per tick setup or the loop becomes deterministic. Author responses into buffer rules:

Input (buffered)	Beats	Loses to
Jump on blockstun end	Throw (with invuln)	Meaty air-to-air, delayed high normal
Throw tech	Throw	Shimmy, strike meaty
3-frame jab	Slow throw startup	Frame trap gap, plus meaty
Backdash	Short throw range	Forward walk tick, low reach
Reversal (invuln)	Meaty throw and strike	Block, baited whiff punish

If every row's “loses to” column points to the same attacker option, the tick loop is broken. Spread counterplay across strike, throw, and movement answers.

Harbor Brawl refactor: from 61% to 44% throw-loop wins

Before the tick-throw pass, grappler telemetry showed:

71% of plus-light blockstring endings converted to throw within 8 frames.
Jump attempts during tick setups succeeded 12% (no pre-jump invuln).
Three-throw rounds: 34% of grappler round wins.

Changes shipped:

3-frame pre-jump throw invulnerability on all characters.
Grappler fastest tick normal: +4 → +2 on block.
Throw proximity box narrowed 12% at max range tick distance.
Kara tick from slide special: cancel window visible 2 frames, throw startup +1.
Second throw in same knockdown sequence: 20% damage scaling (was 0%).

Post-patch: throw-loop win rate 44%, jump escape 38%, three-throw rounds 11%. Grappler pick rate stabilized at 14% top-500 (was 19%). The character stayed viable; deterministic tick loops did not.

Technique decision table: tick throws vs alternatives

Pressure tool	Best when	Weak when	Skill floor
Tick throw loop	Grappler with plus lights, long throw range	Jump invuln, short throw whiff punish	Low execution, high matchup knowledge
Shimmy walk-throw	Defenders over-tech, respect throw	Passive block, walk-back meta	Medium spacing reads
Frame trap string	Defenders mash buttons	Patient block, jump escape	Medium frame-data knowledge
Strike-throw mixup (no plus)	Mid-range neutral, stagger pressure	Defenders with fast 3f normals	High timing variance
Command grab alone	Respectful block, no jump habit	Jump, backdash, fast jab	Low, but high whiff risk

Use tick throws as one layer in a grappler kit — not the entire win condition. Pair with high/low mixups and okizeme so defenders cannot solve neutral by holding back and teching.

Pitfalls

Plus lights too generous — a single +5 jab enables tick throws on every character archetype, not just grapplers.
No jump invuln against throws — forces jump to lose; new players quit before learning tech timing.
Throw range exceeds backdash at all tick distances — removes spatial counterplay.
Kara tick invisible — if cancel into throw has no distinct animation, defenders cannot learn spacing limits.
Ignoring throw scaling on chains — infinite tick loops feel cheap even when breakable.
Same tick timing online and offline — rollback may shift walk-input registration; test tick windows at 100+ ms RTT.
Tick throws without strike threat — defenders hold block forever if only throw and jab threaten; add frame traps and overheads.

Production checklist

Spreadsheet plus normals vs jump, backdash, jab, and tech escape tables.
Set pre-jump throw invulnerability (recommend 2–3 frames minimum).
Cap throw proximity at max tick walk distance or require kara for long range.
Add damage scaling on repeated throws in one knockdown sequence.
Expose tick window in debug overlay (plus frames remaining, throw range ring).
Telemetry: throw conversion rate after plus normals, jump escape rate.
Validate kara tick cancel windows are visible in replay slow-motion.
Test tick loops at high rollback RTT against buffered defender OS.
Pair tick pressure with at least one non-throw knockdown threat.
Regression-test throw tech priority after tick throw connects.

Key takeaways

Tick throws exploit plus-frame advantage to throw before jump, backdash, or jab can execute — they are frame-data problems, not raw damage problems.
Pre-jump throw invulnerability and plus-frame caps are the primary designer levers; narrowing throw range is the spatial lever.
Defenders need at least two viable answers per tick setup or the loop becomes deterministic.
Harbor Brawl cut throw-loop win rate 61%→44% with 3f jump invuln, +2 cap on tick jab, and throw chain scaling.
Tick throws complement shimmies and frame traps; they should not replace the full strike-throw mixup toolkit.