How to Build a Hitbox and Hurtbox System

Hitboxes and hurtboxes—the regions that deal and receive damage—define how combat collision works, and their precise design and tuning shape how fair and satisfying combat feels. Building this system well, with careful tuning of the boxes, is what makes hits land fairly and combat feel right, because the boxes determine the moment-to-moment fairness of every hit.

Hitboxes and hurtboxes define combat collision precisely

In combat, you need precise definitions of what deals damage and what receives it, which is the role of hitboxes (the regions that deal damage, like a sword swing or a projectile) and hurtboxes (the regions that receive damage, like a character's vulnerable area). When a hitbox overlaps a hurtbox, a hit registers. Defining these precisely—separate from the visual representation, tuned for gameplay rather than just matching the art—is what makes combat collision work correctly and feel fair. Crucially, hitboxes and hurtboxes are usually not the same as the visual sprite or model: they're gameplay regions tuned for how combat should feel, which is why a character's hurtbox is often smaller than their sprite (so near-misses feel like misses) and an attack's hitbox is tuned for how the attack should connect. Defining hitboxes and hurtboxes precisely, as gameplay regions tuned for combat feel rather than just matching the visuals, is the foundation of a combat collision system that registers hits correctly and fairly.

Tuning the boxes is what shapes how fair and good combat feels. The precise tuning of hitboxes and hurtboxes profoundly shapes combat feel and fairness, which is why it's worth careful attention. A common and effective tuning is smaller hurtboxes and generous hitboxes: making a character's hurtbox somewhat smaller than their visual size means near-misses register as misses, which feels fair (the player wasn't really hit), while making attacks' hitboxes generous means attacks connect when they look like they should, which feels satisfying (the player's hits land). This asymmetry—forgiving hurtboxes, generous hitboxes—tends to make combat feel fair and satisfying, because the player's hits land reliably while near-misses against them don't register as hits. The exact tuning depends on the game and is found by feel, adjusting the boxes until combat feels fair and good—hits landing when they should, misses being misses, the collision matching the player's intuition about what should connect. This tuning is some of the most impactful combat feel work, because the boxes determine the moment-to-moment fairness of every hit, and getting them right makes combat feel fair and satisfying while getting them wrong (boxes that don't match intuition, hits that don't land or land unfairly) makes combat feel off and frustrating. Combining precise hitbox and hurtbox definition (as gameplay regions tuned for combat, separate from visuals) with careful tuning of the boxes (often forgiving hurtboxes and generous hitboxes, dialed in by feel) is what makes a hitbox and hurtbox system produce fair, satisfying combat collision—hits landing fairly, near-misses being misses, the collision matching the player's intuition. Because the boxes determine whether every hit lands fairly, building and tuning them carefully is essential to combat that feels right, which is why hitboxes and hurtboxes, precisely defined and carefully tuned, are at the heart of how fair and good a game's combat feels.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

The first impression is most of the battle

More players leave in the opening minutes than at any other point, which makes the first few minutes the highest-leverage stretch of the whole game — and also the part the developer can least see clearly, having played it a thousand times. What feels obvious to you is often confusing to someone seeing it fresh, and that gap quietly costs you players before they ever reach the good part.

Get the player into the interesting part fast, let them feel competent quickly, and watch first-time players go through the opening without helping them. Nobody quits a game they're enjoying, so making the early minutes land is most of the battle for retention.

Small and finished beats big and abandoned

A folder of impressive unfinished projects teaches far less than a single small finished one, because finishing is where the hardest and most valuable lessons live — the unglamorous final stretch of bug-fixing, polishing, and shipping that ambitious abandoned projects never reach. Each completed game, however modest, builds the finishing muscle and the confidence that make the next one achievable.

So resist the pull of the dream project until you've shipped a few small ones. Scope to what you can actually complete, finish it, and let the experience of shipping make your bigger ambitions realistic.

Trust behaviour over opinions

People are unreliable narrators of their own experience — they're polite, they rationalise, they suggest fixes that miss the real problem. What they do tells the truth that what they say obscures: where they hesitate, where they get stuck, what they ignore, where they quit. The most valuable feedback is usually the behaviour you observe, not the opinion you're offered.

This is why watching beats asking, and why real data about what players actually do beats any amount of speculation. When several people stumble at the same spot, that's a problem worth fixing, regardless of whether any of them mentioned it.

Ship it, then learn from it

No amount of internal deliberation substitutes for the information you get the moment real players touch your game. The assumptions that felt certain turn out wrong, the feature you doubted becomes the favourite, and the problem you never imagined is the one everyone hits. That feedback only exists on the other side of shipping.

So bias toward getting something real in front of real people sooner rather than later. A rough thing that's out in the world teaches you more in a week than another month of private refinement, and every release makes the next decision better informed.

Hitboxes deal damage and hurtboxes receive it, defined as gameplay regions separate from visuals. Tune them—often forgiving hurtboxes and generous hitboxes—by feel, because the boxes determine whether hits land fairly.