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 removes that limitation. 3 billion entities with full physics at 60 FPS. 30,000x scalar throughput. Auto-SIMD IL weaving. Linear scaling to 96 cores. 95%+ memory bandwidth utilization. The abstraction was a concession to hardware limitations that every engine accepted as permanent. This engine doesn't accept it.
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¶
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.
Movement¶
Footwork — The feet lead. The sword follows. Movement-relative combat where the player's footwork generates the attacks. Evasion through real body displacement — sidestep, backstep, slip, duck. No dodge rolls. No i-frames. The skill is spatial intelligence.
Melee¶
Melee Combat — Directional attacks emergent from footwork. Parrying as real weapon collision at real angles. The bind — sustained weapon contact with physics-driven resolution. Guard positions, deflection angles, force transfer.
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.
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 | Sidestep, slip, duck, backstep |
| Grapple | Dagger / fists / absorption | Nothing else works here | You don't evade at this range. You commit. |
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.