Last Pirates: Die Together Co-op Guide

October update: what to check now

Use Start game → Find Crew to browse open sessions by state, stage and player count, including runs in progress. This October 1 flow supersedes older Quick Join interface descriptions. Friends must use the same Steam branch; the October 6 beta and public branch are not interchangeable.

September 25: earlier corrections

Missing shops after transitions and inconsistent death/revive states between players were fixed.

September changes that affect this guide

2026-09-25: Solo quota, shop balances and co-op synchronization changed, alongside Mimic, Ear, Anchor and Castle elevator fixes.

2026-09-18: Lobby previews and clearer host/code feedback arrived with 70 additional loot spawn points across 15 levels, lift corrections and recovery fixes.

Current crew session board

Public-default lobbies do not remove private invite/code flows. Find Crew is the feature route; No Game Found is the error route; reconnect belongs to a run already in progress.

Keep those intents separate so one symptom does not trigger irrelevant fixes.

How many players can join?

Official Steam descriptions consistently say up to four players, and the feature list includes both single-player and online co-op. The supported party range is therefore one to four.

That number does not tell us whether enemy pressure, loot, or objectives scale in a particular way. Party-size balance belongs to live-build research.

Can you play solo?

Yes, Steam lists single-player. A solo pirate still has to handle observation, object movement, threat response, and the return trip without teammates dividing those jobs.

The official marketing focuses on shared chaos and cooperation, but this guide does not claim that solo is unsupported or name an optimal crew size before observing current scaling.

Crew setup and region considerations

Choose a sensible region, confirm who is hosting, and make sure every player has finished updating before diagnosing a lobby problem. A version mismatch or distant region can look like a broken co-op system.

For a planned group, agree on one person who will recreate the lobby if the host disappears. This is a reversible coordination step, not a promise about how host migration resolves every case.

Reconnect and host-migration context

Official June and July patches added or repaired a reconnect screen, session synchronization, and host migration behavior. The patch history shows the systems were active development areas before launch.

Use the dedicated save-and-reconnect guide for symptoms after a dropped run. It separates in-game flow, standard Steam steps, and any future community workarounds.

Voice chat status

The official developer FAQ says the game uses in-game voice chat and tells players to keep a microphone enabled. It does not document range behavior, push-to-talk controls, volume settings, or current defaults.

Check the current in-game audio and input settings before treating a microphone symptom as a network failure. External crew communication remains a practical fallback.

Steam Deck and control considerations

A July patch mentioned Steam Deck support fixes, FOV, invert-Y, and control-related work. That is not equivalent to Valve Verified status or a guarantee of flawless handheld play.

The requirements page keeps official store minimums and Deck qualification together. Recheck input prompts and settings after each significant build.

Common co-op problems

If no public lobby appears, confirm client version, region, and Steam connectivity before changing system settings. If a run disconnects, use the in-game reconnect flow before restarting the entire crew.

Do not download networking fixes, disable security globally, or delete saves as a first step. The troubleshooter prioritizes documented and reversible actions.

Direct answers

Frequently asked questions