DevblogNo.026
Server discovery gets smarter, setup gets easier
OPEN//77 improves Cyberpunk 2077 multiplayer with curated server discovery, easier dedicated server setup, better launcher UX and new RP-ready NPC tools.
In this article
OPEN//77βs latest update focused on three practical areas: finding the right server, setting up a server more easily, and smoothing out a few rough edges in the game client. It is not a flashy trailer-day patch, but it is exactly the kind of work that makes a Cyberpunk 2077 multiplayer mod feel more real and more usable over time.
Better server discovery for players and communities
The public server directory now supports curation. That means the OPEN//77 team can mark servers as official or featured, giving promising communities a clearer place to stand out.
For players browsing Cyberpunk 2077 online options in the launcher or on the site, this should make the server list feel less random and more trustworthy. A curated list helps new players spot the servers that are active, supported, or especially important to the ecosystem.
There is also now support for hiding servers from public directory listings. This matters for communities that want to prepare quietly, run tests, stay private for staff, or avoid public traffic until they are ready. For a future Cyberpunk 2077 RP server owner, visibility control is a big quality-of-life feature. Not every server should appear in a public browser the moment it exists.
Together, those two changes make the directory more useful at both ends: easier to browse for players, and easier to manage for operators.
Launcher improvements for a cleaner Night City online experience
The launcher also picked up a directory polish pass. The server browser now has a more compact curated presentation, which should make it quicker to scan through available servers.
Server history artwork now persists too. That is a small detail, but good launcher UX is built from small details. When players come back to a favorite server, familiar visuals help the experience feel more polished and less temporary.
For a project like OPEN//77, this matters because the launcher is not just a download button. It is the front door to CP2077 multiplayer. Every bit of clarity and consistency helps the platform feel more stable and more ready for regular use.
Easier Cyberpunk 2077 dedicated server setup on remote hosts
One of the most practical changes in this batch is on the dedicated server side. First-run setup is now reachable across the network by default instead of only from the local machine.
In plain language: if a server owner spins up a fresh VPS, the initial setup flow is no longer awkwardly locked to localhost. Remote onboarding becomes much more straightforward.
That is a big win for anybody planning to host a Cyberpunk 2077 dedicated server. A lot of multiplayer projects work fine on a developer machine, then become annoying the moment somebody tries to deploy them on a rented server box. This update removes one of those friction points.
It is the kind of change most players will never see directly, but they will feel the effect later because it lowers the barrier for new communities to launch servers.
Better input behavior for in-game web UI
The client also received a useful input fix for web-based interfaces. Selected keys can now be consumed by the UI without interfering with normal gameplay input.
That sounds technical, but the player-facing result is simple: in-game interfaces should behave more cleanly. Menus and overlays can take the keys they need while the rest of the control scheme stays more predictable.
This matters for immersive systems used in Cyberpunk 2077 co-op and RP scenarios, where custom interfaces often handle phones, shops, media surfaces, interaction prompts, or other scripted tools.
New NPC groundwork for richer RP scenes
Another notable addition is support for networked NPC morphs, along with admin-facing NPC catalogue and presentation tools.
For players, this is early groundwork for more varied characters and more believable scenes in multiplayer spaces. For admins and event staff, it points toward better control over how NPCs are selected, displayed, and used during live moments.
In a Cyberpunk 2077 multiplayer world, atmosphere matters. Night City feels better when the people in it do not all look the same. This update pushes that direction forward, especially for RP-heavy servers that want more expressive public scenes, events, or faction spaces.
Safer packaging for custom server resources
There was also a practical fix for resource packaging. The system now rejects missing required files before signing client packages.
That means broken uploads can be caught earlier instead of slipping through and causing confusion later. Server owners and developers should get a more reliable path when preparing content for players.
This is not a flashy feature, but reliability work like this is part of what turns a mod into a platform.
Why this update matters
This was a community-building update more than a spectacle update. The headline features are not explosions or cinematic trailers. They are the systems that help players find good servers, help operators launch them with less hassle, and help in-game experiences feel cleaner once you are connected.
That is important for OPEN//77βs long-term goal: a real Cyberpunk 2077 multiplayer mod with its own accounts, launcher, and dedicated server ecosystem. Better discovery, better hosting, and better in-game usability are exactly the pieces that make that vision believable.
If you are waiting to jump into Night City online, this is the kind of progress that quietly moves the project closer. And if you are planning to run a community, todayβs changes should make the road ahead look a bit friendlier.
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.