🎮 Game Error Codes What it means & how to fix it

Dragonwilds Won't Connect to Your Server? Here's the Fix

Since the RuneScape: Dragonwilds 1.0 launch (15 Sep 2026) almost every 'can't connect' report is one of three things: your client updated to 1.0 before the dedicated server did (version mismatch — the server then won't even appear in the list), UDP port 7777 isn't reachable, or the Owner ID in DedicatedServer.ini is wrong so your world never lists as Public. The fastest path in 2026: confirm the server log (RSDragonwilds.log) shows the same build as your client's top-left version, wait for 'START SESSION - Success', then search Worlds > Public by the exact 16-character world name — or fall back to a direct IP:7777 join.

Dragonwilds 1.0 dedicated-server connection cheat sheet (verified 24 Sep 2026)

1.0 launch
15 Sep 2026 (largest build change to date)
Game port (UDP only)
7777 (second instance 7778)
Owner ID field
OwnerId= in DedicatedServer.ini (32-char 'My Player ID' from Settings)
Server-ready log line
START SESSION - Success (in RSDragonwilds.log)
World name search
exact DefaultWorldName, case-sensitive, max 16 chars

Last verified: 2026-09-24

Error codes

CONNECTION LOST — Network connection was interrupted You reached a session and then dropped it (not a discovery/listing failure).

Cause: UDP 7777 intermittently blocked, host on a different build after a patch, or an unstable NAT/port-forward.

Fix:
  1. Confirm the dedicated server is on the exact same Dragonwilds 1.0 build as your client — check RSDragonwilds.log version line vs the client version top-left.
  2. Forward UDP (not TCP) port 7777 to the server's local IP and allow it through the firewall; a second server instance uses 7778.
  3. Fall back to a direct IP:port join instead of the Public browser.
  4. Restart the server once after any patch so it pulls the current build.
World missing from the Public list The server is running but your world never registers as Public.

Cause: Wrong or missing Owner ID, or a world-name mismatch (search is case-sensitive, 16-char max).

Fix:
  1. Copy 'My Player ID' from in-game Settings (32 chars) and paste it into OwnerId= in DedicatedServer.ini while the server is stopped, then restart.
  2. Search by the exact DefaultWorldName (case-sensitive, ≤16 chars), NOT the Server Name.
  3. Wait several seconds after opening Worlds > Public before assuming it failed.
Failed to join after the world appears The world lists but the handshake to join never completes.

Cause: UDP port not forwarded/blocked, or a client-vs-server version mismatch.

Fix:
  1. Recheck UDP 7777 forwarding and firewall on the host.
  2. Confirm both sides are on identical 1.0 builds; a server on an older build does not appear at all — restart it to pull the current build.
  3. Do NOT use Steam invites — they don't connect to dedicated servers; use Public list or direct IP.

Fixes that work for most RuneScape: Dragonwilds errors

  1. Match builds first: client version (top-left) must equal the server version printed in RSDragonwilds.log — the #1 cause after the 1.0 patch.
  2. Forward UDP 7777 (only UDP, not TCP) to the server's local IP; second instance uses 7778.
  3. Set OwnerId= in DedicatedServer.ini to your 32-char 'My Player ID' from Settings (server stopped, then restart).
  4. Search Worlds > Public by the exact DefaultWorldName (case-sensitive, ≤16 chars).
  5. Wait for 'START SESSION - Success' in the server log before trying to join.
  6. Use a direct IP:7777 join as a reliable fallback to the Public browser.
  7. Never use Steam invites for dedicated servers; console players can't run client-side mods — test on a clean vanilla server.

FAQ

Why doesn't my Dragonwilds server show up in the Public list?

Usually a wrong/missing Owner ID or a world-name mismatch. Paste your 32-character 'My Player ID' into OwnerId= in DedicatedServer.ini (server stopped) and search by the exact case-sensitive DefaultWorldName (max 16 chars), not the Server Name. If the server is on an older build than your client, it won't list at all — restart it to pull 1.0.

Which port does a Dragonwilds dedicated server need?

UDP 7777 forwarded to the server's local IP (a second instance on the same box uses 7778). Forward UDP only, not TCP, and allow the server through the host firewall.

I updated to 1.0 and now I can't find my server — why?

Your client updated before the dedicated server did. A server on the previous build does not appear in the list. Restart the server so it pulls the current build, confirm the RSDragonwilds.log version matches your client, then search again.

Other games