Dagger Directive Workshop and Custom Ops

Version 1.0 treats Steam Workshop as part of the finished game, not a poster on a roadmap. You can subscribe to community missions and weapons, bring them into solo or Co-op, and — if you have the patience — build your own with the official Unity map package and the weapon template.

This page is the player-facing flow plus the creator limits. It is not a Unity textbook. Official long-form steps live on the developer’s custom maps guide and custom content / weapons pages; use those when you are actually exporting a scene.

Play a community mission

1. Open the Steam Workshop for Dagger Directive and subscribe.
2. On the in-game mission board, look to the right of the official list. That is the Workshop column.
3. Select the op, confirm you are subscribed, and let it appear on the board.
4. Pack a kit as if you do not trust the author. Community maps can be fair, cruel, or broken.

If the op does not show, restart the game, confirm the subscription, and check that every co-op client subscribed to the same item. A host-only Workshop file is a desync you chose. Co-op will not save you from that.

Play a community weapon

Workshop already has community rifles and magazines — the M1928 Thompson and extra STANAG examples showed up in official posts. Subscribe, then look for them in the armory beside the vanilla rails. Custom weapons must use projectiles the game already has. They will not bring a new muzzle flash or a new attachment family. If a gun feels like a reskin with different numbers, that is the current ceiling, not a bug in your download.

Rank them for yourself. This wiki’s Weapon ranks cover the official 1.0 set (54+ rails, including MK-18, P90, M17, M32, M7, XM8, M2, MK19). Community guns are extra spice. Do not let a 60-round magazine talk you into a sprint on a stealth brief.

Build a map (short version)

Custom maps are built in the Unity Editor with the official Dagger Directive map package. The developer’s outline is:

1. Install the package and create a scene.
2. Build the environment.
3. Author the mission objects and items.
4. Prepare a local test.
5. Test in-game.
6. Upload to Steam Workshop.

You will need the current package — official notes mention updating that package when the game moves. If your local test works and the Workshop upload does not, you are usually on a stale package or a missing mission item. Read the official “mission item information” page before you rewrite the valley.

Build a weapon (short version)

The weapon guide wants an FBX from Blender or Maya, PNG icons, a config file, and a Workshop upload. Supported today: weapon settings, magazine settings, fire sound. Not supported: custom tracers, custom muzzle flashes, attachments other than magazines, and brand-new projectiles. If you need a special bullet, the developers have asked creators to request it rather than invent one.

Test custom content like a player, not a proud parent

• Run the op solo with a Stealth kit and a loud kit.
• Check night. Many custom maps forget lamps and NVG logic.
• Invite one friend. Confirm the objective completes for both — Co-op desync tests apply harder to custom scripts.
• Fly a drone. Radio bubbles and tall custom geometry fight.
• Save and reload once. EA notes called out drones and saves; custom items can revive old ghosts.

If a map is fun, leave a Workshop comment that says where it broke, not just a score. The community is small enough that a useful note matters.

Where this sits beside official campaigns

Workshop does not replace Bering, Pacific, Europe, or Shadow Strike. It extends the nights after you have learned those theaters in the Walkthrough. If you are still on Getting Started, finish an official extract first. Custom maps are a poor first teacher and a great second addiction.

When 1.0 patch notes mention Workshop or the map package, they will land on Patch history. Check that page before you update Unity and brick a scene you loved.