Guide

Game grab and throw systems explained

Harbor Siege's ranked meta after the posture patch still had a problem: the Sentinel tank archetype held block for 68% of duel time and won 54% of matches against aggressive rushdown characters. Posture breaks helped, but experienced Sentinels rolled away on break recovery and re-blocked before punish landed. Chip damage ticked health down slowly; duels still felt like attrition marathons.

The grappler answer was a dedicated grab and throw layer: proximity throws with a tech window, two command grabs that ignore block, wall-splat throws near arena edges, and a throw-break meter for defenders. Turtle win rate against grapplers fell from 54% to 37%; average throw attempts per duel rose from 0.1 to 1.4. This guide covers grab taxonomy, hitbox and priority rules, throw techs and breakaways, grappler kit design, the Harbor Siege refactor, a technique decision table versus block-only anti-turtle tools, pitfalls, and a production checklist.

What grabs and throws are

A grab is an attack that connects on a defender regardless of block state (for command grabs) or only when the defender is not blocking (for regular throws). A successful grab transitions both fighters into a paired animation — the throw — that deals damage, repositions characters, or sets up follow-up pressure.

Grabs exist because block and parry systems otherwise dominate defensive play. They are the structural counter to turtling: if blocking is always optimal, offense needs an unblockable-on-block option with clear risk. Grabs also interact with guard break — command grabs are one of five common break triggers, but throws add repositioning and stage control that posture breaks alone do not provide.

Unlike strike hitboxes, grab hitboxes typically check overlap with hurtboxes without a clash resolution against opposing attacks. Priority rules — grab vs strike, grab vs grab — must be explicit or players experience “random” whiffs.

Grab and throw taxonomy

Most combat games implement two or three of these categories. Mixing all six without tutorial support overwhelms new players.

Type	Block interaction	Typical use
Regular throw	Beaten by block; whiffs if defender holds guard	Close-range mixup after blockstring; frame trap bait
Command grab	Ignores block; loses to jump, i-frames, or outrange	Anti-turtle, anti-shield, grappler identity
Hit grab / command normal	Functions as strike until connect, then grab	Mid-range check with grab follow-up on counter-hit
Air throw	Only connects on airborne hurtbox	Anti-jump escape, juggle ender
Wall / corner throw	Variant animation splatting defender into wall	Stage control, extended okizeme
Grab super / cinematic	Often armor through strikes; ignores block	Meter spend, comeback tool, boss phase transition

Regular throws vs command grabs

Regular throws are fast (often 5–8 frames startup in fighters), short range, and lose cleanly to block. They create a rock-paper-scissors loop: strike beats throw (defender can jab), throw beats block (defender held guard too long), block beats strike. Without throw techs, this loop collapses into strike-only neutral.

Command grabs have slower startup (18–35 frames typical) and longer whiff recovery. They punish block-holding but lose to jumps, backdash, and preemptive strikes. Telegraph with distinct aura VFX, voice lines, or a two-phase wind-up so defenders can react with skill, not guesswork.

Grab hitboxes and priority

Grab detection differs from strike collision:

Proximity sphere — simple distance + facing check; common in action RPGs and brawlers.
Grab box overlap — dedicated grab hurtbox that must overlap defender hurtbox; allows directional throw variants.
State-gated grab — only connects if defender is blocking, airborne, or in a specific stagger state.

Priority when grabs and strikes collide

Document and teach these rules explicitly:

Interaction	Common resolution
Strike vs regular throw (same frame)	Strike wins; throw whiffs and enters recovery
Strike vs command grab (active frames overlap)	Strike wins if it lands before grab connect; grab wins if strike is absorbed by super armor
Grab vs grab	Tech (both reset) or priority by character weight / input timing
Grab vs jump	Grab whiffs; punishes slow command grabs
Grab vs i-frames	Grab whiffs during dodge invulnerability

Networked games should resolve grab connects on the server with the same hitbox snapshot used for strikes. Client-side grab prediction that the server rejects produces the worst class of combat feel bugs.

Throw techs, breakaways and escape tools

Throws without defensive answers become oppressive in neutral. Standard escape patterns:

Throw tech (throw break)

When a regular throw connects, both players enter a brief input window (often 8–12 frames). If the defender presses throw during the window, both characters bounce apart with no damage — a tech. Techs reward reaction and prevent infinite throw loops. Some games add tech chase: the attacker can input a follow-up on tech animation to catch a predictable escape.

Throw breakaway meter

Action games often give defenders a limited resource — one breakaway per round, or a meter that refills slowly — to escape command grabs or infinite juggle throws. Breakaways should have visible cost (meter drain, long cooldown) so attackers can condition defenders to spend it early.

Jump and roll escape

Slow command grabs are answered by dodge i-frames or jump if the grab does not catch airborne hurtboxes. Ensure jump-grab coverage is consistent: if only one character has an air throw, document it in movelist.

Tech windows interact with counter-attack design: a failed throw attempt is a long recovery punishable by counter-hit strings; a successful throw tech resets neutral with frame advantage to neither side.

Throw damage, positioning and okizeme

Throws are not only damage — they control space:

Corner carry — throw toward nearest wall; sets up wall-splat extended combos.
Midscreen reset — throw leaves attacker at +5 to +15 frames for meaty strike or command grab mixup.
Hard knockdown — defender cannot quick-rise; enables full okizeme setup.
Damage scaling — throws often deal fixed % health; cap throw loop damage per combo.

Wall-splat throws should have a distinct animation and a follow-up window (2–4 seconds before splat decay) so players learn stage positioning as a skill. Edge-guard design in arena fighters depends on throw routes that do not instantly ring-out at 0% damage unless that is an explicit design goal.

Grappler character design

A grappler archetype centers grab tools but needs neutral tools to get in range:

Approach — armored dash, projectile nullifier, or fast normal with plus frames on block.
Strike mixup — overhead/low or plus blockstring ending in throw threat.
Command grab suite — one fast short-range, one slow long-range with super armor.
Throw loop ender — high damage throw that does not reset to neutral (corner carry or hard knockdown).
Defensive weakness — weak backdash, large hurtbox, or poor anti-air so grapplers are not universal.

PvE grappler enemies should telegraph command grabs with a 0.8 s wind-up and a unique SFX so players learn jump or dodge answers before boss grabs become one-shot mechanics.

Harbor Siege grappler refactor

The Sentinel-turtle patch added grab systems alongside existing posture breaks:

Regular throw (6f startup): 8% health damage, tech window 10 frames, whiff recovery 22 frames.
Command grab “Iron Clasp” (24f startup): ignores block, 14% damage, splats to wall within 3 m, red hand VFX.
Command grab “Vault Toss” (32f startup, 2 m dash): catches jump if timed late; 11% damage, midscreen knockdown.
Throw break meter: one free breakaway per round; refills on taking 20% health damage.
Grappler roster slot (Brawler Kesh): both command grabs plus plus-on-block shoulder check approach.

Telemetry on 6,200 post-patch duels: throw attempts 1.4 per duel (was 0.1), command grab success rate 38% (target 35–45%), Sentinel turtle win rate vs grapplers 37% (was 54%), average duel length unchanged at 38 s. Players reported throws felt readable in post-match surveys (72% fair rating).

Technique decision table

Approach	Best when	Skip when
No throws	Ranged-only shooters, bullet heaven	Melee duels with hold-block defense
Regular throw only	Fighters with strong strike/block mixups	Heavy turtling with no tech tutorial
Command grab only	Boss anti-shield mechanics	Fast neutral without slow grab telegraphs
Throw + tech	Symmetric PvP fighters, arena brawlers	Single-player action with no defensive input
Throw + command grab + breakaway	Ranked duels, grappler archetypes	Mobile casual with no practice mode
Wall-splat throws	Arena with visible edges, stage control focus	Infinite flat arenas, ring-out at low %

Common pitfalls

Command grab without telegraph. 20-frame startup invisible to players feels like unblockable spam. Add VFX, SFX, and movelist frame data.
No throw tech. Regular throws become dominant once players learn strike loses to throw on block.
Grab beats every strike. If grab has armor and fast startup, neutral becomes grab-only. Slow command grabs or strikeable recovery fixes this.
Inconsistent air throw rules. Some moves grab airborne, others do not, with no visual difference. Tag moves in data and UI.
Throw loop infinite. Throw knocks down, meaty throw repeats. Add tech, scaling, or knockdown invulnerability.
Network grab desync. Client predicts throw animation before server confirms; always reconcile on authoritative connect.
PvE one-shot grab. Boss grabs at 100% health teach players grabs are unfair. Telegraph, allow dodge, or cap grab damage.
Ignoring stage geometry. Throws clip through walls or launch defenders off ledges without intentional ring-out design.

Production checklist

Document regular throw, command grab, and air throw separately in movelist data.
Define grab hitbox shape, range, and state gates (blocking, airborne).
Publish grab vs strike vs grab priority rules for internal QA and player wiki.
Implement throw tech window with input buffer matching strike standards.
Author throw breakaway meter with visible UI and refill conditions.
Tag command grabs with distinct VFX, SFX, and tutorial callouts.
Author wall-splat and corner throw variants with splat decay timing.
Cap throw damage per combo and per round for PvP balance targets.
Training mode: throw tech counter, grab range overlay, frame advantage on reset.
Server-authoritative grab connect with rollback or reconciliation policy.
Telemetry: throw attempts, success rate, tech rate, command grab whiff punish rate.
Playtest: can a defender hold block for 60+ seconds without grab threat? If yes, add command grab or posture break.

Key takeaways

Grabs exist to punish blocking and turtling — regular throws for mixups, command grabs for anti-shield.
Grab priority vs strikes must be explicit; ambiguous overlap reads as randomness.
Throw techs and breakaways prevent grab loops; every grab needs a defensive answer.
Harbor Siege cut Sentinel turtle win rate from 54% to 37% with throws, command grabs, and a breakaway meter.
Throws control space — wall splats and knockdown type matter as much as damage percentage.