--- title: "Build 82 opens server building and upgrades in-world screens" date: "2026-09-18" description: "Build 82 improves Cyberpunk 2077 multiplayer with better player replication, remote camera screens, and server building access for all Alpha members." tags: ["cyberpunk-2077-multiplayer", "cyberpunk-2077-rp-server", "cyberpunk-2077-dedicated-server", "night-city-online"] --- OPEN//77’s latest update delivers Build 82, with a strong mix of multiplayer polish, creator-facing features, and broader access for future server owners. The headline changes are better player-facing replication, new remote camera support for in-world surfaces, and server building access opening up to all Alpha members. For anyone following the future of **Cyberpunk 2077 multiplayer** and **Cyberpunk 2077 dedicated server** tooling, this is a meaningful step forward. ## Build 82 brings better in-world screens and camera-driven experiences The standout feature in this release is support for independent remote render cameras that can be used with map surfaces and display-style setups. That unlocks more creative options for servers that want live views on screens, surveillance-style scenes, custom venues, events, or immersive world interactions. For players, the value is simple: Night City can feel more alive when servers are able to show camera feeds and build interactive spaces that go beyond static props or menu-only interfaces. For creators, this is the kind of feature that can help a **Cyberpunk 2077 RP server** stand out with distinctive locations and roleplay tools. The same release also includes improvements aimed at making these systems behave more safely around the game’s UI and editing flows. That should make custom setups easier to work with and less likely to run into awkward control conflicts. ## Multiplayer character movement looks more natural Build 82 also adds replicated body heading in multiplayer. That is a small line in a changelog, but it matters in practice. When other players turn, move, or reposition, the way their bodies face is an important part of readability. Better heading replication helps online interactions feel cleaner and more believable, especially in social scenes, roleplay, and close-quarters encounters. In a project focused on **Cyberpunk 2077 online** play, these details add up quickly. This kind of polish does not always make for flashy screenshots, but it improves the moment-to-moment feel of seeing other people in the world with you. ## Safer restart behavior for server-managed access Another user-visible improvement in this update is better restart safety for private grants. The important takeaway is reliability. When a server restarts, players and owners both want systems to come back cleanly and predictably. Tightening restart handling reduces edge-case problems and helps keep managed access behaving more consistently. That matters more and more as OPEN//77 moves closer to the kind of persistent environments expected from serious **CP2077 multiplayer** communities. ## Server building is now open to all Alpha members This is one of the biggest community-facing changes of the day: server building on open2077.net is now open to all Alpha members. That means more people can start experimenting earlier, whether the goal is a private hangout, a prototype co-op space, or the early foundations of a larger roleplay project. Opening access this way is a strong sign that the platform is maturing and that the team wants more hands on the tooling. For future server owners, this is the practical kind of progress that matters. Access to building tools is what turns interest into actual projects. ## New guides for maps, cameras and native API usage The website also published new and updated documentation covering remote cameras, map customization, WebUI tabs, and native API references. That matters because features only become truly useful when creators can learn them without digging through scattered notes. Better documentation makes it easier for Alpha members to understand what is possible, especially as the mod grows beyond basic connection and movement into richer world-building systems. For the broader **Cyberpunk 2077 multiplayer mod** effort, good docs are part of the product. ## Large-scale RP evaluations continue to pressure-test the platform The devkit side of the project spent time running broad RP-focused evaluations across identity, inventory, banking, jobs, housing, immersion, crime, admin systems, and many real Night City landmarks. That does not mean every one of those systems is suddenly a finished product for public play. What it does mean is that the platform is being tested against the actual demands of roleplay gameplay loops instead of only isolated technical demos. That kind of pressure-testing is important for the future of **Cyberpunk 2077 co-op** and RP servers alike. It helps expose limits, confirms what already works, and gives the team a clearer view of what needs to scale before wider availability. ## Why this update matters Today’s progress is exciting because it improves three things at once: immersion, reliability, and access. Players benefit from better-looking multiplayer movement and the promise of more interesting in-world spaces. Server creators get new camera-driven possibilities plus clearer docs. Future owners get a bigger opportunity to start building now that Alpha-wide server creation is open. Build 82 is not just about one feature. It is about OPEN//77 becoming more capable as a foundation for **Night City online** experiences, from simple social servers to more ambitious roleplay worlds. --- ## About OPEN//77 [OPEN//77](https://open2077.net) is a free, in-development **multiplayer mod for Cyberpunk 2077**: play online with other players in Night City on community-hosted **dedicated servers**, with synced combat, vehicles and world state, an account-backed launcher, and Lua-scriptable servers for co-op, freeroam and RP. Browse [servers](https://open2077.net/servers), read the [docs](https://open2077.net/docs) to host your own, or join the [Discord](https://discord.open2077.net) to follow development. This devblog is published daily, straight from the work the team shipped that day.