In this article
OPEN//77 had a very world-editor-heavy day, and it is the kind of progress that matters far beyond tools. The NCWE closed beta is now live with applications on open2077.net, approved-access checks inside the editor, and a big wave of improvements to performance, stability, collaboration, and terrain editing. For anyone following Cyberpunk 2077 multiplayer or waiting for a serious Cyberpunk 2077 multiplayer mod, this is a meaningful step toward custom online spaces built for Night City.
NCWE closed beta applications are now live
The biggest public-facing change is simple: NCWE now has a proper closed beta application flow.
OPEN//77 accounts can apply through the new NCWE page on the website, and the platform now handles beta application review and approved access. That gives the team a controlled way to bring testers in while keeping the process tied to real OPEN//77 accounts.
Inside NCWE Studio, the closed beta gate is also active. During this phase, using the editor requires an OPEN//77 account with beta access unless the user is an OPEN//77 administrator. In plain terms, the website and the editor are now connected as one real beta program instead of a loose manual test.
That matters because NCWE is no longer just an experiment. It is becoming part of the wider OPEN//77 ecosystem for future creators, server owners, and world builders.
Cloud projects and live collaboration for shared worlds
A huge addition landed for NCWE Studio: cloud saves and live collaboration.
Approved users can now save projects to the cloud, open projects from the cloud, browse versions, and manage shared worlds. On top of that, NCWE now has live sessions for collaborative work. This is the kind of feature set that changes a world editor from “something one person uses locally” into a team tool.
For a future Cyberpunk 2077 RP server or any custom Night City online experience, collaboration is a big deal. Custom districts, event spaces, race routes, social hubs, interiors, or terrain-heavy set pieces all become much easier to build when multiple people can work in the same ecosystem.
The editor still does not force account use for everything by default, but cloud and collaboration features are now connected to OPEN//77 accounts where that makes sense.
Major NCWE Studio performance gains
NCWE Studio also received a substantial optimization pass.
The headline result is much better responsiveness during long editing routes, with lower frame times, fewer severe frame spikes, and reduced pause time from garbage collection. The exact internal work is less important than the practical result: the editor feels less stuttery and more dependable during real use.
That is especially important for large projects. A world editor that slows down under load becomes frustrating fast. A world editor that stays responsive makes iteration possible, and iteration is what creates better custom content for Cyberpunk 2077 co-op, RP, and dedicated server communities.
Early beta crashes fixed quickly
The first wave of tester feedback already paid off.
Several crash and usability issues were addressed, including problems around file dialogs, fail-fast behavior, and a specific UI-thread re-entry crash that could hit shortly after startup. Diagnostics were also improved so the team can react faster when testers run into trouble.
This is exactly what a closed beta is for: getting the rough edges exposed early and fixing them before a much wider rollout. It is not flashy work, but it is some of the most valuable progress for a tool that people need to trust.
Terrain sculpting, cutting, and painting are now in
One of the coolest additions of the day is terrain editing.
NCWE Studio can now sculpt, cut, and paint the game’s terrain, and export those changes back in a form that matches the game much more closely. The export work was refined so terrain cell buffers and positions line up properly for in-game validation.
That unlocks much more than small cosmetic changes. Terrain tools enable builders to reshape spaces, create custom landmarks, carve out event zones, build pads and paths, and generally push beyond simple object placement.
A showcase generator was also added to produce a project demonstrating each terrain brush in-game, making testing and visual verification easier.
For the long-term vision of Cyberpunk 2077 dedicated server communities, this is exciting because terrain editing expands what custom worlds can actually become.
More languages for NCWE testers
NCWE Studio is also becoming more accessible internationally.
The interface now supports English by default, plus French, Spanish, Japanese, Polish, and Brazilian Portuguese. Language selection is available in the interface, and automatic language picking has been expanded as well.
This is a practical quality-of-life improvement, but it also says something bigger: NCWE is being prepared for a broader community, not just a tiny internal test group.
Why this matters for OPEN//77
Today’s changes were not about adding one flashy gameplay feature to the CP2077 multiplayer experience. They were about building the infrastructure for creation.
A multiplayer project lives or dies on the quality of its worlds, events, and server-side creativity. With NCWE moving into closed beta, gaining collaboration, improving stability, and adding real terrain editing, OPEN//77 is laying groundwork for better custom experiences in the future.
For players, the short version is easy: the tools for building new Night City experiences just got a lot more serious.
For future server owners, the signal is even clearer: OPEN//77 is investing in the pipeline that can eventually power custom spaces, shared development, and richer world design for the wider Cyberpunk 2077 online scene.
About OPEN//77
OPEN//77 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, read the docs to host your own, or join the Discord to follow development. This devblog is published daily, straight from the work the team shipped that day.