Melee and combat systems
Melee combat revolves around distance and the moment of commitment. Starting an action can temporarily remove the ability to defend, so opponents need readable preparation, reach and contact results. These overviews separate decisions about targets, continuing a sequence, choosing a defense and escaping a bad position. Start by testing one attack and one response without decorative effects. The dedicated boss reference remains available in the direction map; this catalog covers the other contact-combat topics. Sources illustrate state and animation-transition models rather than prescribing a universal combat formula.
No matches
Change your query or reset the filters.
Mechanics and variants
1Hand-to-hand combat and beat ’em upsOverview and example ↗The player chooses a target, distance and attack direction, connecting movement to safe contact timing and escape from surrounding enemies.4
Mechanic variants
- Distinct ranges: a short strike is quicker, while a long strike reaches retreating opponents.
- Directional contact: front, side or rear positioning changes the available response.
- Launch and knockdown: a hit temporarily puts the target in another movement state.
- Environmental weapons: picked-up objects change reach and are consumed through use.
Design example. In an alley, the player pushes the nearest enemy toward a wall and exits through the opened side before continuing the fight. Prototype check: Test one enemy and a crowd: repeated overlap checks should not grant unintended extra hits to the same target from one swing.
2Fighting games and duelsOverview and example ↗A duel turns range, startup and recovery into exchanges of advantage: the player provokes an action and selects a response.4
Mechanic variants
- Attack height: different target zones require different defenses or stance changes.
- Whiff punishment: leaving an attack's reach opens a response during recovery.
- Move canceling: a permitted transition reduces commitment at a resource or condition cost.
- Defense breaking: passive blocking loses to throws, accumulated pressure or a changed angle.
Design example. In a training duel, a long lunge catches retreating movement but lets the opponent approach and answer with a short sequence after a miss. Prototype check: Test a hit, a block and a miss for each move separately; resulting advantages should follow the permitted state transitions.
3Combos and character actionOverview and example ↗The player connects actions through permitted transitions, trading reliable finishers against continued pressure and preserved defensive options.4
Mechanic variants
- Branching sequences: the same opening leads to different finishers.
- Conditional follow-ups: the next strike is permitted only after confirmed contact.
- Cancel resources: transitioning into a dodge or another attack spends a limited reserve.
- Target switching: continuing a sequence redirects the next strike to another reachable opponent.
Design example. The player finishes a short sequence with a push or spends a cancel charge to escape another opponent's attack. Prototype check: Send the next input before, during and after the follow-up window; the buffer should not execute the action twice.
4Soulslikes and stamina managementOverview and example ↗The player preserves a response to the next threat by dividing a resource between attacking, dodging, blocking and repositioning.4
Mechanic variants
- Shared reserves: attacks and defenses compete for the same resource.
- Exposed recovery: a sequence requires a pause, distance or a safe position afterward.
- Heavy commitment: powerful actions are harder to interrupt and riskier to use blindly.
- Distinct defenses: spacing, blocking and dodging solve different threats.
Design example. At a heavy doorway, the player saves enough reserve to dodge after a second strike even though a third could finish the current target. Prototype check: Compare full and nearly depleted reserves: feedback should explain an unavailable action before the player makes a dangerous attempt.
5Hack and slashOverview and example ↗The player sustains attacks and chooses ability order to clear groups with different resistances and threats efficiently.4
Mechanic variants
- Area damage: choosing a center and radius matters more than precise targeting.
- Chain reactions: a destroyed or marked target passes effects to nearby enemies.
- Short cooldown cycles: alternating abilities maintains tempo instead of repeating one action.
- Priority targets: support units or dangerous shooters require a new route through the crowd.
Design example. Against a group with a healer, the player opens a path with a dash, marks the healer and uses its defeat to trigger a chain explosion. Prototype check: In a dense group, test chain limits, affected-target counts and whether the next threat stays readable beneath effects.
6Blocking, parrying and counterattacksOverview and example ↗The player matches a defense to threat direction and timing; success can change exchange tempo, position or the available response.4
Mechanic variants
- Held blocking: reduces contact consequences while direction and resources remain valid.
- Timed parrying: a short window turns an incoming hit into an opening.
- Directional defense: a chosen sector covers one threat while exposing others.
- Conditional counterattacks: a response opens only after a specified successful defense.
Design example. An opponent alternates a sweep and a lunge; blocking handles both, but precisely parrying the lunge allows a disarm. Prototype check: Test the start and end of the defensive window, simultaneous hits and the readability of blocking versus parrying.
7Grapples, throws and wrestlingOverview and example ↗The player establishes controlled contact with a target and selects a follow-up, restricting both participants' movement during the interaction.4
Mechanic variants
- Range-gated grabs: entry requires suitable proximity, facing and target state.
- Chosen throws: release direction changes collisions with walls or other enemies.
- Resistance: the grabbed target receives an explicit escape window or resource.
- Geometry compatibility: obstacles cause a clear adjustment or refusal of the interaction.
Design example. On a narrow bridge, the player can throw an enemy behind them to clear a path or pin it against a support for a short stun. Prototype check: Test grabs near walls, edges and a participant's defeat: both characters should return to valid independent states.
8Crowd combat and space controlOverview and example ↗The player manages position relative to several threats, dividing attention and creating temporary safe sectors instead of trading hits in place.4
Mechanic variants
- Attacker limits: some enemies wait for a free position or permission to engage.
- Sector suppression: a broad action temporarily clears an escape direction.
- Group separation: obstacles or lures stagger encounters with different enemies.
- Linked roles: defenders, shooters and support units force changing priorities.
Design example. In a columned hall, the player blocks a distant shooter's sightline and meets pursuers one at a time in a passage. Prototype check: Add enemies individually and inspect simultaneous threats: increasing difficulty should retain distinguishable decisions and escape routes.
9Breakable parts, injuries and conditionsOverview and example ↗The player selects a target part or effect type to change its capabilities rather than merely reduce shared health.4
Mechanic variants
- Local durability: a separate part has its own break condition.
- Functional loss: damaging a weapon, limb or sensor changes the target's behavior.
- State accumulation: repeated effects cross a stagger, injury or vulnerability threshold.
- Part recovery: the target repairs or reconfigures unless the player maintains pressure.
Design example. A mechanical guard can lose leg function and slow down, or lose its ranged weapon while retaining fast melee attacks. Prototype check: After each break, check available actions and visible changes; attacking an already broken part should follow an explicit rule.
Sources and examples
Sources support particular techniques or methodology, not every family variant. Design examples and mechanic combinations are illustrative.
- Robert Nystrom: State
The book author's original text on states, permitted actions and transitions; implementation context for combat states.
- Godot: AnimationTree
Godot documentation for animation blending and state transitions; visual blending alone does not define hit rules.
CC BY 4.0 · gamemechanics.pro contributors