Ravenswatch Co-op Fix: Stuck Offline or No Party Code

You open Ravenswatch, go to play with friends, and the party code is blank, or the game insists you are offline while Steam and everything else work fine. This is one of the most common co-op problems, and it almost always has the same root cause: the game cannot reach one specific server. This guide explains how online play is put together, how to confirm the problem in the game's own logs, and what to do about it.

How Ravenswatch goes online

Online play has three separate layers, and they fail independently:

1. Epic Online Services (EOS) login. Even on Steam, the game signs in to Epic's services in the background. This uses ordinary HTTPS and rarely fails.
2. Passtech's game backend. Party codes, matchmaking and friends all come from the developer's own backend servers (dt-live.passtechgames.com and dt-live-3.passtechgames.com). The game first asks them over HTTPS which servers to use, then keeps a connection open over UDP port 30100.
3. The game session itself. Once a party is formed, the actual gameplay runs player to player (peer to peer), with a relay when a direct connection is not possible.

A blank party code means layer 2 failed. The party code is handed out by the backend, so if the game cannot reach it, there is nothing to show. Your internet connection can be perfectly fine while this one link is blocked.

Step 1: confirm it in the log

Ravenswatch writes detailed logs. Open the game's install folder (in Steam: right-click Ravenswatch → Manage → Browse local files) and look in the _Logs folder. Open the newest file in a text editor. If the file names look out of order, go by the timestamps inside.

Search for Game connection state changed:

• [2] means the backend accepted you. If you see this, your problem is not the connection to Passtech; skip to "Joining a friend mid-run" below.
• If it stops at [1], or you find Failed to connect to the configured server endpoints, the game could not complete the connection to the backend.
• If you see Open failed repeated many times, instantly and without any delay, see the section on mods below.

One line that looks scary but is harmless: StateStartOffline | Offline. That is simply the name of the lobby state when you start solo. It is logged even when everything is connected, so do not treat it as the error.

Step 2: the usual fixes

Work through these in order and restart the game after each one.

Allow the game through your firewall. Make sure Ravenswatch is allowed on both private and public networks in your firewall, and that outgoing UDP on port 30100 is not blocked. Third-party antivirus suites with their own firewall are a frequent cause.

Try another network. A phone hotspot is the quickest test. If the party code appears on the hotspot, the block is on your home network, router or provider, not your PC. Some routers and many workplace, school and dormitory networks block uncommon UDP ports.

Restart the router and update its firmware. Older routers sometimes mishandle long-lived UDP connections.

Disable VPNs and proxies, or use them on purpose. A VPN that is only half working can break the UDP link. Turn it off and test, or see the next step.

Step 3: if your region or provider blocks the backend

Players in some countries (reports have come from Russia and Egypt, among others) cannot reach Passtech's backend at all from their normal connection, while everything works through a VPN. The fix the developer has pointed players to on the Steam community forums is a split-tunnel VPN: route only the backend servers through the VPN and leave everything else direct.

This works well because only layer 2 needs the VPN. Once you are in a party, the gameplay itself (layer 3) runs fine on your normal connection, so you do not pay the VPN's extra latency during fights. Most VPN apps call this feature "split tunnelling" or "app exclusions"; route the two passtechgames.com servers above through the tunnel. If your VPN can only split by app, routing the whole game through it also works, at the cost of some latency.

Using mods? Rule out the loader

Mods that only change textures, models or game data never touch the network. Lua-scripted mods use a small loader DLL that sits next to the game. Loader builds from before 9 October 2026 had a bug on Windows that broke every connection to the backend: the log shows Open failed hundreds of times, instantly, while the Epic login still succeeds. It has been fixed since, so if that matches your log:

1. Update the loader (the desktop app does this for you, or run rsmm update-loader).
2. To test with no mods at all, restore the game (the restore option in the app, or rsmm restore --all), which puts every original game file back and removes the loader, then launch through Steam.

If the party code works after a restore and breaks again with mods applied, report it with your _Logs file attached; that is exactly the evidence needed to fix it.

Joining a friend mid-run

If you can see a party code but joining a friend puts you in their voice chat while you stay stuck in the lobby, check whether they are already in a run. From what the logs show, the party code stays joinable for the whole run, but the game session itself has already formed, so a late joiner ends up in the party and voice room without entering the game. Join from the lobby before the run starts, or have the host start a fresh run.

When to contact Passtech

If you see [2] in the log on another network but never on yours, and none of the above helps, the block is upstream. Contact Passtech support with:

• your country and internet provider
• the newest file from _Logs
• whether a hotspot or VPN makes it work

That information lets them tell a regional block from a server problem quickly, and it helps every other player stuck on the same provider.