Diff: BackroomsMMO

{{Infobox project|name=BackroomsMMO|type=Online multiplayer game and web platform|status=Pre-public-release development|website=https://backroomsmmo.com/|platform=Windows game client, dedicated server, PHP web portal|technology=PHP 8.3, C++20, CMake, vcpkg|related=[[BackroomsEngine]], [[BackroomsHost]], [[BackroomsVideo]], [[BackroomsAtlas]]}}

{{Infobox project|name=BackroomsMMO|type=Online multiplayer game and web platform|status=Pre-public-release development|website=https://backroomsmmo.com/|platform=Windows game client, dedicated server, PHP web portal|technology=PHP 8.3, C++20, CMake, vcpkg|related=[[BackroomsEngine]], [[BackroomsHost]], [[BackroomsVideo]], [[BackroomsAtlas]]}}

'''BackroomsMMO''' is a pre-public-release online multiplayer game project and account platform built around the Backrooms setting. The project combines a native game client, dedicated server runtime, website-backed authentication, character management, private servers, replays, social systems, moderation tools, and deployment workflows. The public-facing website is normally referred to as '''BackroomsMMO.com''', while the native game and server code is provided by [[BackroomsEngine]].

'''BackroomsMMO''' is a pre-public-release online multiplayer game project and account platform built around the Backrooms setting. The project combines a native game client, dedicated server runtime, website-backed authentication, character management, private servers, replays, social systems, moderation tools, and deployment workflows. The public-facing website is normally referred to as '''BackroomsMMO.com''', while the native game and server code is provided by [[BackroomsEngine]].

The project is designed as more than a simple download page. Its web layer acts as the identity system, account portal, game access gate, server browser, launcher service, replay library, private server manager, live operations panel, and control plane for dedicated shards. Its native layer provides the rendered game client, server authority, online protocol, procedural world streaming, gameplay state, voice, replay capture, and tools used to package or test the runtime.

The project is designed as more than a simple download page. Its web layer acts as the identity system, account portal, game access gate, server browser, launcher service, replay library, private server manager, live operations panel, and control plane for dedicated shards. Its native layer provides the rendered game client, server authority, online protocol, procedural world streaming, gameplay state, voice, replay capture, and tools used to package or test the runtime.

BackroomsMMO is part of a wider Backrooms software ecosystem. It is connected to projects such as [[BackroomsEngine]], [[BackroomsHost]], [[BackroomsVideo]], [[BackroomsAtlas]], and related community or media sites. In that ecosystem, BackroomsMMO is the playable online product. It is the place where user accounts, characters, servers, multiplayer sessions, and game-facing services meet.

BackroomsMMO is part of a wider Backrooms software ecosystem. It is connected to projects such as [[BackroomsEngine]], [[BackroomsHost]], [[BackroomsVideo]], [[BackroomsAtlas]], and related community or media sites. In that ecosystem, BackroomsMMO is the playable online product. It is the place where user accounts, characters, servers, multiplayer sessions, and game-facing services meet.

== Overview ==

== Overview ==

BackroomsMMO is structured around a website and a native runtime. The website manages user identity, permissions, server listings, private server ownership, replay processing, social data, challenge lobbies, runtime manifests, and administrative control. The native runtime provides the actual game client and dedicated server that players connect to.

BackroomsMMO is structured around a website and a native runtime. The website manages user identity, permissions, server listings, private server ownership, replay processing, social data, challenge lobbies, runtime manifests, and administrative control. The native runtime provides the actual game client and dedicated server that players connect to.

The website is a PHP 8.3 application with a lightweight custom MVC structure. Its source tree contains controllers, models, services, views, database migrations, command-line scripts, and smoke tests. The application uses models for users, tokens, shards, private servers, game servers, replays, characters, host nodes, bans, announcements, control deployments, and game server commands. Services handle account access, game authentication, runtime authority, social systems, private server provisioning, replay libraries, control-plane packages, remote deployment, support, QA, MFA, session management, and BackroomsHost integration.

The website is a PHP 8.3 application with a lightweight custom MVC structure. Its source tree contains controllers, models, services, views, database migrations, command-line scripts, and smoke tests. The application uses models for users, tokens, shards, private servers, game servers, replays, characters, host nodes, bans, announcements, control deployments, and game server commands. Services handle account access, game authentication, runtime authority, social systems, private server provisioning, replay libraries, control-plane packages, remote deployment, support, QA, MFA, session management, and BackroomsHost integration.

The project started as a fuller first deploy rather than a bare scaffold. It includes account registration, login, logout, remember-me sessions, email verification, dashboard and account settings, character slot scaffolding, server browser and shard list, announcements, admin controls, permissions, bans, shard creation, website-backed game auth token issuance, dedicated server token verification, and bootstrap endpoints for the launcher or game menu.

The project started as a fuller first deploy rather than a bare scaffold. It includes account registration, login, logout, remember-me sessions, email verification, dashboard and account settings, character slot scaffolding, server browser and shard list, announcements, admin controls, permissions, bans, shard creation, website-backed game auth token issuance, dedicated server token verification, and bootstrap endpoints for the launcher or game menu.

== Relationship to BackroomsEngine ==

== Relationship to BackroomsEngine ==

BackroomsMMO relies on [[BackroomsEngine]] for the native game runtime. The engine builds the main game executable, the dedicated server, launcher tools, replay player, model tools, mods tool, load bot, admin utilities, and regression tests. BackroomsMMO.com supplies the online services around that runtime.

BackroomsMMO relies on [[BackroomsEngine]] for the native game runtime. The engine builds the main game executable, the dedicated server, launcher tools, replay player, model tools, mods tool, load bot, admin utilities, and regression tests. BackroomsMMO.com supplies the online services around that runtime.

The relationship is deliberately split. BackroomsEngine handles frame-time game work: rendering, input, movement, world generation, chunk streaming, audio, voice, replay capture, networking, authoritative server state, and local tools. BackroomsMMO.com handles identity, persistence, permissions, server discovery, private server ownership, runtime configuration, deployment state, web dashboards, and game-facing HTTP APIs.

The relationship is deliberately split. BackroomsEngine handles frame-time game work: rendering, input, movement, world generation, chunk streaming, audio, voice, replay capture, networking, authoritative server state, and local tools. BackroomsMMO.com handles identity, persistence, permissions, server discovery, private server ownership, runtime configuration, deployment state, web dashboards, and game-facing HTTP APIs.

This split lets the game client authenticate through the website, request a join ticket, pick a character, find a shard, download launcher or runtime manifests, and connect to a dedicated server. The dedicated server then verifies the player with the website, reports live status through heartbeats, receives queued control commands, and can persist or request authority data through website endpoints.

This split lets the game client authenticate through the website, request a join ticket, pick a character, find a shard, download launcher or runtime manifests, and connect to a dedicated server. The dedicated server then verifies the player with the website, reports live status through heartbeats, receives queued control commands, and can persist or request authority data through website endpoints.

== Website and Account Platform ==

== Website and Account Platform ==

BackroomsMMO.com is the account portal for the game. It supports registration, login, logout, email verification, account settings, MFA, remembered client sessions, account status pages, warnings, support tickets, and user-facing dashboard views.

BackroomsMMO.com is the account portal for the game. It supports registration, login, logout, email verification, account settings, MFA, remembered client sessions, account status pages, warnings, support tickets, and user-facing dashboard views.

The account system is not only for the website. It is part of the game security model. The native client can authenticate against the website, and the dedicated server can verify a player's session before allowing access. The site can also decide whether a user has game access, whether official shard access is allowed, whether a user is blocked, and which permissions or admin flags apply.

The account system is not only for the website. It is part of the game security model. The native client can authenticate against the website, and the dedicated server can verify a player's session before allowing access. The site can also decide whether a user has game access, whether official shard access is allowed, whether a user is blocked, and which permissions or admin flags apply.

The account portal includes user preferences, preferred characters, preferred shards, social privacy, voice consent, active sessions, and support flows. It also includes staff application and moderation support in later migrations. These pieces make the account system usable for both players and operators.

The account portal includes user preferences, preferred characters, preferred shards, social privacy, voice consent, active sessions, and support flows. It also includes staff application and moderation support in later migrations. These pieces make the account system usable for both players and operators.

== Characters and Progression ==

== Characters and Progression ==

BackroomsMMO includes character slots and game-facing character APIs. Players can create, rename, delete, and select characters. Character records include user ownership, slot data, display names, status, shard preferences, and progression-related fields.

BackroomsMMO includes character slots and game-facing character APIs. Players can create, rename, delete, and select characters. Character records include user ownership, slot data, display names, status, shard preferences, and progression-related fields.

The website stores and serialises character data so the client can present a character picker and pass a selected character into the online session. The game auth service can issue join tickets tied to a user, character, and shard. The server can consume the ticket and load persistent state rather than trusting the client to invent identity or progression.

The website stores and serialises character data so the client can present a character picker and pass a selected character into the online session. The game auth service can issue join tickets tied to a user, character, and shard. The server can consume the ticket and load persistent state rather than trusting the client to invent identity or progression.

== Shards and Server Browser ==

== Shards and Server Browser ==

BackroomsMMO uses the term '''shard''' for game server instances that players can join. The website stores game shards, game servers, host nodes, shard templates, control deployments, server commands, runtime metrics, and player sessions. The server browser API provides public or permitted shard data to the game client.

BackroomsMMO uses the term '''shard''' for game server instances that players can join. The website stores game shards, game servers, host nodes, shard templates, control deployments, server commands, runtime metrics, and player sessions. The server browser API provides public or permitted shard data to the game client.

Shard records include server identity, status, region, host information, player counts, access rules, build version, world profile, asset library information, and other data needed by clients. The client can request bootstrap data and server lists from the website, then connect to a chosen shard with a join ticket.

Shard records include server identity, status, region, host information, player counts, access rules, build version, world profile, asset library information, and other data needed by clients. The client can request bootstrap data and server lists from the website, then connect to a chosen shard with a join ticket.

Region selection is handled by a shard placement service. The web layer can choose nodes, expose public region options, rank shards for a preferred region, and support private hosting location options. This allows the platform to present different official and private server locations while keeping placement logic centralised.

Region selection is handled by a shard placement service. The web layer can choose nodes, expose public region options, rank shards for a preferred region, and support private hosting location options. This allows the platform to present different official and private server locations while keeping placement logic centralised.

== Game Authentication and Join Tickets ==

== Game Authentication and Join Tickets ==

BackroomsMMO's auth path is website-backed. The client logs in to the website, receives a session token, chooses or receives a character, requests a join ticket, and uses that ticket when connecting to the dedicated server. The dedicated server verifies the token or consumes the join ticket through the website before accepting the player.

BackroomsMMO's auth path is website-backed. The client logs in to the website, receives a session token, chooses or receives a character, requests a join ticket, and uses that ticket when connecting to the dedicated server. The dedicated server verifies the token or consumes the join ticket through the website before accepting the player.

This design keeps the server from trusting a username or local account id sent by the client. Admin status, permissions, and access are derived from website responses. That matters for moderation, staff tooling, private server membership, official shard access, and future in-game command paths.

This design keeps the server from trusting a username or local account id sent by the client. Admin status, permissions, and access are derived from website responses. That matters for moderation, staff tooling, private server membership, official shard access, and future in-game command paths.

The website exposes game APIs for login, resume, verification, current user data, characters, preferences, private server operations, join requests, bootstrap data, server browser data, asset manifests, server runtime manifests, replay upload and conversion, social features, clan data, challenge lobbies, and live map data. The article does not list sensitive deployment values because those belong in private configuration, not in public documentation.

The website exposes game APIs for login, resume, verification, current user data, characters, preferences, private server operations, join requests, bootstrap data, server browser data, asset manifests, server runtime manifests, replay upload and conversion, social features, clan data, challenge lobbies, and live map data. The article does not list sensitive deployment values because those belong in private configuration, not in public documentation.

== Runtime Authority ==

== Runtime Authority ==

A major design goal of BackroomsMMO is to move important online state away from purely local client decisions. The source contains runtime authority services and server endpoints for consuming join tickets, loading state, persisting state, applying state patches, resolving loot rolls, handling combat actions, processing social commands, updating clan bases, and refreshing voice consent.

A major design goal of BackroomsMMO is to move important online state away from purely local client decisions. The source contains runtime authority services and server endpoints for consuming join tickets, loading state, persisting state, applying state patches, resolving loot rolls, handling combat actions, processing social commands, updating clan bases, and refreshing voice consent.

The authority model covers movement, vitals, inventory, persistence, chat, loot, combat, currency, party systems, clan chat, world state, enemy state, and trade or crafting flows. The dedicated server and website exchange state through controlled APIs so that gameplay records can be checked, persisted, and moderated.

The authority model covers movement, vitals, inventory, persistence, chat, loot, combat, currency, party systems, clan chat, world state, enemy state, and trade or crafting flows. The dedicated server and website exchange state through controlled APIs so that gameplay records can be checked, persisted, and moderated.

== Private Servers ==

== Private Servers ==

Private servers are a major BackroomsMMO feature. The website includes private server plans, private server membership, ownership roles, server actions, settings updates, funding pools, billing portal support, coin rental, card-payment gating, hosting location options, live shard heartbeat sync, runtime metadata, private profiles, server migration, retained server state, export bundles, and admin tools.

Private servers are a major BackroomsMMO feature. The website includes private server plans, private server membership, ownership roles, server actions, settings updates, funding pools, billing portal support, coin rental, card-payment gating, hosting location options, live shard heartbeat sync, runtime metadata, private profiles, server migration, retained server state, export bundles, and admin tools.

The code defines private server plan sizes for 2, 4, 8, 16, and 32 player servers. The service layer can expose plans, calculate coin or monthly amounts, decide hosting locations, list servers available to a user, check membership roles, update settings, request runtime actions, migrate servers, and export private server bundles.

The code defines private server plan sizes for 2, 4, 8, 16, and 32 player servers. The service layer can expose plans, calculate coin or monthly amounts, decide hosting locations, list servers available to a user, check membership roles, update settings, request runtime actions, migrate servers, and export private server bundles.

Private server settings are also connected to the game runtime. Updates can queue runtime commands so live server settings can change without relying only on static files. The website can inspect and create export bundles, including manifests and replay references, and it contains smoke tests to ensure private server exports and seed handling stay intact.

Private server settings are also connected to the game runtime. Updates can queue runtime commands so live server settings can change without relying only on static files. The website can inspect and create export bundles, including manifests and replay references, and it contains smoke tests to ensure private server exports and seed handling stay intact.

The private server system is also where mod policy becomes important. BackroomsEngine supports mods for singleplayer and private servers that explicitly allow them, while official MMO servers block mods. This allows private environments to be more flexible without weakening official shard integrity.

The private server system is also where mod policy becomes important. BackroomsEngine supports mods for singleplayer and private servers that explicitly allow them, while official MMO servers block mods. This allows private environments to be more flexible without weakening official shard integrity.

== Challenges, Social Systems, and Clans ==

== Challenges, Social Systems, and Clans ==

BackroomsMMO includes several multiplayer and community systems beyond basic login. The web API includes social overview, friend requests, friend responses, friend join tickets, privacy updates, message rooms, direct messages, clans, challenge lobbies, and official challenge start or completion endpoints.

BackroomsMMO includes several multiplayer and community systems beyond basic login. The web API includes social overview, friend requests, friend responses, friend join tickets, privacy updates, message rooms, direct messages, clans, challenge lobbies, and official challenge start or completion endpoints.

Database migrations add friend requests, friendships, message rooms, message room members, messages, clans, clan members, clan invites, parties, party members, party invites, trade offers, challenge lobbies, challenge members, challenge rules, difficulty, objectives, rewards, and shard lifecycle support. Later migrations include scoped clan bases so clan data can be separated by public or private context.

Database migrations add friend requests, friendships, message rooms, message room members, messages, clans, clan members, clan invites, parties, party members, party invites, trade offers, challenge lobbies, challenge members, challenge rules, difficulty, objectives, rewards, and shard lifecycle support. Later migrations include scoped clan bases so clan data can be separated by public or private context.

These systems make the project closer to an MMO service than a standalone game launcher. Players can have persistent identities, relationships, groups, private spaces, challenge sessions, messages, and social privacy settings that exist outside a single game process.

These systems make the project closer to an MMO service than a standalone game launcher. Players can have persistent identities, relationships, groups, private spaces, challenge sessions, messages, and social privacy settings that exist outside a single game process.

== Replays and BackroomsVideo ==

== Replays and BackroomsVideo ==

BackroomsMMO includes a replay library. Players or clients can upload replay files, check replay status, convert replays, export videos, download replay files, preview MP4 files, and set replay visibility. The website has a replay controller for browser-facing replay management and API endpoints for game-facing replay upload and processing.

BackroomsMMO includes a replay library. Players or clients can upload replay files, check replay status, convert replays, export videos, download replay files, preview MP4 files, and set replay visibility. The website has a replay controller for browser-facing replay management and API endpoints for game-facing replay upload and processing.

The replay service can store uploaded replays, decorate replay records for display, stream downloads, convert replay files to MP4 profiles, export replay media to BackroomsVideo, and report exporter health. The system supports public replay listing through later migrations and links private server replays with server export flows.

The replay service can store uploaded replays, decorate replay records for display, stream downloads, convert replay files to MP4 profiles, export replay media to BackroomsVideo, and report exporter health. The system supports public replay listing through later migrations and links private server replays with server export flows.

BackroomsEngine supplies the runtime capture side. It has a replay ring that records snapshots, camera state, player vitals, audio events, voice frames, and relevant gameplay state over a configured time window. BackroomsMMO.com supplies the account, library, conversion, and publishing side.

BackroomsEngine supplies the runtime capture side. It has a replay ring that records snapshots, camera state, player vitals, audio events, voice frames, and relevant gameplay state over a configured time window. BackroomsMMO.com supplies the account, library, conversion, and publishing side.

== Voice, Consent, and Mimic Features ==

== Voice, Consent, and Mimic Features ==

The project includes voice-related services and consent controls. The website has a voice consent service that stores per-user preferences, serialises consent, updates consent from account pages, handles server clip upload, clip selection, clip usage reporting, server-side consent refresh, and expired clip pruning.

The project includes voice-related services and consent controls. The website has a voice consent service that stores per-user preferences, serialises consent, updates consent from account pages, handles server clip upload, clip selection, clip usage reporting, server-side consent refresh, and expired clip pruning.

The engine side contains voice runtime, voice frames, voice playback, voice mimic data, and server modules for voice mimic and related online events. The website-side consent layer is important because voice systems can involve personal data. BackroomsMMO treats voice use as an explicit consent and control problem rather than a purely technical feature.

The engine side contains voice runtime, voice frames, voice playback, voice mimic data, and server modules for voice mimic and related online events. The website-side consent layer is important because voice systems can involve personal data. BackroomsMMO treats voice use as an explicit consent and control problem rather than a purely technical feature.

== Assets, Launcher, and Runtime Delivery ==

== Assets, Launcher, and Runtime Delivery ==

BackroomsMMO.com exposes launcher and runtime delivery endpoints. The site can serve client launcher manifests, launcher files, bootstrap files, game asset manifests, asset files, server runtime manifests, and runtime files. This allows the game client or launcher to discover required files through the web service instead of relying on manual distribution only.

BackroomsMMO.com exposes launcher and runtime delivery endpoints. The site can serve client launcher manifests, launcher files, bootstrap files, game asset manifests, asset files, server runtime manifests, and runtime files. This allows the game client or launcher to discover required files through the web service instead of relying on manual distribution only.

The BackroomsHost manifest describes BackroomsMMO.com as a website authentication, account portal, and dedicated-server control plane. It marks the app as database-backed, with a public web root, installer support, deployment metadata, preserved paths, and preview points such as accounts, shard diagnostics, node enrolment, and BackroomsHost-ready auto install flow.

The BackroomsHost manifest describes BackroomsMMO.com as a website authentication, account portal, and dedicated-server control plane. It marks the app as database-backed, with a public web root, installer support, deployment metadata, preserved paths, and preview points such as accounts, shard diagnostics, node enrolment, and BackroomsHost-ready auto install flow.

== Admin and Control Plane ==

== Admin and Control Plane ==

The admin area manages users, permissions, bans, announcements, shards, server commands, host nodes, host node commands, shard templates, world profiles, subsystem settings, private server settings, deployment profiles, control-panel package generation, remote control-panel deployment, assets, QA, staff applications, and runtime status.

The admin area manages users, permissions, bans, announcements, shards, server commands, host nodes, host node commands, shard templates, world profiles, subsystem settings, private server settings, deployment profiles, control-panel package generation, remote control-panel deployment, assets, QA, staff applications, and runtime status.

A key design decision is that dedicated servers do not need to expose a public inbound admin port for ordinary control operations. Instead, the dedicated server posts heartbeats to the website, the website returns queued commands for that shard, the server executes them locally, and then the server acknowledges completion. Supported control concepts include kick, ban, unban, freeze, unfreeze, teleport, teleport all, runtime settings, status updates, and moderation actions.

A key design decision is that dedicated servers do not need to expose a public inbound admin port for ordinary control operations. Instead, the dedicated server posts heartbeats to the website, the website returns queued commands for that shard, the server executes them locally, and then the server acknowledges completion. Supported control concepts include kick, ban, unban, freeze, unfreeze, teleport, teleport all, runtime settings, status updates, and moderation actions.

== BackroomsHost Integration ==

== BackroomsHost Integration ==

BackroomsMMO.com is designed for BackroomsHost deployment. Its application manifest describes database requirements, public web root, install hooks, auto deploy support, soft reinstall preservation for environment and storage paths, public entrypoints, admin dashboard entrypoints, and installer token support.

BackroomsMMO.com is designed for BackroomsHost deployment. Its application manifest describes database requirements, public web root, install hooks, auto deploy support, soft reinstall preservation for environment and storage paths, public entrypoints, admin dashboard entrypoints, and installer token support.

The web app includes services for BackroomsHost bridge operations, BackroomsHost auto-install, control panel package building, remote SSH deployment, and standalone control-plane provisioning. These services let the MMO site prepare or deploy supporting control-plane software to game hosts while preserving the normal BackroomsHost drop-in deployment model.

The web app includes services for BackroomsHost bridge operations, BackroomsHost auto-install, control panel package building, remote SSH deployment, and standalone control-plane provisioning. These services let the MMO site prepare or deploy supporting control-plane software to game hosts while preserving the normal BackroomsHost drop-in deployment model.

== Security and Access Control ==

== Security and Access Control ==

BackroomsMMO has several access-control layers. It has web sessions, remember tokens, email verification, permissions, bans, MFA, game auth tokens, join tickets, account access checks, game access gates, download access checks, private server membership roles, admin access rules, and server-side verification.

BackroomsMMO has several access-control layers. It has web sessions, remember tokens, email verification, permissions, bans, MFA, game auth tokens, join tickets, account access checks, game access gates, download access checks, private server membership roles, admin access rules, and server-side verification.

The game access gate is important because pre-public-release builds should not become uncontrolled public downloads. Tests check that access locks are respected and that admin users can still perform necessary internal operations. Private server export tests also verify that export streaming does not accidentally depend on public download unlocks in the wrong place.

The game access gate is important because pre-public-release builds should not become uncontrolled public downloads. Tests check that access locks are respected and that admin users can still perform necessary internal operations. Private server export tests also verify that export streaming does not accidentally depend on public download unlocks in the wrong place.

The codebase stores sensitive deployment material through configuration and encrypted or protected service layers. Public documentation should describe the existence of secure deployment flows without publishing keys, tokens, private host addresses, or secret values.

The codebase stores sensitive deployment material through configuration and encrypted or protected service layers. Public documentation should describe the existence of secure deployment flows without publishing keys, tokens, private host addresses, or secret values.

== Testing and QA ==

== Testing and QA ==

BackroomsMMO.com includes smoke tests for game access gates, MMO respawn authority, control-plane server source packaging, private server exports, and private server seed handling. It also includes command-line tools for health checks, live smoke checks, replay exporter health, realbot account provisioning, standalone control-plane provisioning, and local shard state cleanup.

BackroomsMMO.com includes smoke tests for game access gates, MMO respawn authority, control-plane server source packaging, private server exports, and private server seed handling. It also includes command-line tools for health checks, live smoke checks, replay exporter health, realbot account provisioning, standalone control-plane provisioning, and local shard state cleanup.

The wider Backrooms repository also contains predeploy QA tooling that checks the website and engine together. That reflects the nature of the project: the web layer and native layer are separate codebases, but a working release depends on both behaving correctly.

The wider Backrooms repository also contains predeploy QA tooling that checks the website and engine together. That reflects the nature of the project: the web layer and native layer are separate codebases, but a working release depends on both behaving correctly.

== Development Status ==

== Development Status ==

BackroomsMMO is under active pre-public-release development. Its architecture already covers many live-service concerns: identity, moderation, server management, private servers, challenges, replays, voice consent, asset delivery, runtime authority, and deployment. At the same time, the project documentation and source make clear that parts of the runtime are still being hardened and should be treated as current-format development work rather than a legacy compatibility product.

BackroomsMMO is under active pre-public-release development. Its architecture already covers many live-service concerns: identity, moderation, server management, private servers, challenges, replays, voice consent, asset delivery, runtime authority, and deployment. At the same time, the project documentation and source make clear that parts of the runtime are still being hardened and should be treated as current-format development work rather than a legacy compatibility product.

The project is best understood as an integrated MMO platform in progress. It is not only a website, and it is not only a game executable. It is the service layer, control layer, account layer, and operational layer around the BackroomsEngine runtime.

The project is best understood as an integrated MMO platform in progress. It is not only a website, and it is not only a game executable. It is the service layer, control layer, account layer, and operational layer around the BackroomsEngine runtime.

== See Also ==

== See Also ==

* [[BackroomsEngine]]

* [[BackroomsEngine]]

* [[BackroomsHost]]

* [[BackroomsHost]]

* [[BackroomsVideo]]

* [[BackroomsVideo]]

* [[BackroomsAtlas]]

* [[BackroomsAtlas]]

* [[Cameron Lobban]]

* [[Cameron Lobban]]

[[Category:Backrooms]]

[[Category:Backrooms]]

[[Category:Projects]]

[[Category:Projects]]

[[Category:Video games]]

[[Category:Video games]]

[[Category:Online platforms]]

[[Category:Online platforms]]