Romestead Co-op Guide (1–8 Players)
Last updated: 2026-08-22
Romestead supports up to 8 players in online co-op and LAN, with scaled difficulty. Co-op makes the boss fights significantly easier but introduces a different problem: coordinating storage, roles, and god choices across a shared settlement. This guide covers the practical decisions you need to make in the first 30 minutes of a co-op run.
On this page
Hosting and joining
Romestead's co-op runs on Steam friend invites. To host:
- Start or load a singleplayer save.
- Open the pause menu and select the co-op option.
- Invite friends via the Steam overlay.
- For LAN, both clients need to be on the same network with the LAN option enabled.
Joiners need their own copy of the game. Cross-platform isn't yet supported as of the current Early Access build.
If co-op has been rough for you, the picture has changed a lot since launch. The 0.25.2 beta patches rebuilt the network code to be more stable and efficient, and added a network quality indicator — including the ability to see other players' connection quality, which makes it far easier to work out whether the problem is the host, a specific player, or the game. Further connection work, plus that indicator, reaches everyone in the Autumn Update on August 31, 2026. Beartwigs is actively asking for multiplayer feedback via the opt-in beta branch.
One thing to settle as a group before patch day: the Autumn Update requires a new world to see its 30+ new dungeons. Existing worlds keep working, but they won't contain the new content. Decide together whether you're rerolling before someone loads the old save on the 31st — and remember each player's character, skills and Favour Points carry across worlds, so only the shared settlement is at stake.
Difficulty scaling
Romestead's official Steam page lists co-op as scaled-difficulty. Practical observations from community reports (not yet fully verified by us):
- Enemies and raids scale with player count. A 4-player party faces tougher fights than a solo run.
- Resource yields generally don't scale. Per-capita resources go down with more players — plan economy accordingly.
We're keeping role recommendations general until we've run co-op enough to verify what actually works in the live game versus the demo. Most "co-op tier list" content online is recycled from city-builder genre conventions.
General role principles (any party size)
Rather than prescribing rigid roles, here are the principles that hold in most co-op city-builders and seem to apply here:
- Diversify classes. A party with one ranged (Scholar), one melee (Legionary), and one economy (Woodcutter or Miner) covers more situations than three of the same.
- Specialize early. Assign who's primary builder, who's primary fighter, who scouts new biomes. Switching constantly wastes everyone's time.
- One player owns the Shrine. Don't let god offerings fall through the cracks because "someone else will do it." The Shrine gates progression for the whole party.
Storage etiquette
In any shared base, storage friction is the #1 source of arguments. A few practical rules:
- One central Food Storage and one central material storage. Everyone dumps there.
- Personal chest per player for unique gear, named weapons, and stuff you don't want consumed.
- Tools in workshop storage, not personal inventory. Saves the next player from digging in their bag for a pickaxe.
Same god, different god
An early decision: should the whole party court the same god, or split? Worth noting that only one blessing can be active per player at a time, so even split worship doesn't let a single player wear multiple blessings simultaneously.
Same-god is typically faster to unlock blessings (Worship Points accumulate against one tree). Split worship broadens the pool of blessings the party can rotate through. We'll add specific recommendations once we've tested both in practice.
Co-op mistakes to avoid
- No assigned roles. If everyone tries to do everything, nothing gets done well.
- Triggering the Satyr war before everyone's geared. The raid hits the whole settlement — you can lose citizens to permadeath if half the party is undergeared.
- Skipping the Shrine. Mandatory for progression. Pick a Shrine-owner in the first session.
- No host-disconnect plan. If the host drops, the session ends. Make sure the host has the stable connection.