Troubleshooting

1. Check the folder: you should have Documents\Timberborn\Mods\TimberTogether\version-1.1\manifest.json. Extracting a zip often adds an extra folder level.
2. Install and enable Harmony and Mod Settings.
3. Enable Timber Together in the mod manager and restart the game.
4. Check the game version: Timberborn 1.1 (tested on 1.1.2.4).
5. Search %USERPROFILE%\AppData\LocalLow\Mechanistry\Timberborn\Player.log for Timber Together v1.4.0-rc31 is loaded!. If it's there, the mod loaded.

Only one multiplayer mod can run: Timber Together, the Stability Fork and the Workshop BeaverBuddies change the same parts of the game. Unsubscribe from the Workshop version, delete any other multiplayer mod's folder from Documents\Timberborn\Mods (the Stability Fork, or an older copy of this mod), and restart the game. Your saves aren't in that folder.

The update changed something Timber Together corrects for co-op, so co-op stops rather than drift out of step; the message names it. Single player carries on. Update Timber Together when a new build is out, all of you together.

Why

The game version, the mod version or the mod's own files differ from the host's, and the message names which. A copy someone built themselves is refused even with the same version number.

Try this

1. Everyone installs the same zip: the host's, or the newest release's.
2. Replace the TimberTogether folder and fully restart Timberborn on every computer.
3. Compare with your host again.

Why

When someone joins, the games compare their enabled mods and warn if any is on only one computer or at another version. It's a warning, not a refusal: interface-only mods are usually harmless, but a mod that changes the simulation will make the games drift apart. A guest missing a mod the host uses (MixedStorage, for example) leaves the game with a message naming it.

Try this

1. Read the lists: Only on your computer, Only on …'s computer, Different versions.
2. Make them identical on every computer, or turn those mods off everywhere.
3. Restart the changed games, then host again. (The warning is also in Player.log: search for "Mod lists differ".)

1. Invite friends stays greyed until the Steam lobby is ready: give it a moment after you start hosting.
2. Check Enable Steam networking is on in Timber Together's settings (the default).
3. Both of you must be online in Steam, be Steam friends, and own Timberborn on Steam.
4. Your friend can also find your game in Join co-op game.
5. Still stuck? Use direct IP or Hamachi instead.

Nobody can join once the host presses Start game, and a started game may also drop off the Join co-op game list. The host chooses Esc → Save and rehost and sends a new invite, or you join from Join co-op game once the room is open.

They choose Rejoin on the lost-connection message: it waits in their game and joins the host's room as soon as it opens. The host chooses Esc → Save and rehost. Either can go first; when everyone is ready, Start game carries on.

An invite doesn't end the co-op game you're in. Leave it from the game menu (Esc), then accept the invite again, or join from Join co-op game. If you're hosting a room of your own, close it first.

Nobody can join a game that has started. The host uses Save and rehost, and you join that room. If it happens again, send every player's logs.

The message includes Steam's own reason (for example, no working route between you); so does Player.log.

1. Check you're both on the exact same build: joining that never gets past "Receiving the world…" is usually that.
2. Try again. If it repeats, use direct IP or Hamachi.
3. Still failing? Collect every player's logs and ask for help.

1. The host must be hosting, with the room still open.
2. Use the right address: the host's public IP, or the Hamachi (virtual network) address if you use one.
3. Port 25565 must be forwarded to the host's computer, and the firewall must allow Timberborn.
4. Port forwarding is the hard part: Hamachi or a Steam invite avoids it.

A path of yours would touch their road (built or not yet), or a door would open onto it. Keep your roads a cell apart from theirs and from their district center; to link the colonies, put a Trading Post between them. Ctrl+L shows whose roads are whose.

Each half needs a different colony's road at its door: yours at one, theirs at the other. Once it trades, a waiting round says why in the panel: paused or flooded, no workers, no room, or nothing left to bring.

The save is a shared game. To split it, a player other than the host chooses Esc → Found your own colony, or the host rehosts the save and ticks Separate colonies in its room. Either is for good, and the shared colony stays the host's.

The host hasn't given you a colony yet: wait a moment, and send the logs if it lasts. Later, That belongs to another colony means just that: you can change only your own colony.

Ping colors: normal text is 80 ms or less, yellow up to 160 ms, red anything higher or no response. The dot beside the status is green when you're in sync, yellow while catching up or waiting for the host, and red when the connection is unstable, out of sync or disconnected.

Why

The players' games have drifted apart. The log says which check caught it: Random state mismatch, or Colony state differs in a separate-colonies game (that one may be a bug in the check itself, so please send the logs).

Try this

1. The host chooses Save and rehost.
2. Guests choose Reconnect (wait for rehost), in any order: each waits in their game and joins the host's room when it opens.
3. Everyone presses Ready; the host presses Start game.

Common causes

• Different mods or mod versions: take the mod warning seriously.
• Dev mode's tools: only its instant unlock, Finish now and Add 1000 Science are shared.

Keep backups. In a separate-colonies game every computer writes a report when a desync happens: send them all.

An action couldn't be completed on one player's game, so the session stops rather than let the games differ unnoticed. Open the menu (Esc), reload a known-good save, and don't overwrite it with the stopped session. If it repeats with the same action, send the logs and say what you were doing.

A guest who sees An action from the host could not be read is missing a mod the host uses, named in the message. That guest has left the game and the others play on: install the same mods, and the host uses Save and rehost to let them back in.

When a guest loses the host, the game says why and stays paused, with the menu working again. Choose Rejoin to wait in your game and join the host's room when they rehost, or Stay here and save this game alone from the menu.

1. Turn off Always use detailed logging in Timber Together's settings on every computer. It's off by default, and costly.
2. Check the connection panel: a red ping means the connection is the problem.
3. Try a lower game speed. The host can also click Ease off below in the connection panel to slow a little for a slow guest.
4. More colonies mean more to simulate: prefer a smaller map. Ctrl+Shift+J writes a report showing where the time goes.

• It only appears in multiplayer games.
• Check Connection panel in Timber Together's settings (Mods → the settings button beside it): it may be Hidden, or in another corner.
• If you bound Toggle connection panel, you may have hidden it with that key.
• It may be collapsed to one line: click it to expand.

Someone pressed pause. The connection panel's title line says who: Paused by …. Anyone can pick a speed to carry on.

Menus and dialogs don't pause a co-op game, so the game keeps running while one is open.

• Player activity indicators must be on in Timber Together's settings, for them and for you.
• A cursor hides over the game's interface, outside the window, or off the map.
• In Options → Player cursors, check you haven't shrunk or faded that player's cursor. Reset restores the defaults.
• For pings, bind Ping location in the game's key bindings.