Skip to content

Combat

The combat system is built on one principle: the physics is real. No i-frames. No hitboxes approximating bodies. No timing windows pretending to be parries. No stat tables pretending to be weapons. The sword either hit the body or it passed through the space the body left. No abstraction between the player's intention and the physical result.

Every action game in history has been a painting of combat: hitbox approximations, invincibility frames, canned animations triggered by button presses inside frame windows. Three layers of abstraction between the player and the fight. The industry standardized on this not because it's good design but because real physics for fast-moving humanoid combat at 60 FPS was never viable. The engine couldn't afford it.

HellspawnEngine is being developed to make this design testable. Its ECS, numerical, parallel, Weaver, and Physics work provide the technical foundation, but the full Darkfire combat stack remains a target to prove in a bind rig and later vertical slice. Scale and performance claims belong to reproducible engine benchmarks, not this game-design document.

The combat is not a system bolted onto the story. Combat is the moment where every verb converges under pressure. The player fights, and mid-fight they choose: absorb or restrain? Talk first or strike? Research the enemy's nature or overpower them? Every combat encounter is the courtroom. Testimony delivered through violence, the player judging in real time. The combat passes the fusion test because the physics is the mechanic, the mechanic produces the narrative data, and the narrative data determines the endings.


The Foundation

Player Interface and Input owns action lifecycle, context mapping, accessibility, and feedback for every combat mode. Combat remains intent-driven: the player chooses the judgment; body and physics perform the reachable attempt.

Physics Foundation: The paradigm break. Why every existing combat system is a rhythm game wearing a costume. What real physics combat means. Why the engine makes it possible. The window, not the painting.

Body Physics. The body is physics. 20 rigid segments, constrained joints, muscle forces. No animation. The body obeys physics the same way the sword does. Balance, stability, fatigue as muscle properties. Racial differences through mass distribution. If it looks wrong, the physics is wrong.

Articulated Armour. Rigid plates move through joints, overlaps, and straps. Mail, leather, cloth, and padding follow their own material behaviour. Procedural fitting, physical coverage, equipment loads, and the controller share one assembly. The first proof is an elbow, followed by a shoulder and a full suit; metal deformation and crowd performance require separate evidence.

Usability and Mastery Contract

Combat must be natural to command without becoming shallow. The player chooses intent, timing, direction, range, target relationship, and commitment. Competent motor control performs routine whole-body coordination. Mastery comes from reading and combining real systems: distance, posture, momentum, contact, terrain, fatigue, wounds, magic, opponents, and consequences.

The same verbs and physical rules serve the first fight and the hundredth hour. Assistance may make an intention easier to express or delegate more low-level coordination, but it never grants a different contact rule, hidden knowledge, invulnerability, damage, or enemy behaviour. Failure must be attributable: the player should be able to see what hit, what missed, what was blocked, and which physical condition changed the result.

These are acceptance targets, not claims that the current combat stack has already proved them:

Proof Target
First 30 seconds A new player can move, turn, stop, and face deliberately without fighting the controller.
First 5 minutes A new player can attack, guard, and evade intentionally, even before understanding advanced technique.
First 30 minutes A player can discover one useful interaction or composition without following an exact prescribed sequence.
Attribution After a hit, miss, fall, interruption, or failed cast, the player can identify the physical cause from available evidence.
Control parity Replaying the same realized trajectories produces the same contact and consequence under every assistance setting.
State consistency Materially equivalent intent from a materially equivalent state produces a materially equivalent attempt; differences have inspectable causes.
Long mastery Expert play continues to reveal new timing, geometry, compositions, counters, and cross-system uses without replacing the original grammar.

Movement

Footwork. The feet lead. The sword follows. Footwork constrains, powers, biases, and transforms the reachable attack set without uniquely selecting the weapon line. Evasion is any physically achievable body movement. Steps, pivots, slips, ducks, limb withdrawals, jumps, rolls, environmental routes, and powered corrections are descriptive possibilities rather than invulnerability-bearing actions. No dodge state. No i-frames. The skill is spatial intelligence.

Melee

Melee Combat. Directional attacks coupled to footwork and constrained by the body's reachable motion. Parrying as real weapon collision at real angles. The bind. Sustained weapon contact with physics-driven resolution. Guard positions, deflection angles, force transfer.

Momentum. The commitment curve. Feints as momentum redirects, not animation cancels. Cancels as deceleration physics (pull-back, redirect-to-guard, release into evasive movement). The read. Feet, acceleration, rotation, redirect. AI reading scales from weapon position (fodder) to foot pressure and support changes (bosses). Weapon-specific momentum feel. The bind as the deepest cancel state. Momentum as the grammar of combat.

Weapons: Every weapon is a rigid body with mass, length, balance point, edge geometry, and material hardness. Behavior emerges from physics, not stat tables. Sword, greatsword, dagger, spear, shield, fists. The weapon choice reflects the pilgrimage.

Ranged

Ranged Combat: Bows and crossbows with real ballistics. Trajectory, draw weight, arrow persistence, wind deflection. Blocking, deflecting, and catching arrows. The bow is the UI.

Magic

Magic. The unified system expressed as combat. Three natures, three magic styles. Angel structured, demon analytical, human faith. Slide casting, delay casting, bolt physics, deflection, reflection. Asheron's Call-inspired casting mechanics rebuilt on real physics.

Area Effects: AoE as physics propagation, not circle checks. Shockwaves with inverse square falloff. Fire that spreads based on material. Lightning that chains through conductors. Geometry blocks propagation. Elevation matters. Area denial as environmental creation under combat pressure.

Integration

Absorption in Combat: Absorption lives at grapple range. The most dangerous bracket. The footwork to close that gap is the skill test. The consent tracker records the spatial story of what happened. The physics produces the narrative context.

Wounds and Mortality: Wound type computed from contact geometry (edge/flat/point × velocity). Local muscle impairment, blood loss as systemic fatigue, pain as motor disruption. The mortality split: Real God can die (finite regeneration ceiling), True God cannot (The River removes the ceiling). One physics parameter changes at the water. The entire combat experience pivots on it.

Magic as Physics. Every buff, debuff, enchantment, and spell is a physics parameter modification. Strength is muscle MaxForce. Speed is ActivationSpeed. Fire is heat transfer. Ice is localized cooling. Lightning is involuntary muscle contraction. Character attributes are body properties. No stats screen. The body shows what it is through how it moves.

Enemy Design. Angels, demons, humans, and hybrids as physically different combatants. Racial differences through body properties, not animation sets. The tribrid player adapts. Angel speed, demon force, human adaptability. Every faction fights the way it lives.


Range Brackets

Combat operates across four range brackets. The player transitions between them through footwork:

Range Primary Secondary Evasion
Long Bow / crossbow / bolt magic AoE area denial Sidestep, use cover, read the archer
Medium Spear / thrown weapons / bolt magic Closing or retreating footwork Movement prediction, cover
Close Sword / axe / mace / melee magic Parry, shield, bind Physical translation, rotation, posture, limb clearance, cover, entry or retreat
Grapple Dagger / fists / absorption Framing, leverage, posture, disengagement No free escape: change the actual contact or remain held

Core Axioms

The design philosophy governs combat. Every axiom applies:

  • The Mirror. No morality system in combat. The consent tracker records what happened, not whether it was right.
  • The Grey. A being absorbed after a fight they started reads differently from one absorbed after the player struck first. Both are grey.
  • The Fusion Test. Every combat moment simultaneously reveals character (how the player fights), embodies theme (the cost of power, the intimacy of absorption), and operates as gameplay (real physics, real spatial decisions).
  • Show, Don't Tell. The combat teaches through physics, not tutorials. Near-misses are visible because they're real. Weight is felt because it's mass. The player learns by doing.
  • Mechanics Are the Story. The combat is the story. The way you fight is who you are. The footwork is the morality.
  • Complete Information Removes Ignorance, Not Difficulty. A player who has absorbed every enemy type and understands every weapon's physics still faces real spatial challenges. Knowledge of physics doesn't make physics easier.