# OPEN//77 > OPEN//77 is an open, community-run multiplayer platform for Cyberpunk 2077. It is not a single server: it is the client, dedicated server and scripting layer that lets communities host and script their own persistent Night City worlds. This site documents the platform and its Lua API, and hosts the server browser. The project is pre-alpha and unaffiliated with CD PROJEKT RED. ## Status - Stage: pre-alpha. There is no public build, no download and no release date. - The server browser at /servers is populated with clearly labelled demo data, not live servers. - The documentation describes software under construction; APIs can change. - Unaffiliated with CD PROJEKT RED. Playing requires your own legal copy of Cyberpunk 2077. - Documentation synced from the platform wiki on 2026-08-21. ## Site - [Home](https://open2077.net): what the platform is, for players and for server owners. - [Server browser](https://open2077.net/servers): directory UI, currently demo listings. - [Create a server](https://open2077.net/create): what hosting an OPEN//77 world will involve. - [Community](https://open2077.net/community): how to follow the project and join the alpha. - [Brand kit](https://open2077.net/brand): logo, mark, colours and social assets. ## Introduction - [OPEN//77 documentation](https://open2077.net/docs.md): How OPEN//77 packages gameplay as resources: the session model, the authoritative server, a hello-world manifest, and the conventions shared by every Lua API. - [How OPEN//77 works](https://open2077.net/docs/platform.md): What OPEN//77 is and is not, how players connect, why it is built on dedicated servers rather than peer-to-peer sessions, the project roadmap, and answers to the questions people ask most. ## Getting started - [Server resources](https://open2077.net/docs/server-resources.md): Resource manifests, the client and server runtime split, signing and download, hot reload, and the security model around resources the server hands to connecting players. ## Identity and access control - [Player identity](https://open2077.net/docs/identity.md): Durable player identifiers, session-scoped ids, display names, the rename flow, and what a game server can actually verify about a connecting player. - [Commands and ACL](https://open2077.net/docs/server-acl.md): Exporting a public identity, whitelisting a player, and declaring restricted server commands behind the access control list. ## Server API - [Complete server Lua API](https://open2077.net/docs/server-api.md): Every dedicated-server global, CyberM namespace, permission, constant and result shape: scheduler, events, commands, players, combat, routing buckets, loot, vehicles, NPCs, elevators, database and logging. - [Official resource exports](https://open2077.net/docs/resource-exports.md): Every client export published by the official OPEN//77 resource packages, with signatures per package and how to call them safely across resources. ## World systems - [Vehicles](https://open2077.net/docs/vehicles.md): Network vehicle identity, streaming, authority leases, seats and proxy replication, doors and glass, damage profiles, and the full asymmetric server and client Lua API. - [NPCs](https://open2077.net/docs/npcs.md): Server-owned NPCs: templates, streaming, authority leases, the task queue, health and damage, events, the read-only client API, and the current limitations. - [Elevators](https://open2077.net/docs/elevators.md): Server-authoritative native lifts: adopting a LiftDevice, bucket and chunk streaming, movement and pause control, late-join catch-up, and the reference resource commands. - [Loot](https://open2077.net/docs/loot.md): Authoritative ground drops: creating and projecting item drops, validating pickups, the onLootPickup hook, and where native UI ends and server authority begins. - [Time and weather](https://open2077.net/docs/weather.md): Synchronised session time and weather: the network model, shared configuration, ACL-gated commands, random weather events, and the server and client APIs. ## Client and interface - [Blips and map pins](https://open2077.net/docs/blips.md): Vanilla map markers and mappins: creating and updating blips, attaching them to entities, custom icon metadata, stable aliases, and the complete sprite catalogue. - [Contextual interactions](https://open2077.net/docs/interactions.md): Custom world and NPC prompts: attaching interactions to players or NPCs, multiple actions and hold keys, the definition reference, and keeping server authority intact. - [Notifications](https://open2077.net/docs/notifications.md): Reusable WebUI toasts: local client notifications, server-targeted delivery, updating and dismissing, queue limits, positions and progress. - [Visual and audio effects](https://open2077.net/docs/effects.md): Resource-owned world and entity visual effects plus spatialised sound effects, with inspection, cleanup and the curated alias catalogues. - [Chat](https://open2077.net/docs/chat.md): Chat messages, slash commands, completion, and the built-in developer commands available to every player. - [Clipboard](https://open2077.net/docs/clipboard.md): The write-only client clipboard API, the clipboard.write permission, failure reasons, and the built-in /pos and /rot transform commands. - [Client persistent KVP](https://open2077.net/docs/client-kvp.md): Endpoint- and resource-isolated local key/value persistence: CRUD, search, atomic operations, quotas, and why it must never hold secrets. ## Reference - [Lua API reference](https://open2077.net/docs/api.md): Searchable reference for every registered OPEN//77 Lua function, separated by runtime so a client projection is never mistaken for server authority. - [Game data reference](https://open2077.net/docs/data-reference.md): NPC templates, vehicle records, seat and door constants, items, weapons, effects, sounds, animations and sprite catalogues, with explicit support levels. - [Privileged debug runtime](https://open2077.net/docs/debug-runtime.md): The ACL-gated in-game Lua laboratory: client execution, native lab commands, the REDscript bridge, and the limits that keep it out of gameplay code. ## API reference by namespace ### Server runtime — 43 functions Runs on the dedicated server and is authoritative: state written here is the truth every client is told about. - [CyberM.vehicles](https://open2077.net/docs/api/server/cyberm-vehicles.md): 43 functions. ### Client runtime — 215 functions Runs inside the game process. Reads and presentation are local; anything that changes shared state has to go through the server. - [Globals](https://open2077.net/docs/api/client/globals.md): 19 functions. - [CyberM.animations](https://open2077.net/docs/api/client/cyberm-animations.md): 5 functions. - [CyberM.appearance](https://open2077.net/docs/api/client/cyberm-appearance.md): 5 functions. - [CyberM.assets](https://open2077.net/docs/api/client/cyberm-assets.md): 2 functions. - [CyberM.blips](https://open2077.net/docs/api/client/cyberm-blips.md): 18 functions. - [CyberM.camera](https://open2077.net/docs/api/client/cyberm-camera.md): 6 functions. - [CyberM.character](https://open2077.net/docs/api/client/cyberm-character.md): 18 functions. - [CyberM.clipboard](https://open2077.net/docs/api/client/cyberm-clipboard.md): 1 function. - [CyberM.debug](https://open2077.net/docs/api/client/cyberm-debug.md): 3 functions. - [CyberM.doors](https://open2077.net/docs/api/client/cyberm-doors.md): 23 functions. - [CyberM.elevators](https://open2077.net/docs/api/client/cyberm-elevators.md): 4 functions. - [CyberM.environment](https://open2077.net/docs/api/client/cyberm-environment.md): 6 functions. - [CyberM.events](https://open2077.net/docs/api/client/cyberm-events.md): 3 functions. - [CyberM.exports](https://open2077.net/docs/api/client/cyberm-exports.md): 1 function. - [CyberM.input](https://open2077.net/docs/api/client/cyberm-input.md): 2 functions. - [CyberM.inspector](https://open2077.net/docs/api/client/cyberm-inspector.md): 3 functions. - [CyberM.json](https://open2077.net/docs/api/client/cyberm-json.md): 2 functions. - [CyberM.kvp](https://open2077.net/docs/api/client/cyberm-kvp.md): 11 functions. - [CyberM.loot](https://open2077.net/docs/api/client/cyberm-loot.md): 6 functions. - [CyberM.markers](https://open2077.net/docs/api/client/cyberm-markers.md): 5 functions. - [CyberM.nameplates](https://open2077.net/docs/api/client/cyberm-nameplates.md): 4 functions. - [CyberM.net](https://open2077.net/docs/api/client/cyberm-net.md): 2 functions. - [CyberM.network](https://open2077.net/docs/api/client/cyberm-network.md): 7 functions. - [CyberM.npcs](https://open2077.net/docs/api/client/cyberm-npcs.md): 5 functions. - [CyberM.players](https://open2077.net/docs/api/client/cyberm-players.md): 6 functions. - [CyberM.Promise](https://open2077.net/docs/api/client/cyberm-promise.md): 2 functions. - [CyberM.resource](https://open2077.net/docs/api/client/cyberm-resource.md): 6 functions. - [CyberM.runtime](https://open2077.net/docs/api/client/cyberm-runtime.md): 2 functions. - [CyberM.session](https://open2077.net/docs/api/client/cyberm-session.md): 3 functions. - [CyberM.settings](https://open2077.net/docs/api/client/cyberm-settings.md): 3 functions. - [CyberM.sfx](https://open2077.net/docs/api/client/cyberm-sfx.md): 4 functions. - [CyberM.time](https://open2077.net/docs/api/client/cyberm-time.md): 1 function. - [CyberM.travel](https://open2077.net/docs/api/client/cyberm-travel.md): 4 functions. - [CyberM.vehicles](https://open2077.net/docs/api/client/cyberm-vehicles.md): 6 functions. - [CyberM.vfx](https://open2077.net/docs/api/client/cyberm-vfx.md): 6 functions. - [CyberM.webui](https://open2077.net/docs/api/client/cyberm-webui.md): 2 functions. - [WebUI.Page](https://open2077.net/docs/api/client/webui-page.md): 9 functions. ## Optional - [Complete documentation in one file](https://open2077.net/llms-full.txt): every guide and the whole API reference concatenated. - [Complete API reference](https://open2077.net/docs/api.md): all 258 functions in one Markdown document. - [HTML documentation index](https://open2077.net/docs): the same content as web pages. - [Site source](https://github.com/Open2077/open77-app): the repository this site is built from. - The platform repository is not public yet, so guides that reference files outside the wiki name the path instead of linking to it. Pages indexed: 22 documentation pages, 38 API namespaces.