The Order Of The Hollow Star
Combat Design — Full Breakdown

Description: 
A psychological combat system where player actions replace traditional inputs, and emotional states act as both pressure and consequence
Discipline: 
Combat Design, Behavioral Systems, Encounter Design
Engine: Unreal Engine 5 (Blueprints, C++)Combat Type: 
Behavioural Combat: tension-driven encounters where success depends on attention, presence, and composure rather than mechanical execution
Jump to: Premise • Combat Loop • Combat Pillars • Trial Structure • Skill Expression • Failure Case • What I Built • Full Project Page

Combat Premise
Combat in Hollow Star is behavioral, not mechanical. Players engage in high-stakes Trials where NPCs continuously evaluate their actions, and outcomes emerge from accumulated behavior over time. The pressure is real. The stakes are permanent. The inputs are not buttons.
Combat type:  Behavioral combat, where player behavior replaces traditional inputs and emotional states function as both the damage system and the health system simultaneously.
HOW THIS MAPS TO TRADITIONAL COMBAT
Traditional Combat Hollow Star Equivalent
Health pool Trust and Loyalty levels
Incoming damage Suspicion and Fear accumulation
Status effects Respect and Affection shifts
Enemy aggression level NPC evaluation intensity
Attack inputs Gaze, proximity, timing, dialogue tone
Lethal hit Breaking eye contact at a critical moment
Core Combat Loop
Every Trial runs through a continuous evaluation pipeline. Player behavior feeds into the emotional state system, which shifts pressure, which determines outcome:
PLAYER INPUT
Eye contact / gaze Proximity Attention duration Dialogue tone Hesitation Movement patterns
↓
EMOTIONAL EVALUATION
Continuous weighted evaluation across 30-40+ behavioral signals, aggregated into 6 emotional variables with delayed state resolution
↓
COMBAT STATE SHIFT
Suspicion up: higher failure risk Trust drops: locked options Fear elevated: destabilized encounter Balanced states: progression
↓
OUTCOME
Trial success Partial success (altered path) Soft failure Permanent failure
The player is not reacting to attacks, they are managing how they are being read in real time.
Combat Pillars
Pillar 1: Pressure Through Observation
The primary source of tension in Hollow Star is not incoming damage. It is being watched. NPCs continuously evaluate where the player looks, how long they stay, and how they move. This sustained evaluation replaces the threat of enemy attacks with something more psychologically demanding: the awareness of being read.
Combat intent: replace incoming damage with sustained evaluation pressure.
Pillar 2: Accumulated Damage — Delayed Consequence System
Unlike traditional combat, there is no immediate damage feedback. Mistakes accumulate invisibly and thresholds are crossed over time. A brief hesitation carries no immediate consequence. Repeated hesitation spikes suspicion. Sustained inconsistency triggers failure.
HOW DAMAGE ACCUMULATES
Single hesitation before response no consequence
Repeated hesitation across session suspicion spike
Sustained inconsistency over time failure threshold crossed
Combat intent: create uncertainty, sustained tension, and delayed punishment rather than immediate and legible damage feedback.
Pillar 3: Emotional States as Combat Variables
The 6 emotional variables function as the complete combat state. There is no health bar. There are no damage numbers. The player's combat viability is the stability of their emotional state profile across all six variables simultaneously.
Combat is not about reducing health. It is about maintaining a stable emotional state profile under escalating pressure.
Pillar 4: Legibility vs Ambiguity
Players must feel the system without fully decoding it. Too much clarity makes combat solvable. Too little makes it feel arbitrary. The system is tuned to stay interpretable but never fully predictable which is also the most fragile balance to maintain in playtesting.
Combat intent: keep the system felt, not solved. The moment players fully decode the evaluation logic, the encounter stops being combat.
Trial Structure — Designed Encounters
Each Trial functions as a multi-phase combat encounter with escalating pressure, behavioral checkpoints, and a final threshold resolution. Here is the structure of "The Witness", a representative Trial. Each Trial runs approximately 2 to 4 minutes and escalates continuously, with no hard breaks between phases:
1
Presence Check
Player must maintain proximity and attention. NPC establishes a baseline trust reading. Failure here raises thresholds for every subsequent phase.
↓
2
Stability Under Pressure
NPC introduces subtle behavioral tests: deliberate pauses, gaze shifts, ambiguous dialogue. Player must maintain eye contact, avoid erratic movement, and respond with consistent timing. Mistakes begin accumulating as suspicion.
↓
3
Disruption Event
NPC breaks expected pattern abruptly through sudden movement, unexpected silence, or direct confrontation. Player must adapt without overcorrecting. Overreaction spikes Fear. Underreaction spikes Suspicion. Both are wrong.
↓
4
Threshold Resolution
System evaluates the accumulated emotional state profile. Stable profile: success. Imbalanced profile: altered outcome. Critical threshold breach: instant failure with permanent narrative consequence.
HARD FAILURE CONDITION
Breaking eye contact during Phase 3 at a critical moment triggers immediate trial termination. No recovery. The encounter ends and the narrative consequence is permanent. This is the equivalent of a lethal hit in a traditional combat system.
Player Skill Expression
Skill in Hollow Star's combat is not expressed through reaction speed or mechanical precision. It is expressed through behavioral fluency under sustained psychological pressure.
SKILL DIMENSIONS
Consistency → Maintaining stable behavioral patterns across the full duration of a trial, not just at checkpoints
Attention → Recognizing subtle shifts in NPC behavior before they become threshold-crossing events
Interpretation → Understanding what the evaluation system is currently weighing without explicit feedback
Composure → Avoiding overcorrection under sudden pressure events, where both overreaction and underreaction are punished
Recovery → Recognizing when suspicion is accumulating and adjusting behavior before a threshold is crossed
Higher-skill players anticipate evaluation patterns, maintain stable emotional states under disruption, and recover from early mistakes before thresholds trigger. The ceiling is behavioral fluency, not mechanical speed. The player is not executing actions, they are maintaining a readable, stable presence under scrutiny.
Failure Case: When Combat Became Solvable
The system failed when players stopped experiencing the Trials as encounters and started treating them as puzzles with known solutions. The tension collapsed entirely.
What Players Did
Identified safe behavioral patterns and repeated them
Treated "look for X seconds, stand at Y distance" as a formula
Optimized emotional states like resources rather than inhabiting them
Lost the feeling of being evaluated entirely
Why It Happened
Feedback was too predictable and immediate
Evaluation patterns became learnable and repeatable
Safe strategies dominated once discovered
The system lost the ambiguity that made it threatening
ROOT CAUSE → FIX → RESULT
Predictable evaluation → Introduced variability in evaluation weights across sessions, preventing any single behavioral strategy from being reliably safe
Immediate feedback → Added delayed state resolution so consequences accumulate before surfacing, breaking the direct optimization loop
Visible safe strategies → Increased ambiguity in NPC behavior during disruption events so players could no longer predict the correct response
After the fix: players stopped optimizing and started reacting intuitively. The tension came back when the system became uncertain again. Combat only works when the player cannot fully solve it.
What I Built
COMBAT SYSTEM CONTRIBUTIONS
Psychological Combat 
System → Designed a non-traditional combat framework using behavioral input and emotional evaluation as the complete combat state, replacing health, damage, and cooldown systems
Trial Encounter Design → Structured multi-phase Trial encounters with escalating pressure, behavioral checkpoints, disruption events, and threshold resolution across soft and hard failure conditions
Emotional State Engine → Built a 6-variable emotional state system functioning as the complete combat state with delayed evaluation and weighted aggregation across 30-40+ behavioral inputs
Behavioral Input System → Integrated gaze direction, proximity, timing, movement patterns, and dialogue tone as the primary combat inputs replacing button inputs and mechanical execution
Failure Condition Design → Designed a spectrum of failure conditions from soft failures that alter narrative path to hard failures with permanent consequence, including instant termination on critical behavioral breaks
Playtesting and Iteration → Led 8+ structured playtests specifically targeting the tension between system legibility and combat ambiguity, iterating on evaluation variability until safe strategies were eliminated
Design Philosophy
Combat is not limited to mechanics
Conflict can exist through perception, pressure, and interpretation. The body is not the only thing that can be threatened.
Tension comes from uncertainty
Players are most engaged when they feel the system but cannot fully see it. The moment combat becomes solvable, it stops being combat.
The player is both actor and signal
What the player does is not just input. It is the data the system reads, evaluates, and resolves into consequence. The player is the weapon and the target simultaneously.
In a Commercial Context
Psychological and behavioral combat systems are directly applicable to narrative-driven titles where player presence and attentiveness should carry mechanical weight. This system maps to companion AI, stealth, social encounters, and psychological horror, any context where tension comes from uncertainty and being evaluated rather than reaction speed. The delayed consequence architecture applies directly to any title where dread needs to accumulate rather than spike.

← Back to Full Project Page