Field manual

Docs

Digital Crew Chief builds persistent DCS World campaigns, tracks the theatre state, and exports missions you can fly without hand-writing scripts.

Campaign workflow

  1. Create a campaign from a scenario, theatre, era, and faction pairing.
  2. Use the campaign map to inspect objectives, airbases, packages, and active flight groups.
  3. Generate a DCS mission, fly it, then submit the resulting campaign state back into Mission Control.
  4. Continue the theatre as a persistent campaign instead of rebuilding missions by hand.

What it generates

The mission pipeline combines shared campaign contracts, DCS theatre data, aircraft definitions, ground groups, structures, warehouses, kneeboards, and Lua scripts into `.miz` output.

Mission Control

After flying a mission, Mission Control can ingest `dcc_state.json` so the next sortie starts from the updated campaign state, including results produced on another machine or server.

Developer setup

  1. Install Bun 1.3+ and Node.js 20+.
  2. Run `bun install` at the repository root.
  3. Run `bun run dev` for the Electron app and renderer dev servers.
  4. Run `bun run lint` and `bun run tsc` before shipping changes.

Project links

Read the source, report issues, and inspect release assets on Codeberg. Join the pilot community on Discord.