Backrooms:
Betrayal

Order Against Entropy  ·  Cooperation Under Suspicion

A cooperative multiplayer liminal horror experience centred on maintaining reality within unstable Backrooms sectors. Players explore, stabilize, and survive — all while questioning whether the collapse surrounding them is environmental, accidental, or deliberate.

The environment is not backdrop. The environment is the antagonist. Instability spreads, geometry shifts, entities manifest from entropy itself. The only defence is coordination — and the only threat may be each other.

6 Core Pillars
7 Loop Stages
6 Dev Phases
Coop Game Mode
Liminal Horror Genre
Scroll

The Cycle of Collapse

Backrooms: Betrayal is not a game about surviving a monster. It is a game about surviving a deteriorating reality. The loop below is not a sequence of discrete mechanics — it is a continuous, overlapping pressure system. Players do not complete the loop once. They repeat it, under increasing entropy, with dwindling certainty about who they can trust.

01

Explore

Players move through large, procedurally-flavoured liminal spaces searching for stabilization objectives, generators, reality anchors, resources, and extraction routes. The environment is already shifting. Nothing is entirely where it should be.

02

Detect Instability

Players learn to read environmental signals: flickering fluorescent lights, spreading grime, objects out of place, asymmetric room arrangements, abnormal audio. Every environmental cue is a data point. Instability has causes — and causes have authors.

03

Stabilize

Players perform tactile maintenance tasks — calibrating generators, restoring room symmetry, carrying reality anchors, reconnecting severed cables, resealing spreading anomalies. Tasks are short, physical, and deliberate. Stabilization is gameplay, not busywork. Every corrected sector buys time.

04

Temporary Safety

Stabilized sectors become briefly navigable: lighting restores, geometry corrects, entity pressure decreases. Objectives become accessible. Players feel, momentarily, that the environment is cooperating. This feeling does not last. But its memory makes the next collapse more dreadful.

05

Escalation

Entropy is relentless. Sectors begin degrading again. The rate of collapse accelerates as the session progresses. New failures appear faster than players can address them. Resources thin. Tasks become more complex. The environment stops feeling like a place and starts feeling like an organism fighting back.

06

Distrust

When failures accumulate faster than the environment alone can explain, players begin watching each other. Did the generator go offline on its own? Did someone disconnect it? Was that object moved by instability, or by a teammate? Plausible deniability is the core social mechanic. There are no accusation prompts. Suspicion is emergent.

07

Escape or Descend Deeper

Players face a binary: extract through a stabilized exit corridor, or descend further into a more unstable sector for higher rewards and escalating danger. Both paths carry risk. Extraction requires completing specific prerequisites under environmental pressure. Descent means leaving stability behind entirely.

Loop repeats — entropy never resets fully
Diagram B — Entropy Pressure Model (Mid-Session State)
Sector Instability
72%
Entity Aggression
60%
Player Sanity
44%
Team Trust
38%
Navigation Reliability
30%
Environmental Clarity
25%
Diagram D — Sector Gameplay Topology

Simplified overhead schematic: players converge on one stabilization objective, contain instability spread, move through the stabilized zone, then commit to an exit/deeper route while a subtle sabotage vector threatens the run.

Player Player Objective Instability Stabilized Zone Exit / Deeper Sabotage
Player Objective Instability Stabilized Zone Exit / Deeper Route Sabotage

Five Forces in Tension

Each pillar is a pressure system that operates simultaneously. No single pillar dominates. The game is defined by the friction between them.

🧭

Exploration

Players navigate large liminal environments searching for objectives, exits, and resources. Exploration is never casual — the environment actively changes. Familiar hallways shift. Previously safe areas degrade. Every journey has a time cost measured in entropy.

isolating atmospheric unpredictable
⚙️

Environmental Stabilization

Maintenance tasks are the primary form of player agency. They are short, tactile, and visually satisfying. The goal is not cleanliness — the goal is reality integrity. Players who understand this distinction will survive longer. Players who treat it as busywork will collapse the sector.

tactile purposeful collaborative
🌀

Escalating Instability

The environment degrades continuously. Flickering lights, spreading stains, geometry distortion, missing objects — these are not set dressing. They are mechanical consequences of entropy values exceeding thresholds. The game world communicates its own health state in readable, atmospheric ways.

relentless readable atmospheric
👁️

Social Paranoia & Betrayal

Players may intentionally or accidentally destabilize sectors. The design goal is plausible deniability: every failure could have an innocent explanation. Players should question each other without being prompted to. Suspicion is emergent, not systemic. There is no accusation UI. The environment is the alibi.

emergent deniable psychological
⚡

Entity Pressure

Entities are not independent threat actors — they are symptoms of instability. The more a sector degrades, the more frequently and aggressively entities manifest. They do not patrol or hunt traditionally. They emerge from environmental breakdown. Stabilizing the environment is the only way to suppress entity activity.

environmental reactive systemic
🔮

The Tertium Quid

Not simply another entity. The Tertium Quid is a possible reality immune system — a manifestation of structural imbalance, or a maintenance intelligence correcting excessive entropy. It becomes more active as instability increases. Its agenda may not be hostile. Or it may be precisely hostile enough to make the distinction meaningless.

enigmatic reactive escalating

Four Systems, One Pressure

The four foundation systems feed each other. Entropy affects sanity. Sanity affects task performance. Task failure affects entropy. Replication ensures every system state is shared across all players in real time. No system operates in isolation.

Sanity Mechanics

Player sanity degrades in high-entropy environments and recovers in stabilized sectors. Low sanity introduces unreliable perceptions — false entity sounds, hallucinated objects, distorted spatial information. Players must weigh task efficiency against their own psychological stability.

Done Needs balancing pass in Phase 6

Entropy / Instability Engine

A sector-level value that tracks environmental health. It rises continuously, faster in the presence of uncorrected anomalies, and drops when stabilization tasks complete successfully. Entropy crossing defined thresholds triggers environmental state transitions: lighting changes, geometry corruption, entity spawning rules, and audio degradation.

Next Up Phase 2 — core development target

Task System

A simple, framework-based objective system driving player interaction with the environment. Tasks are currently functional and support the stabilization loop. Future iterations will expand task variety, add multi-stage sequences, and introduce sabotage-adjacent interactions within the existing framework.

Done Framework complete — expansion planned

Replication & Multiplayer Sync

Core multiplayer state replication is operational. Environmental state, task progress, player positions, and sanity values are synchronised in real time. The replication foundation is sufficient to support all planned Phase 2–4 systems. Entity replication and betrayal-action sync will extend the existing foundation.

Done Core sync functional — entity sync pending

Design note:  This game deliberately avoids requiring complex combat systems, expensive cinematic assets, or high-variety AI. The atmosphere is generated through interaction traces, decal systems, state-driven lighting, environmental audio scripting, and object placement. Strong atmosphere at manageable scope.

Path Through the Backrooms

Six phases, ordered by dependency. Each phase has exit criteria that must be satisfied before the next begins. Current status is shown below. The project is mid-Phase 1 — the vertical slice is the immediate target.

System Status Notes
Task System Done Simple framework in place
Sanity Mechanics Done Needs balancing pass later
Basic Replication Done Core multiplayer sync working
Level Design Done Near-complete — excluded from active scope
Core Loop Flow
In Progress
Connecting all systems into one session loop
Environmental Instability Not Started Major next gameplay pillar — Phase 2
Entity Pressure Scaling Not Started Must react to entropy — Phase 4
Betrayal Mechanics Not Started Plausible-deniability design — Phase 3
Session Progression Not Started Run structure & extraction — Phase 5
Polish & Readability Not Started Final tuning pass — Phase 6
Phase 1
Core Loop Lock-In
In Progress
  • Task system baseline
  • Sanity mechanics
  • Basic replication
  • Complete session arc
  • Failure states clear
Phase 2
Environmental Instability
Not Started
  • Entropy model
  • Visual degradation
  • Audio degradation
  • Object displacement
  • Stabilization rewards
Phase 3
Betrayal & Paranoia
Not Started
  • Sabotage interactions
  • Deniability design
  • Emergent suspicion
  • Ambiguous failure overlap
Phase 4
Entity Pressure
Not Started
  • Entropy-tied spawning
  • Escalation thresholds
  • Aggression scaling
  • Environmental manifestations
Phase 5–6
Progression & Polish
Not Started
  • Session run structure
  • Objective rotation
  • UI readability
  • Sound & lighting polish
1

Core Loop Lock-In

Goal: One complete, playable session arc

The current development priority. All existing systems — task framework, sanity, replication — must be connected into a single coherent session flow with clear start, escalation, and end conditions.

  • Task system framework
  • Sanity mechanics
  • Basic multiplayer replication
  • Complete session flow (explore → stabilize → escalate → exit)
  • Failure states defined and readable
  • Instability meaningfully affects gameplay, not just visuals
  • Multiplayer test: all systems run in sync
Exit Criteria

A session can begin, progress, escalate, and end cleanly. Players understand what to do without heavy UI guidance. Instability changes gameplay, not just aesthetics.

2

Environmental Instability System

Goal: The Backrooms itself becomes the antagonist

Build the sector entropy model and its environmental consequences. Instability must be readable, escalating, and mechanically consequential — not merely decorative.

  • Sector stability/entropy model
  • Visual degradation states (lighting, geometry, decals)
  • Audio degradation states (buzzing, distortion, silence)
  • Geometry/layout corruption triggers
  • Object displacement and missing-object events
  • Symmetry/order detection and correction tasks
  • Stabilization rewards and temporary safety windows
Exit Criteria

Players can detect unstable sectors. Stabilization visibly improves the environment. Instability escalates over time in a readable, atmospheric way.

3

Betrayal & Social Paranoia

Goal: Plausible-deniability sabotage as emergent gameplay

Introduce actions that can intentionally or accidentally destabilize sectors. The game must make sabotage feel believable inside the fiction — ambiguous enough that players can never be fully certain.

  • Intentional destabilization interactions
  • Hidden and ambiguous sabotage mechanics
  • Accidental vs. intentional failure overlap
  • Emergent suspicion without accusation UI
  • Social tension generated by system design alone
Exit Criteria

Players can meaningfully interfere. Sabotage feels plausible within the fiction. The game generates suspicion naturally without prompting.

4

Entity Pressure & Threat Scaling

Goal: Entities as consequences of instability

Entities must feel like manifestations of entropy — not independent monsters. Threat should escalate predictably based on sector state while remaining atmospherically unpredictable in moment-to-moment behavior.

  • Entity behavior driven by entropy values
  • Escalation thresholds and spawn frequency
  • Aggression scaling with corruption
  • Environmental manifestation precursors
  • Tertium Quid behavior design
Exit Criteria

Entities feel like consequences of instability. Threat ramps predictably but still feels unpredictable. Environment and entities reinforce each other atmospherically.

5

Progression, Objectives & Session Structure

Goal: Structured, replayable run architecture

Formalize the session arc with objective variety, sector-based progression, resource scarcity tuning, and clearly defined win/lose conditions that make each run feel distinct.

  • Objective rotation system
  • Sector-based progression
  • Resource scarcity tuning
  • Temporary safe-zone logic
  • Win/lose/end conditions
  • Difficulty curve across sessions
Exit Criteria

Runs have a clear arc. Players make strategic choices about what to stabilize. Replays feel different through objective and instability variation.

6

Polish, Feedback & Readability

Goal: Tense, satisfying, and understandable

Final tuning pass across all systems. The experience must be readable — players should always understand the state of the run — while remaining atmospheric and tense throughout.

  • Lighting feedback for stability changes
  • Sound cues for instability and sabotage
  • UI for tasks, sanity, and sector state
  • Player feedback for stabilization success/failure
  • Onboarding for core systems
  • Sanity balancing pass
Exit Criteria

Players always know the state of the run. The game feels tense without confusion. Stabilization is emotionally rewarding, not mechanically opaque.

The Aesthetics of Wrong

Visual design is not decoration in Backrooms: Betrayal. It is the primary communication channel between the game state and the player. Instability is visible before it is mechanically consequential. Stability is a reward the player can see and feel.

Instability Visual Language

Environmental degradation signals are layered: early instability introduces subtle wrongness (slightly misaligned objects, faint flicker), while advanced instability breaks visual coherence entirely.

  • → Spreading grime and staining
  • → Flickering and failing fluorescent lights
  • → Peeling wallpaper and exposed infrastructure
  • → Stretched and distorted geometry
  • → Clutter accumulation and object displacement
  • → Asymmetric room arrangements

Stabilization Visual Reward

Stabilization should feel visually and emotionally rewarding. Players need to see the environment respond to their work. The before/after contrast is the primary feedback loop.

  • → Lighting restores and stabilises
  • → Geometry corrects and symmetry returns
  • → Stains and grime recede
  • → Ambient noise reduces
  • → Environmental calm settles briefly
  • → Objects return to correct positions

Environmental State Contrast

Unstable
  • Flickering lights
  • Asymmetric layout
  • Missing objects
  • Spreading stains
  • Distorted audio
  • Geometry shifts
Stabilized
  • Steady lighting
  • Correct symmetry
  • Objects in place
  • Clean surfaces
  • Reduced noise
  • Consistent geometry

Colour Palette Direction

The visual palette should reinforce the liminal aesthetic: institutional yellows and greens, dead whites, deep shadow, and the amber warmth of failing fluorescent light.

Fluorescent White
Institutional Yellow
Faded Institutional Green
Deep Shadow Brown
Near-Black Void
Corruption Red

Barely Holding Reality Together

"We are barely holding reality together long enough to survive."

This is the exact emotional fantasy the game is designed to deliver. Not power. Not mastery. Desperate, collaborative competence against an entropy that cannot be stopped — only delayed, sector by sector, minute by minute.

The Backrooms should feel like a place that does not want to be stable. Players are the immune system. The environment is the infection. And somewhere in the team, there may be a carrier.

The ideal Backrooms: Betrayal session ends with players not entirely sure whether they lost to the environment, to each other, or to their own decisions under pressure. That ambiguity is the product.

  • 01
    The environment is the antagonist

    Entities, social tension, and mechanical pressure are all expressions of a single underlying system: entropy. There is no external villain. The Backrooms itself is the threat.

  • 02
    Atmosphere through systems, not assets

    The game's horror derives from interaction traces, state-driven lighting, environmental scripting, and sound design — not from expensive cinematic content or complex AI.

  • 03
    Plausible deniability is the social mechanic

    There is no accusation UI. There is no betrayal meter. Suspicion is emergent because the design ensures every failure has a plausible innocent explanation.

  • 04
    Stabilization is the reward, not the task

    Players should feel the environment respond to their work. The before/after contrast of a stabilized sector is the game's primary emotional payoff.

  • 05
    Entropy never fully resets

    Players buy time. They do not achieve permanent safety. This keeps tension constant and ensures every stabilization is meaningful precisely because it is temporary.

😰
Tension
Constant low-grade dread with periodic spikes
🫥
Vulnerability
The environment is bigger and smarter than the player
🔧
Responsibility
If you don't stabilize this, it collapses on everyone
👁️
Paranoia
Was that an accident? Or is someone working against us?
😮‍💨
Temporary Relief
Stabilization feels earned precisely because it doesn't last
🌑
Dread
The inevitable return of decay, now closer than before