KNOWN ISSUES · FIELD GUIDE
Could not connect? Compare the Windows Mullvad case.
Checked October 16, 2026 · Full game · Source-based guide
If your case matches a Windows 11 player using Mullvad, compare the VPN/network path before repeating reinstalls. Iblis reports over 90 minutes of working co-op after changing VPN service and proxy. That is one player’s outcome; their UDP/NAT explanation remains a hypothesis.[1]
What changed in the reported case
Both players used Windows 11, but only Iblis used Mullvad. Swapping hosts, public/private rooms, passwords and reinstalling had failed. Changing the VPN service and proxy then worked for that pair. Because two network settings changed, the thread does not isolate which change mattered.[1]
Make a comparison you can undo
- Write down the exact error, both players’ platforms/builds, who hosts, and which VPN or proxy is active.
- If you choose to compare a different network path, change one setting at a time and restore it afterward. Disabling a VPN exposes your usual network address; skip that comparison if the VPN is required. The source suggests it, but reports success after a different VPN/proxy combination.
- Retry the same room with the same players and record whether joining and movement now work. If the game is already permitted through the firewall, do not keep broadening access without a matching blocked-traffic observation.
This is a diagnostic comparison based on the case. It is not a recommendation to buy a VPN, turn off your firewall, open guessed ports or treat every co-op error as a Mullvad problem.
Separate connection, authorization and in-world problems
| What you see | What the evidence supports |
|---|---|
| Could not connect to game; Windows 11 and Mullvad involved | Compare the case above; only one reported pair and one successful changed setup.[1] |
| Joined but frozen at the initial spawn | Pippy reports this in a separate thread without a solution. Matching appearance does not establish the same cause.[2] |
| Failed to deserialize server response / local mode | A separate authorization report has no solution reply; the Mullvad case is not a verified remedy.[3] |
| Joined successfully, but the guest’s ranged weapon fails | Use the Bow/Harpoon host-versus-guest check. This is a later gameplay symptom. |
What Patch 1.0.47.0 actually says
The October 15 official notes fix removal of a lobby password. They do not say that all connection failures, join freezes or authorization errors are resolved, nor establish identical release timing on every platform.[4]
Send the observations that distinguish your case
Use Raw Fury Support Desk (external, opens in a new tab) with the full error, both builds, host/guest roles, room visibility, network-path comparison and a short video if movement differs between screens. Raw Fury asks for reproduction steps and screenshots/video in its ranged-weapon reply.[5]
Source-based launch-week checks, not our networking test. Current incidence, server-wide outage status and a complete cross-store invitation flow are not established.
Sources & verification
- Iblis, October 14: Windows 11 connection attempts and changed VPN/proxy outcome; single case. Checked October 16, 2026; not tested by this site. Steam Community (external, opens in a new tab)
- Pippy, October 15–16 display range: public-room join freeze, no solution reply. Checked October 16, 2026; not tested by this site. Steam Community (external, opens in a new tab)
- KUBrik, October 15–16 display range: authorization / deserialize error, no solution reply. Checked October 16, 2026; not tested by this site. Steam Community (external, opens in a new tab)
- Official October 15 Patch 1.0.47.0 notes: lobby-password removal fix. Checked October 16, 2026; not tested by this site. Steam Community (external, opens in a new tab)
- Karen RawFury, developer reply: support desk, reproduction steps and screenshots/video. Checked October 16, 2026; not tested by this site. Steam Community (external, opens in a new tab)