Guide

Game divekick attack systems explained

Harbor Brawl's rushdown roster leaned on full-hop jump-ins until telemetry showed defenders blocking high 71% of the time at mid-screen. The combat team added a divekick layer to two characters: a shallow diagonal descent with a crouching hurtbox that slips under standing anti-air normals. Low-profile confirm rate rose from 19% to 47%, but only after the team tied each divekick variant to explicit landing recovery tiers and angle caps. Without those guardrails, early prototypes let players cross the screen in eight frames with no whiff punish.

A divekick is an aerial attack that moves the character downward and forward (or backward) on a fixed or input-scaled trajectory. Unlike a standard jump normal that peaks then falls, divekicks commit to diagonal descent early, trading vertical range for speed and a low approach profile. They power rushdown mixups, safe jumps, and crossup angles when paired with tiger knee inputs. This guide covers trajectory taxonomy, frame and hitbox phases, variable-height routing, pressure and oki handoff, anti-air counterplay, the Harbor Brawl refactor, a technique decision table, pitfalls, and a production checklist.

What makes an attack a divekick

Not every downward aerial is a divekick. Designers usually tag moves with a divekick flag when they share a bundle of properties:

Diagonal velocity — horizontal and vertical speed applied on startup; the character does not float at jump apex before attacking.
Low hurtbox during descent — crouching or airborne-low collision capsule that ducks under standing AA normals.
Grounded landing state — touchdown ends the move into a standing or crouching recovery window, not a full jump landing with universal landing lag (unless you deliberately blend both).
Angle constraints — min/max descent angle so players cannot steer into broken cross-screen routes.

Divekicks sit between grounded dash approaches and full jump-ins. They answer the design question: “How does rushdown cross mid-screen without eating a rising AA every time?” The cost is predictable: long recovery on whiff, vulnerability to low attacks on landing, and limited conversion if the defender blocks.

Trajectory taxonomy

Trajectory shape drives which defenders can answer and which mixups follow. Common families:

Fixed-angle divekick

One descent vector regardless of input timing (e.g. 45° forward-down). Easiest to balance and teach; spacing is purely positional. Weak to pre-placed AA at the intercept point because timing is deterministic.

Variable-height divekick

Input timing after jump squat selects shallow vs steep angle — the same tiger-knee pipeline as instant-air specials. Late input yields a shin-height kick that barely clears the ground; early input yields a head-height dive that still descends but stays airborne longer. Variable height is the core mixup: defenders cannot hold one block height.

Back-turn and crossup divekick

Diagonal toward or through the opponent's back switches facing mid-arc. Requires explicit crossup rules (which side block applies, pushback on block). Pair with crossup protection windows documented in your combat spec.

Hover or stall divekick

Brief hang before descent (one to three frames) sells overhead ambiguity with jump normals. Use sparingly — stall frames stack with tiger-knee height variance and explode test matrices.

Document each variant in data: angle_deg, speed_px_per_frame, min_height, max_travel, and whether velocity overrides gravity for the active window.

Frame data and hitbox phases

Divekicks compress the jump arc into three production phases:

Launch — jump squat (if any) plus first frame velocity applied. Tiger-knee cancels shorten squat to one frame; document whether divekick can be TK'd from a empty jump.
Active descent — hitbox active for N frames along the vector. Multi-active divekicks (leg extended throughout) need hitstun decay or scaling caps to avoid infinite low confirms.
Landing recovery — grounded frames after touchdown: plus on block, neutral, or minus. Whiff recovery when the divekick travels past the opponent is often longer than block recovery to reward spacing reads.

Hitbox placement matters as much as frame data. A divekick that only hits below the waist forces crouch-block; one with a late high extension becomes an overhead on steep angles. Debug-draw hurtbox height during descent — if the hurtbox pops to standing height on frame 1 of active, standing AA will clip it and the move fails its design role.

Priority flags interact with AA systems: some games give divekicks low_profile (immune to standing AA) but lose to crouching AA or invincible reversals. Others use height-tier trades. Pick one ruleset and apply consistently.

Pressure, mixups, and oki handoff

Blocked divekicks should feed your oki layer without becoming infinite pressure:

Frame advantage tiers — shallow divekick −2 on block; steep divekick −6. Different angles, different follow-ups.
True blockstring vs reset — only the shallow variant links to fast lows; steep variant resets to neutral or tick throw range.
Empty divekick — jump without triggering descent baits AA; landing low catches reversal whiff. Same conditioning as empty hop.
Divekick into special cancel — on hit only, with scaling bump; on block, cancel disabled to prevent safe chip loops.

Rushdown characters use divekicks to alter approach timing: the defender sees jump startup (same as empty jump) but must react to angle. That shared startup is the mixup — not hidden animation swaps.

Anti-air counterplay and defensive answers

Divekicks must lose to prepared defense or they replace neutral:

Crouching AA — low hitbox reaches diagonal path; primary answer when low_profile ignores standing AA.
Invincible reversal — beats active descent if invuln overlaps intercept frame; whiff punishes empty jump conditioning.
Low poke on landing — if divekick recovery is −8 or worse, 2LK beats re-approach. Test at max travel whiff distance.
Anti-air projectile — vertical or diagonal shot clips steep angles before active frames; loses to shallow shin divekicks that skim the ground.
Throw on landing — divekicks are often throw vulnerable on touchdown unless tagged throw-invulnerable for first N recovery frames (use sparingly).

Telemetry: track divekick attempt rate, confirm rate, and AA punish rate separately. High attempt + low punish means AA answers are undertuned; high punish + low attempt means the move is dead.

Worked example: Harbor Brawl rushdown refactor

Problem. Two rushdown characters shared identical full-hop jump-ins. Defenders crouch-blocked into plus frames; rushdown win rate at mid-screen stalled at 44%. Playtests showed players wanted a low approach but abused prototype divekicks with no angle cap (cross-screen in 8f).

Refactor steps.

Angle table: shallow 25° (shin, max travel 280px), medium 40°, steep 55° (head-height, max travel 180px). TK timing maps to row.
Hurtbox: crouching capsule 48px tall during active; standing hurtbox forbidden until landing recovery frame 1.
Priority: low_profile vs standing AA; loses to crouch AA and invincible DP on trade.
Recovery: block −3 / −5 / −7 by angle; whiff −18 uniform; landing cancel into dash only on hit.
Crossup: steep angle only; pushback on block prevents same-side infinite.

Outcome. Low-profile confirm rate 19% → 47%. AA punish rate on divekick attempts stabilized at 31% (target band 28–35%). Full-hop jump-in rate dropped 11 percentage points as players routed into angle mixups — intended rushdown texture without deleting jump offense.

Technique decision table

Design goal	Best approach	Why not jump-in only?
Beat standing AA at mid-screen	Low-profile divekick with crouch hurtbox	Jump normals peak at AA height.
Approach without full jump arc	Fixed-angle shallow divekick	Full jump telegraphs descent timing.
High/low mixup after jump startup	Variable-height TK divekick	Single-angle divekick is readable.
Safe jump setup	Steep divekick with jailing follow-up	Raw jump-in minus on block is punishable.
Crossup offense	Steep back-turn divekick + pushback rules	Ground dash crossup lacks airborne ambiguity.
Punish whiffed divekick	Low poke at max travel recovery	DP only works if defender pre-read angle.
Teach new players	Two-angle divekick (shallow + steep)	Five TK tiers confuse without UI feedback.
Zoner neutral check	Projectile AA + standing poke	Divekick should not invalidate zoning at far range.

Common pitfalls

No travel cap — diagonal speed without max range crosses screen faster than grounded movement.
Standing hurtbox on descent — defeats the purpose; standing AA clips every attempt.
Plus on block shallow divekick — creates infinite low pressure with no meter cost.
Identical recovery on hit and whiff — removes spacing reads; whiff must hurt.
Ignoring crouch AA — if divekick beats all AA, defenders have no grounded answer.
Steep angle without overhead tag — players expect high block; ambiguous body hurtbox feels unfair.
TK divekick from zero squat — instant cross-screen; require minimum 2f squat or hop.
No empty-jump counterpart — if every jump is divekick, defense holds low forever; empty jump must bait.
Crossup without pushback — same-side block into re-divekick loop.
Testing only point-blank — max-travel whiff recovery breaks at screen edge.

Production checklist

Tag divekick moves with angle, speed, max travel, and low-profile flags in combat data.
Map tiger-knee timing windows to angle tiers; document in movelist.
Debug-draw hurtbox height every active frame; verify crouch capsule under standing AA.
Define AA priority vs standing, crouching, and invincible answers.
Publish block advantage per angle; verify no plus-on-block infinite routes.
Measure whiff recovery at max travel and corner spacing.
Test crossup variants for facing, block direction, and pushback.
Pair with empty jump and full-hop normals sharing jump squat startup.
Telemetry: attempt rate, confirm rate, AA punish rate, average travel distance.
Playtest rushdown vs zoner at three screen positions after each balance pass.

Key takeaways

Divekicks are diagonal descent attacks with low hurtboxes that slip under standing anti-air and rush mid-screen.
Variable height via tiger-knee timing creates high/low mixups without hiding startup animation.
Angle caps, travel limits, and whiff recovery prevent cross-screen abuse; crouch AA and landing lows are the intended counters.
Harbor Brawl raised low-profile confirm rate from 19% to 47% with a three-tier angle table and uniform −18f whiff recovery.
Divekicks complement — not replace — jump-ins, empty hops, and grounded footsies in rushdown neutral.