Hawthorn Multiplayer & Co-op Guide

1. Confirm everyone can actually run it. Minimum specs are an i5-6400 or Ryzen 5 1400, 8 GB RAM, a GTX 1060 6GB or equivalent, and 50 GB of storage. See Steam page facts.
2. Be Steam friends with everyone first. Since sessions are Steam-invite based, friend connections are the access path — sort this out before the session, not during it.
3. Agree on a host. With shared-world behaviour unconfirmed, pick the person with the most stable connection and the most playtime available.
4. Decide roles before you load in. Hawthorn’s villager job system makes role overlap genuinely wasteful. Use the Co-op Role Planner or read Co-op Roles.
5. Back up saves if you are in a playtest. A rare save-file corruption issue was reported during the August 2026 playtest; the team asked affected players to keep their last known-good save.

NEARstudios has published exactly one sentence about the mechanics of joining: co-op is “set up as private sessions where you can invite your friends on Steam to join you.” Everything below is standard Steam-session practice rather than a confirmed Hawthorn menu path, and it is labelled as such.

1. Launch the build and enter or create your world.
2. Open the session or multiplayer option in the pause or main menu.
3. Set the session to private and send Steam invites to your group.
4. Confirm everyone loads into the same world before anyone starts building.

Two practical cautions worth applying regardless of the exact menu wording:confirm shared-world behaviour on your first session before investing hours, and agree on who owns the save.

Four open questions sit at the centre of co-op planning. Each changes how you would set up a group, so it is worth knowing that they are open:

• Player cap. “Small-scale” is all we have.
• Shared world vs host world. Whether all players progress one village is unstated.
• Per-player progression. Affinity is per player, which implies player-specific progress — but the interaction with co-op is undocumented.
• Drop-in / drop-out. Whether someone can join mid-session.

Affinity being per player is the most interesting clue. It means two players in the same village can have entirely different relationships with the same NPC, which is a strong argument for splitting social duties deliberately rather than everyone talking to everyone.

Hawthorn quietly punishes the default co-op behaviour of everyone doing everything. Three habits fix most of it:

• One owner per production chain. Farming, building, exploration and social each get an owner. Villagers then extend that owner rather than duplicating them.
• Do not double-assign villager jobs. Because NPCs have job preferences, two players assigning the same villager to different jobs wastes the preference system.
• Centralise storage early. Hauling with the rope is much worse when every player has their own pile.

Co-op Roles turns this into an actual job split by group size, and the Co-op Role Planner generates one you can tick off in game.