How to Play Dagger Directive Co-op

Dagger Directive supports online co-op for up to four operators. You meet on the ship, pick a mission, pack kits, and deploy together. That sentence is the fantasy. The history is desync: a dead enemy standing for one client, an objective that completes only for the host, a drone corpse that never despawns for the joiner.

Version 1.0 on 13 August 2026 is the first finished-build checkpoint for those bugs. This page does not promise they are gone. It tells you how to test, how to split roles, and when to restart instead of arguing with a ghost.

Host like a grown-up

One player hosts. Everyone else joins before anyone opens the armory for real. Confirm:

• The same mission name on every screen
• The same time of day
• The same Workshop subscription if you queued a community op — see Workshop
• Everyone spawned on the ship, not in a black load screen

If a friend joins late, wait until their kit is real. Late joins were a source of phantom drones and missing saves in Early Access. Patch history records those notes; 1.0 is where you verify they stayed dead.

Split the loadouts on purpose

Four identical SAWs is a parade. Use the loadout planner and Role builds to assign:

• One ghost with a recon drone and a suppressor
• One overwatch with glass and a rangefinder
• One breacher with smoke and an underbarrel
• One floater who carries extra medical calm and a spare explosive drone

Ballistics matters more when someone else is about to walk into your miss. Call the lase. Call the shot. Stealth matters more when one sprinter ruins three crawls. If a teammate will not walk, they are not on a stealth brief — change the brief or change the teammate.

Saves and the sentence you say out loud

Save-anywhere is still the law. In co-op it is also a social skill. The host should say “saving” before a door and after a clean ridge. If clients do not see the same checkpoint, stop. Do not push a compound on a split timeline. Restarting a session is cheaper than a twenty-minute argument about a crate that exists for one person.

The 1.0 desync test

Press notes for 1.0 added missions, AI, and explosive toys. Those are networking stress, not just content. Before a campaign night:

1. Form the party and load one short official mission.
2. Confirm shared spawns and the same objective text.
3. Kill one enemy in view of everyone. Confirm the body.
4. Fly a recon drone. Confirm the mark.
5. Fire the new M32 or a grenade. Confirm the hole.
6. Run a second mission in the same session. Long sessions were where old desync woke up.

If step 3 fails, you do not have a squad night. You have a bug report. Try a different host, verify game files, and check Version 1.0 for the feature list you thought you were testing.

Voice, marks, and who peeks

The game is slow enough that voice is a weapon. One player should own the recon drone. One player should own the first peek. Everyone else watches flanks and the route you already cleared — claymores from Gear belong on that route, not on a teammate’s shin.

If you play without voice, you will friendly-fire a smoke and a doorway. That is not the AI’s fault.

When to stay solo

Solo is the better teacher. Getting Started still recommends one extract alone so pouches and walk are muscle memory. Solo is also how you learn a Walkthrough theater before you donate your friends’ evenings to your geography homework.

Co-op is for the second clear, the loud brief, and the Workshop map someone in the Discord cooked. It is not for the first time you meet the OICW fuze. Learn that on Ballistics with a save you can shamefully reload.

If the squad is stable, the game becomes the thing reviews promised: two voices whispering “did you save?” on a dark ridge. That is the mode. Earn it with a five-minute test, not a three-hour hope.