BackroomsMMO is an online multiplayer game project based on the Backrooms setting. It combines a native game client, dedicated server runtime, account-backed online play, persistent characters, replay support, social systems, and server browsing into a single multiplayer platform.
The project is closely tied to BackroomsEngine, the native C++ runtime used for the game client, server, renderer, world generation, audio, networking, replay capture, and development tools. BackroomsMMO is the player-facing online game and service layer, while BackroomsEngine is the lower-level technology that runs the game.
BackroomsMMO is in active development. Its design is aimed at a survival and exploration experience where players move through procedural and authored Backrooms spaces, join online shards, maintain characters, interact with other players, record moments, and take part in a wider connected Backrooms ecosystem.
Concept
BackroomsMMO takes the Backrooms idea and treats it as a multiplayer world rather than a single static location. The project is built around exploration, unease, survival pressure, group play, and the feeling of moving through spaces that are familiar enough to recognise but unstable enough to be dangerous.
The MMO part of the name reflects the project's online direction. It is not only a standalone Backrooms level viewer or a small co-op test. It is being built as a wider online game with accounts, characters, public server discovery, persistent state, social features, replay tools, and server-side authority.
The project uses the Backrooms setting as a foundation for several kinds of play:
- exploration of large procedural spaces
- survival against environmental pressure and hostile encounters
- team-based support and recovery
- persistent characters and progression
- server-based online sessions
- social and group play
- recorded replays and shareable moments
- moderation and safety systems suitable for an online community
Relationship to BackroomsEngine
BackroomsMMO and BackroomsEngine are separate but closely connected parts of the same project. BackroomsEngine provides the native game technology. BackroomsMMO uses that technology to present the online game, account flow, website, server list, character flow, and player-facing services.
The engine builds the BackroomsMMO executable and the dedicated server runtime. It handles rendering, world streaming, input, audio, networking, replay capture, server authority, gameplay state, and tools. The web platform handles account-facing tasks such as login, character selection, server discovery, replay library pages, player settings, and online session support.
This split keeps the realtime game work in the native engine while keeping identity, account access, and player-facing online services in the web platform. The result is a project that behaves more like a live online game than a purely local executable.
Gameplay Direction
The gameplay direction is based on exploration, survival, and support-oriented multiplayer. Players are expected to move through Backrooms spaces, manage risk, recover from dangerous situations, and work with other players rather than simply run through a set of linear levels.
The source code and project structure show support for player vitals, progression, missions, safe rooms, stashes, challenges, reputation, clans, investigation traces, map discovery, waypoints, loot spots, and persistent world interactions. These systems suggest a game built around repeated play and long-term identity rather than one-off sessions.
Support play is a natural fit for the project. BackroomsMMO includes systems that can support revives, team recovery, healing, protection, party play, group challenges, and social coordination. The Backrooms setting also gives support mechanics a stronger role because isolation, injury, fear, and getting lost can become part of the actual game loop.
World and Exploration
BackroomsMMO's world is driven by BackroomsEngine's world generation and streaming systems. The engine supports deterministic chunk generation, world seeds, multiple floors, procedural corridors, doors, instance entrances, loot markers, props, biome-style variation, and streamed chunk loading around the player.
The world is not limited to one room type. The engine source contains support for themed generation, dungeon and instance spaces, poolrooms and other themed tests, safe rooms, door travel, and level-aware map discovery. This gives BackroomsMMO room to grow beyond a single Level 0 interpretation.
Exploration systems include discovered chunks, discovered doors, level-aware map data, room transitions, instance paths, safe-room waypoints, and persistent marks such as chalk or investigation evidence. These details help make exploration meaningful. A player is not only moving through scenery; they are building knowledge of the spaces they have survived.
Online Servers
BackroomsMMO uses dedicated servers for online play. Players discover servers through the game and connect through a session flow that verifies identity and character selection. The server runtime is designed to own important parts of online state instead of trusting the client with everything.
Server authority is important for an MMO because players share the same world state. Movement, vitals, chat, combat, loot, inventory, currency, party systems, and other gameplay features can be checked or corrected by server-side systems. This is meant to make online sessions more consistent and harder to abuse.
The server also reports live player and world information back to the web layer so that server status, player counts, and online session data can be shown outside the game client. This supports a server browser and gives operators a clearer view of what is happening in the online world.
Characters and Identity
BackroomsMMO includes character-based play. Players can use account-backed character slots, choose a character for a session, and carry character data through online play. Character identity is part of the game's longer-term structure because an MMO needs continuity between sessions.
Character systems are tied to progression and persistent state. The engine has structures for account progression, character progression, missions, stashes, reputation, alignment, safe rooms, respawn anchors, and world discovery. The online platform connects these ideas to account identity and server access.
The project also supports player-facing names, preferences, and social privacy. These are important for a multiplayer game because identity does not stop at a character model. It includes how players appear to others, how they join friends, and how much social access they want to allow.
Social Features
BackroomsMMO includes social features intended to support an online player community. These include friends, messages, parties, clans, privacy controls, challenge lobbies, and group play flows. The aim is to make the game feel connected even when players are not currently inside the same corridor.
Group systems are especially relevant to the Backrooms setting. The threat of separation, rescue, support roles, and team survival all become stronger when the game can track who is playing together and how they are connected. Parties and clans can give players a reason to return, organise sessions, and build identity around groups.
The project also includes challenge-oriented play. Challenge lobbies and challenge state make it possible to run structured sessions with objectives, difficulty, rewards, and completion tracking. This gives the game another layer beyond open exploration.
Replays and Media
BackroomsMMO includes replay support. BackroomsEngine can capture recent gameplay snapshots, camera state, player state, audio events, and voice frames. The online platform can then store and present replay files for the player.
Replay support fits the Backrooms theme well because unexpected events, near misses, strange encounters, and rescues are central to the appeal of the setting. A replay system lets players keep those moments rather than relying only on live memory or external recording software.
The project also has links to wider media tooling in the Backrooms ecosystem. The important public point is that BackroomsMMO is being built with sharing, recording, and replay review in mind, not just live play.
Voice and Communication
BackroomsMMO includes voice and chat systems. Chat can support different channels such as world, local, party, and clan communication. Voice systems are more sensitive because they involve player audio, so consent and player control are important parts of the design.
Voice is especially relevant to the Backrooms setting. Local communication, radio-style effects, distance, echo, panic, and misdirection can all become part of the atmosphere. The project also experiments with mimic-style voice features, which makes consent and careful handling even more important.
Moderation and Safety
BackroomsMMO is an online community project, so moderation and safety are part of the design rather than an afterthought. The platform includes account access, bans, permissions, warnings, game access checks, server-side verification, and operator tools.
For an online game, this matters as much as graphics or world generation. A shared multiplayer space needs a way to handle abusive behaviour, compromised accounts, cheating, spam, harassment, and bad-faith use of social systems. BackroomsMMO's account-backed design gives the project a foundation for those controls.
Expanded Gameplay Systems
BackroomsMMO is the player-facing game built on BackroomsEngine. Its central loop is an expedition into a persistent, streamed Backrooms world: move through unfamiliar spaces, read the environment, manage scarce resources, work with or avoid other people, complete objectives, recover what was lost, and leave traces that affect the next decisions.
Exploration, Levels, and Travel
The world is generated from deterministic seeds and streamed in chunks instead of being a small fixed map. Current world modules include Level 0, the Mall, Factory, Hotel, Poolrooms, Island, and Dungeon themes, with rooms, doors, props, vertical transitions, nested instances, and authored special spaces. The same seed and persistent state let the world remain recognisable across visits while streamed chunks are loaded and evicted around the player.
Ropes, rappelling, ladders, depth transitions, falling, landing safety, and rope rescues make vertical movement part of navigation. Maps, waypoints, safe rooms, extraction points, and investigation traces provide navigational context without turning the world into a simple corridor.
The game supports cross-world portals, intersections, remote views, world-view slices, authority handoff, and rescue travel. A cross-server rescue can move a rescuer through a controlled transition, preserve authority and identity, and return the player to the appropriate world state. The portal and intersection presentation is part of the same system as travel and recovery.
Survival and the Environment
Characters manage health, armour, sanity, stamina, hunger, thirst, bleeding, fire, movement noise, and downed or revived states. Sprinting and fast crouching consume stamina; empty hunger or thirst pools can cause periodic harm; food, water, medical items, and other actions restore or modify the relevant pools. Air quality, water, temperature, darkness, weather, and environmental hazards add reasons to change route or equipment.
BackroomsMMO literally simulates air. The server maintains connected air zones and apertures with pressure, temperature, humidity, smoke, dust, gas composition, internal energy, emitters, surfaces, obstacles, and airflow. Pressure-driven openings use a bounded vertical counterflow model with hydrostatic effects, while fixed-step transport moves moles, energy, and environmental scalars between zones. Around the active focus, a quality-budgeted local 3-D field models velocity, pressure and divergence, gusts, body wakes, buoyancy, vorticity, turbulence, smoke advection, dust diffusion and settling, obstacles, and pressure projection. This is a hybrid simulation rather than a world-wide high-resolution CFD grid: zone state is authoritative across the connected world, and detailed local flow is concentrated where players are.
A door, leak, emitter, fire, wet surface, moving body, or gust can therefore change the air state around an expedition rather than merely swapping a post-processing colour. Smoke, dust, spores, mould, radon progeny, humidity, and heat have their own environmental reservoirs and transport paths. Fire consumes oxygen and produces heat, water vapour, carbon dioxide, carbon monoxide, and particulates. Mould responds to substrate, humidity, temperature, air speed, turbulence, disturbance, and light.
Respiratory physiology uses that composition. Oxygen and carbon-dioxide partial pressures, carbon monoxide, irritants, separate toxicant burdens, solvent exposure, and radon dose are tracked as distinct inputs. Players can encounter oxygen-poor, toxic, irritating, smoky, dusty, spore-laden, mould-affected, or radon-affected air. Masks, air-purifying cartridges, SCBA, and underwater rebreathers have leaks, finite capacity, breakthrough, breathing demand, and persistent item identity. Underwater breath-hold and rebreather rules are separate from ordinary breathing, and no protective item creates absolute immunity. Exposure is represented as typed respiratory burdens, protection-resource depletion, and air-quality cues; not every burden directly damages the life-state model.
Water and air are coupled. Shallow water, waves, porous substrates, droplets, splashes, evaporation, condensation, latent and sensible heat, and surface temperature can feed back into the environmental state. Swimming and submerged movement sample chemistry-derived density, drag, pressure, buoyancy, propulsion, and equal-and-opposite fluid reactions; environmental loads can also respond to pressure gradients and thermal exchange.
Items, Loot, Equipment, and Workbenches
Loot is deterministic and authoritative. Search spots and loot tables produce item instances with categories, stack limits, weights, levels, rarity, durability, and bonus affixes. Inventory and equipment persist, and the paper-doll and toolbelt systems make carried weight, equipped protection, utilities, and recovery choices visible to the player.
Consumables can restore vitals; tools support traversal, searches, protection, and rescue; and safe-room workbenches provide a place to craft or maintain useful equipment. Item identity is retained across reconnects and recovery, preventing a retry from duplicating an item or silently restoring a depleted protective cartridge.
Personal Hubs and Safe Rooms
Personal hubs and safe rooms are persistent places rather than menu screens. Players can claim or transfer ownership, name a room, set access modes, link friends, assign permission roles, fortify doors, place buildables, maintain storage, and install utilities such as beds, workbenches, lights, and respawn anchors. Stash and extraction systems connect a room to expedition planning and property recovery.
Sleeping bags and safe-room beds establish respawn anchors. Storage, ownership, access checks, and object upgrades are authoritative and survive reconnects. A hub can therefore be a social shelter, a crafting location, a planning base, and a remembered piece of the world.
Death Caches, Honour, and Recovery
Death does not reduce the character to an unexplained reset. Recoverable property can become a persistent Death Cache with an owner, a timed lifecycle, a protected recovery period, and a later public or return path. The server, account service, and inventory authority reconcile the cache so recovery, theft, return, and reconnect operations remain durable.
Honour is a private conduct and relationship signal connected to cooperative play. It is bounded separately from alignment and faction reputation, has authored aura ranges, and can snapshot into the presentation of a later Death Cache. Rescue work and returning sealed property can award Honour, while breaking a seal to steal property can penalise it. Death Cache actions include owner grace, public interaction, sealed returns, custody and reclaim states, anonymous remainder returns, and a Returned Property locker. Honour is not a public money balance or a leaderboard, and it should not be confused with Coins. Death Cache presentations can also use Honour, rainfall, autumn-leaf, or galactic effect styles and selectable colours as owned cosmetic state.
Characters, Progression, and Factions
Accounts can carry character identity, appearance, character slots, progression, perks, specialisations, item levels, rarity bonuses, statistics, alignment, and faction reputation. Alignment combines a dominant trait with ethical and moral axes and a recent-action record. Reputation tracks relationships with factions such as survivors and engineers, allowing missions, rescues, and other actions to have a longer-term social meaning.
Missions, Puzzles, and Challenges
Mission contracts can come from planning desks or held NPC mission objects. They can ask players to recover, deliver, investigate, rescue, stabilise, or return something, and they persist through the relevant acceptance and completion path. Survivor-focused objectives connect missions to safe rooms, supply chains, faction relationships, and rescue play.
The puzzle system uses validated templates, clues, dials, ordered sequences, item rotation and combination, sockets, circuit routes, submissions, hints, case items, permutations, action nodes, room, chain, world or daily lifecycles, tiers, snapshots, gate unlocks, and reward effects. A puzzle can record a mission objective and remain consistent after reconnecting. Challenge mode adds controlled operations, scoring, checkpoints, temporary session loot, revive choices, mission-item custody, coins, voice states, challenge residents, and private-server probes.
Survivor Contacts and NPC Missions
Survivor contacts can offer dialogue and generated fetch, area, search, recover, missing-survivor, proof-recovery, route-depth, keepsake, trade, and coin objectives. Mission acceptance, capacity, turn-in, completion, and reward state persist with the character. These chains connect survivor reputation, safe-room supply lines, rescue decisions, and the wider world rather than functioning as disconnected menu quests.
Coins and Clan Bases
Coins are a distinct wallet and progression resource used by authored missions, challenge operations, trade, and selected services. Clans can maintain a shared base with contribution, upgrades, permissions, and entry rules. Clan state is separate from private safe-room ownership but can support group planning, storage, and social identity.
Entities, Mimics, Traps, and Investigation
Mimics, hostile entities, bodyguards, and director systems make the world react to player presence. Voice mimicry can use consented recordings and audience controls, while authored character voice and semantic sound systems provide controlled reactions. Bodyguards and companions can participate in navigation, rescue, protection, and mission flows.
Players can leave or discover evidence through blood, chalk, investigation objects, traces, semantic sounds, and persistent world state. Bear traps can be authored or player-placed physical objects with placement clearance, instance and world-layer identity, swept foot-contact detection, immobilisation and damage, self-release, assisted release, reset, disarm, pickup, and authoritative state revisions. These systems make the world socially and physically readable: a route can contain evidence of previous activity, a trap can change the next encounter, and a voice can be a warning or a threat.
Close combat includes jabs, hooks, punch combinations, high kicks, roundhouse kicks, lunge spin kicks, counterstrikes, guarding, dodging, and rolling. Stamina costs, contact windows, collision sweeps, and server authority determine the outcome.
Parties, Clans, Trade, and Communication
The social layer includes parties, party rooms, clans, friend links, permissions, trade, chat, proximity voice, radios, emotes, and online presence. Privacy settings control friend and party joining, random intersections, and stranger-rescue volunteering. Social actions are tied to server authority and account identity rather than trusting a client-provided player name.
Shards, Persistence, and Online Operations
BackroomsMMO uses authenticated accounts, character authority, join tickets, shard selection, content synchronisation, authoritative movement and gameplay transactions, persistence journals, encrypted saves, recovery operations, and dedicated-server administration. The website services provide account, character, shard, social, moderation, replay, voice-consent, and related online functions around the game.
Private servers and challenge pools have their own admission, content, progression, and lifecycle controls. Official servers use the same authority model but are operated as a fixed fleet with controlled content and identity.
Cinematics, Replays, Video, and Mods
Cinematics offer tracks, keyframes, branching choices, cameras, authored scenes, online checkpoints, safe playback, accessibility controls, and an editor. Replays can capture sanitised world, player, audio, and voice state, and approved media can be moderated, exported, published, or streamed.
The mod system uses `.brmod` packages with manifests, supported content declarations, safety checks, private-server support, and official-server restrictions. Model, texture, animation, cinematic, asset-cache, load-test, and RealBot tools support production and validation around the game.
RealBot and Operational Testing
RealBot simulates external players with roles, personalities, movement and navigation, doors, instances, travel, loot and inventory, safe-room building, team flows, voice traffic, death and revival, lifesaver probes, challenge/private-server probes, coins, replay/media probes, dashboards, and distributed load runs. It is an operational validation system used to exercise player-facing contracts at scale, not a replacement for human players.
Relationship to BackroomsEngine
BackroomsEngine provides the native client, server runtime, renderer, world generation, physics, chemistry, environmental air, gameplay simulation, networking, persistence contracts, and tools. BackroomsMMO.com provides account, shard, social, moderation, consent, replay, and related online services. The game uses shared identity and state across those layers.
The related technical page is BackroomsEngine. The public project homepage is https://backroomsmmo.com.
Technical Overview
BackroomsMMO uses a mixed architecture. The native runtime is built with BackroomsEngine, a C++20 engine. The web platform is built in PHP and provides the account, website, server browser, replay library, and online support layer.
The native client and server handle realtime play. The web layer handles player-facing account and session workflows. The server sits between them as the authority for online play, while the website provides identity and supporting services.
The main technical themes are:
- native realtime rendering and gameplay through BackroomsEngine
- dedicated server authority for online sessions
- account-backed character selection
- deterministic world generation and streamed chunks
- replay capture and library support
- social and group systems
- moderation controls suitable for a public online game
- test coverage for game access, authority, private state handling, and release safety
Development Status
BackroomsMMO is still in development. It has enough structure to show the intended shape of the project: a playable online Backrooms game with persistent identity, server-backed sessions, replay tools, social systems, and a native engine designed around procedural survival spaces.
The project should be understood as an active build rather than a finished public MMO. Many systems are already present in source form, but the exact public feature set may change as the game is tested, hardened, and prepared for wider use.
See Also
References
Discussion log
Use comments for sourcing notes, corrections, and disputed details.
No comments yet.