NightCoop guide
NightCoop not working
Last checked: 2026-11-04 · Official version: v0.2.0-beta (2026-11-02) · Protocol 164 · Free · Windows 10/11 64-bit · Up to 8 players · RED4ext only (no CET) · Phantom Liberty not required
Two connection error strings are documented: the server does not answer and the server failed the key check. A missing invite code is a separate lobby procedure, not a third published error string. Other rows are search phrases with thinner evidence. Filter by the stage in the first column.
| Stage | Symptom | Message EN | Message RU | Known cause | Steps | Affected build | Evidence | Detail |
|---|---|---|---|---|---|---|---|---|
| Diagnostics | A crash, freeze or desync needs a bug report and the player does not know which files to send | Three different log locations: RED4ext, NightCoop and the game's own crash reporter | Zip red4ext\logs and red4ext\plugins\NightCoop\logs; add %localappdata%\REDEngine\ReportQueue\<latest>\stacktrace.txt; post to Discord with the time and host/guest role | 0.2.0-beta | 2 independent publishers | Guide | ||
| Connection | Host or guest stalls at connect; RU searchers describe it as the server not being found or the connection to the server being lost | The server does not answer | «Сервер не отвечает» | UDP 47800 closed or the hub is down; NAT blocks the direct path; on a self-hosted hub the 47810+ thread ports are closed | Open UDP 47800 (47810-47873 on your own hub); check the hub is up; use Auto: nearest or add your server with its fingerprint; retry | 0.2.0-beta (strings documented in current guides) | 2 independent publishers | Guide |
| In-game | A quest step does not advance, or a guest is stuck behind the host | The story is host-led; some quest steps are decided by the host; Act 1 is the most tested part of the game | Walk to the host; let the host trigger the step; report the quest name and time on Discord | 0.2.0-beta | 1 source (NightCoop project) | |||
| Connection | The host lobby never shows a session code, or the guest cannot get into the session | The host is not in a lobby (a missing Co-op item means the plugin did not load); game or NightCoop build mismatch; the session was not created | Open Co-op > Host a session, select the world save or New game in the lobby, have every player Ready, then Copy the invite from the right. Guests use Join by code. If Co-op is missing, check the plugin and RED4ext log; match builds across the party. | 0.2.0-beta | 1 source (NightCoop project; documented procedure) | Guide | ||
| Startup | The session or the game does not start | cannot start yet (query wording, not a confirmed UI string) | Unresolved: no official or community source documents this exact message | Check the same build, game 2.5/2.31 and that the plugin loaded; then report it on Discord | 0 sources for the exact string | |||
| Any | The mod seems not to load or does nothing | Plugin in the wrong folder, an unlisted game version, or mismatched builds | Verify NightCoop.dll sits in red4ext\plugins\NightCoop, read the RED4ext log, match every player's build | 0.2.0-beta | 1 source (NightCoop project) | |||
| In-game | The screen flickers in and out during a session | Unresolved; display mode and overlays are documented for hitches, not for flicker | Try Borderless window, disable the Discord overlay and NVIDIA frame generation; if it persists, report it | 0.2.0-beta | 1 source for related hitches | |||
| Connection | The server window says the key does not match the fingerprint, or the link shows as encrypted but not verified | The server failed the key check | «Сервер не прошёл проверку ключей» | Fingerprint typo, the hub key was re-created, or the address points at a different server; a bare address cannot authenticate the hub | Re-enter address#fingerprint; ask the hub owner for the new fingerprint after a key reset; confirm the window reads verified | 0.2.0-beta | 2 independent publishers | Guide |
| Any | Players ask whether sessions are stable | Beta software; a published known-issues list; 0.2.0 fixed several crashes and a freeze | Use the latest build and read the known issues before reporting | 0.2.0-beta | 1 source (NightCoop project) |
Known issues on the beta page
- NPCs can twitch or hold a T-pose.
- Story steps wait on the host.
- Exclusive fullscreen can hitch for a second or two on Alt+Tab.
- A one-second hitch is listed next to the Discord overlay and NVIDIA frame generation.
- Sessions above four players have the least testing, according to that page.
Questions
What should I check first?
Same NightCoop build for every player, a Co-op item on the main menu, and UDP 47800 open if the server does not answer.
Where are the logs?
RED4ext logs, the NightCoop plugin logs, and the game crash report live in three different folders. The logs page lists the paths.
Sources
- NightCoop guides — checked 2026-11-04
- NightCoop open beta — checked 2026-11-04
- Independent network notes — checked 2026-11-04
- Self-hosted hub guide — checked 2026-11-04
- CD PROJEKT RED crash-log help — checked 2026-11-04
- Independent save notes — checked 2026-11-04