Match / Clear Merge Units Dodge / Avoid Runner Shoot / Aim Combat Turn‑Based Duel Placement / Building Choice / Strategy Physics Puzzle Progression Simulation Timing

Dodge / Avoid

Survive under continuous pressure and spatial constraints; the core revolves around hit detection, windows, and rhythm.

What is it

Hazards keep flying at you and your job is to stay alive — bullet-hell shooters, Flappy Bird, and dodgeball-style games are all built on this.

How it plays

You drag your character through a storm of bullets, weaving between them; the split second where one grazes past without killing you makes your heart skip — that "so close" thrill is the signature move.

Why learn it

It is the purest sample of "difficulty as rhythm" — if you want to learn how to make players tense without feeling cheated, start here.

Dodge play breaks "survival" into a chain of readable, moment-to-moment judgments: every hazard has a telegraph, a trajectory, and a hitbox, and every dodge immediately reports its outcome and its reason. The hard part is not the dodging — it is the credibility and forgiveness of the judgment: the gap between hitbox and visual circle is your thrill budget, and invincibility frames plus graze feedback decide whether a failure is learnable. The fairness players feel is built from these invisible judgment-engine details.

Why This Mechanic Matters

For Players

Dodging feeds a safe craving for danger — a bullet grazing past without killing you gets converted by the brain into pure thrill. Forgiveness windows and graze bonuses mass-produce that moment, letting players harvest small wins swinging between "I almost died" and "I can’t believe I didn’t."

For the Ecosystem

Bullet-dodging is one of the lowest-barrier forms in action gaming: one finger, ten seconds a run, naturally suited to fragmented time and short-video sharing.

Transferable Craft

Learn dodge play and you learn pressure-curve and forgiveness engineering — density ramps, hitbox scaling, telegraph lead time — knobs you will keep turning in runners, shooters, and boss fights.

Play Behavior

Dodge / Avoid

Gameplay Features

Numbers Timed

Complexity

Beginner → Advanced

Learning Goals

Beginner: understand the minimal survival loop — spawn → telegraph → move → judge → feedback — and reproduce one graze judgment in the demo
Intermediate: write the full hit-judgment contract (hitbox, graze zone, invincibility frames, respawn protection) and tune forgiveness parameters that keep beginners from churning
Advanced: design the pressure curve (density × speed × time ramp structure) and verify difficulty health with graze rate and survival-time distribution

Core Patterns

Action

② Instant Playable Demo

Dodge / Avoid Demo

Loading game…

Rule Hints

Rule: Hazard generation → Warning/trajectory → Player movement → Hit detection (hit/near miss) → Feedback (damage/Invincibility frames)

Lab Guide: treat the demo as an experiment

Hit Tolerance Experiment

Do: Drag "Forgiveness Window (hitbox shrink, px)" from 0 up to 24, then deliberately let bullets graze past your ship

Observe: Tolerance = the hitbox is one ring smaller than the visuals: at 0px a graze kills, at 24px players dare to thread between bullets. The gap between the two circles is your near-miss budget — too strict crushes showmanship, too loose kills the tension

Near-Miss Reward Experiment

Do: Pull "Graze Bonus" from 0 to 50, then set "Bullet Density" to 3+ and actively fly close to bullets

Observe: A graze bonus turns dodging from survival into a chased thrill: hazards become score resources. The higher the reward, the closer players hug danger — one parameter rewrites the whole risk-reward curve

Density Pressure Curve

Do: Step "Bullet Density" from 1 up to 5, surviving 20 seconds at each level

Observe: Density is the pressure-curve knob: each +1 visibly shrinks the safe space ratio. Density alone is not difficulty — real difficulty is density × tolerance: dense + forgiving stays casual, sparse + strict still kills

③ Behavior System Breakdown

3.1 Problems Solved

Make failure reasons attributable (why you were hit, where safety lies)
Turn near misses into satisfying moments rather than just staying alive
Control intensity with a pressure curve (density/velocity/rhythm) to avoid pure numeric stacking

3.2 Minimal Ruleset

Hazard: Generation rules (frequency/direction/speed/quantity)
Movement: Player movement and constraints (speed, turning, boundaries)
Hit detection: Hit radius and resolution (damage/failure/Invincibility frames)

3.3 System Loop (optional)

Input (movement/dodging) → Prediction (read warning) → Hit detection (hit/near miss) → Feedback (damage/survival) → Pressure change → New input

Design Notes

Thrill is a designed resource: how many pixels the hitbox sits inside the visual circle is exactly how brave players dare to be — too strict and they turtle up, too loose and the tension is gone. That gap is worth tuning more than bullet speed.

"Nearly died" beats "perfectly dodged": graze bonuses turn threats into resources, luring players toward danger — counterintuitively, rewarding grazes makes players safer, because they start studying trajectories on purpose.

Only attributable failure earns a retry: with unclear telegraphs, players feel "wronged" instead of "I messed up" — telegraph lead time is not an accessibility feature; it is the fairness foundation of dodge play.

④ Common Combos & Variants

Dodge / Avoid + Shoot / Aim

Output while evading, creating a 'positioning and shooting' loop

Dodge / Avoid + Progression

Convert survival time/perfect dodges into progression resources

Dodge / Avoid + Random

Randomize hazard patterns, emphasizing adaptation and reading the map

⑤ Advanced Design & Algorithms (collapsed)Click to expand

Design Warnings

Unclear warnings make failures unaccountable (players feel unjustified)
Too fast speed with weak feedback turns the experience into 'passively getting hit'
Overly strict hit detection compresses expressive space; overly lenient loses tension

Algorithm Examples

Generation: Bullet/obstacle generator and difficulty curve
Hit detection: Circle/capsule collision, near-miss detection, invincibility frame window

⑥ Related Case Articles

Pacman City: Turning "Dodge the Ghosts" into Timed Route Planning

120 seconds, 3 lives, 323 dots: eat and dodge through a block-city maze, where the 8-second power-pellet reversal is the only rhythm switch that matters.

Roguelike Slaying: Enemy Density Formulas and Screen Readability

This article dissects the core mechanics of roguelike slaying games, breaking down the construction of enemy density curves to create dynamic combat pacing. It explains how director systems use calculation to control enemy distribution for screen readability, analyzes hard rules limiting special effects to ensure visual clarity, and reveals the satisfaction derived from linear enemy growth paired with exponential player damage. The guide provides actionable advice for developers to balance numerical values with player experience.

Survival Countdown: Designing Time Pressure and the 'Final 10 Seconds' Effect

Analyze time pressure mechanics focusing on non-malicious dynamic curves and forgiveness windows. Deep dive into the 'Final 10 Seconds' effect to reveal how countdowns alter risk-reward ratios, driving players toward aggressive decisions in high-stakes endings, providing empirical strategies for building urgency in action-dodging levels.

Tap Dodge: Balancing Failure Tolerance and Bullet Speed Curves

A deep dive into the tap dodge mechanic, analyzing hitbox tolerance settings and near-miss feedback to balance failure risk. We also explore constructing bullet speed curves to achieve smooth difficulty progression, providing core design strategies for developers to ensure both responsive controls and long-term player retention.