Romestead Connection Issues can interrupt multiplayer sessions even when Steam is online. Developer Beartwigs recommends switching to beta branch 0.26.3-beta, moving the host role to whoever has the strongest connection, or bypassing Steam Datagram Relay with a direct-IP connection.
The developer confirms main and beta saves are compatible and that Romestead’s default server port is 8050. Start with the developer’s beta, then test the host and connection method if the problem continues.
Romestead Connection Issues: Install the 0.26.3-beta branch
1. Close the game. Open your Steam Library, right-click Romestead and choose Properties → Betas. Select 0.26.3-beta from the available branches.
2. Allow Steam to update the files, then reopen Romestead. Have your friends use a compatible branch before trying the same world again.
3. Rejoin the same world and see whether the session stays connected. If the beta still disconnects, report the problem to Beartwigs with your game version and connection method.
According to the developer, main-branch and beta saves are compatible. It is still worth making a backup of an important settlement before changing versions, but you do not need to create a new world just to test the beta.
Romestead Connection Issues: Which player should host?
In ordinary co-op, the host’s computer runs the world server. The developer says connections normally use Steam Datagram Relay (SDR), which helps route traffic and protect the host’s public IP address.
If several friends keep dropping, choose the person with the strongest and most stable connection to host. Prefer a wired link where available, and don’t assume the fastest advertised download speed means the most reliable upstream connection.
If Romestead Connection Issues only happen with one host, try a session with someone else running the world. That helps tell a host connection problem from a wider multiplayer issue.
Connect to Romestead using direct IP instead of Steam
Beartwigs says some players solved disconnects by using Host LAN or the separate Romestead Dedicated Server and joining by IP address rather than Steam matchmaking.
Step 1: The host starts a world using Host LAN or the dedicated server tool. Step 2: Friends use the game’s direct-IP connection option and enter the address and port supplied by the host.
Step 3: For players outside the home network, allow and forward UDP port 8050 on the host’s router and firewall, unless the server uses a different configured port. Local players on the same network can use the host’s private LAN address.
If the host’s provider uses carrier-grade NAT, router port forwarding alone may not make the server accessible from outside. A dedicated server hosted elsewhere can avoid that restriction.
A direct-IP connection avoids Steam’s relay route, which is why Beartwigs suggests trying it when Romestead Connection Issues persist. Our dedicated server setup guide covers the server files, password and port configuration.
Romestead Connection Issues: Does a VPN help?
Beartwigs reports that some players had better results when their traffic took a different route through a VPN-style service such as Cloudflare WARP. This can improve a poor route but may increase latency on an already stable connection.
Test a trusted routing service only after the beta and host swap. Compare the session with and without it. A VPN doesn’t replace the correct direct-IP port configuration or guarantee that multiplayer disconnects will stop.
Why are people disconnected from Romestead?
The developer explains that ordinary multiplayer traffic moves through Steam Datagram Relay. When messages between host and player are delayed or lost, Romestead may disconnect that player.
Beartwigs is developing changes to reduce network traffic, avoid disconnects during temporary interruptions, and reconnect players where they were rather than at their respawn points. These are planned improvements, not fixes that every current game version already includes.
If your group keeps disconnecting during the Halloween event, sort out the connection before starting another boss fight. Strange Shards saved before October 31 remain usable afterwards, so you can try again when everyone can stay connected.
Romestead Connection Issues: Quick fix checklist
Try 0.26.3-beta first. Next, switch the host to the strongest connection. Then test Host LAN and direct IP, or a dedicated server on UDP 8050. If those fail, experiment with routing and report the beta results to Beartwigs.
If Romestead Connection Issues continue, include the branch number, player count, Steam or direct-IP connection method, and any host-switch results when reporting the bug.
Official source: Beartwigs, Message From Olympus #3: Connection Issues
