Triarchy Shared Progress in Co-op

Shared progress is Triarchy’s answer to a common co-op frustration: you help a friend clear an island, log off, and return later to find your own save did not advance. Digital Confectioners states that co-op uses shared progress on the host’s voyage, meaning major discoveries, boss defeats, and world state changes persist for the party working on that save. Combined with drop-in and drop-out and no tethering, the system is meant to feel like one continuous expedition across the drowned archipelago.

Triarchy remains unreleased with a 2026 Steam target, so edge cases—personal stash tabs, cosmetic unlocks, assist profiles—may only become clear in later playtests. Treat this page as a framework aligned with official copy, then adjust when patch notes contradict assumptions.

Host save versus guest participation

In most co-op ARPGs with shared worlds, the host owns the save slot that advances. Guests participate in that timeline for the session. Triarchy marketing emphasizes sailing and boss hunting together on one archipelago, which implies:

• World discoveries — islands marked on the Map Table, shortcuts opened, and boss arenas found while co-oping should remain on the host save.
• Boss clears — defeating a multi-phase boss with unique rewards likely counts once for that save, preventing duplicate farming across rotating guests unless Challenge Modes intentionally allow rematches.
• Ship upgrades — hull and sail investments tied to the mobile base probably live on the host world, making the ship a shared strategic asset.

Guests still bring individual build choices and assist settings (assist planner), which official materials describe as per-player without forcing difficulty on others.

What shared progress encourages strategically

Shared progress pushes crews toward role specialization instead of duplicate grinding. If everyone shares one timeline, wasting resources on redundant crafting hurts the whole voyage. Practical habits:

1. Divide crafting lanes — one sailor focuses consumables at the workbench, another hunts upgrade mats for ship upgrades.
2. Agree on boss order — use Boss overview to prioritize gear checks before Challenge Modes.
3. Document Map Table plans — shared progress is wasted if two players sail to conflicting regions without syncing routes.
4. Align builds — complementary talents beat three identical DPS loadouts when arena hazards demand positioning.

Solo players still benefit: you advance the same save alone, then invite friends who catch up to your discoveries rather than resetting tutorials.

Narrative and quest synchronization

Shared progress usually means one story state. If the host triggers a cinematic on an island, guests typically witness or skip together depending on instancing rules. Until release confirms details:

• Finish dialogue sequences as a group when possible.
• Avoid starting conflicting main-path objectives while someone is drop-in loading.
• Re-read quest text on the ship before sailing if a guest missed lore.

Playtests sometimes gate story beats to the host only; note behavior and update this wiki after verification.

Loot, materials, and stashes

Official pages highlight unique boss materials and boss-exclusive gear. Shared progress suggests those rewards feed the shared crafting economy on the ship rather than disappearing when a guest leaves. Stash behavior—personal versus communal tabs—is not fully documented pre-release.

Assume communal risk: deposit rare mats to the ship stash before drop-out unless future patches confirm personal banks. Crafting legendaries at the workbench likely consumes shared stockpiles, so communicate before spending rare drops from prep tips farming routes.

Progress when players drop out

When a guest leaves, the host continues on the same timeline. Victories achieved while the guest was present should remain cleared; the guest’s later rejoin should reflect that state. If a guest joins late, they benefit from earlier clears without redoing entire islands—consistent with drop-in design.

If a guest needs personal practice, solo scaled fights on their own save may still be necessary for skill checks covered in combat basics.

Shared progress and enemy scaling

Scaling adjusts combat math for party size; it does not replace shared unlocks. A three-player crew might fight beefier adds, but the boss reward still lands once on the save. Read enemy scaling alongside this page so you do not confuse difficulty tuning with loot ownership.

Solo-to-co-op migration path

Many players will wishlist Triarchy, play solo in the first playtest, then invite friends. Shared progress makes that viable:

Stage	Recommended focus
Solo early hours	Learn stamina and sailing; mark islands on Map Table
First co-op invite	Host your save; brief guests on discoveries
Full trio	Split roles; plan Challenge attempts with fixed roster
Between sessions	Host maintains ship upgrades; guests review build notes

Conflicts to watch before launch

Watch for these unresolved questions in future tests:

• Whether guests retain any account-wide codex unlocks
• If Challenge Mode rewards are once-per-save or farmable
• How rollback works after host crash mid-boss

Report findings during playtests so the community wiki stays accurate.

Summary

Shared progress makes Triarchy feel like a crew chronicle rather than parallel single-player games. Respect the host save, pool resources intelligently on the ship, and coordinate bosses through Co-op hub guides. When in doubt, regroup at the mobile base, open the Map Table, and align on the next island before anyone sails solo into scaled elite packs.