54,000 reusable mission pieces.
Fragments are the raw material the engine uses to assemble your mission. Browse them at /fragments.

What is a fragment?
A fragment is a small piece of a real DCS mission — a SAM site, a CAP flight of two, an armor column of four T-80s with infantry escorts. Each fragment has metadata: era, coalition, role, theatre, unit count.
Fragments are reusable — the same Tor-M1 SAM fragment can land in a Caucasus mission today and a Syria mission tomorrow.
Where they come from
We swept the live Fox3 customer fleet — 1,193 real production missions across 200+ DCS servers — and extracted every coherent unit grouping. The result is a 54,000-piece library of patterns experienced mission designers actually used in live games.
What this means:when the engine puts a SAM site in your mission, it's not a synthetic template — it's a SAM site exactly as a real mission designer set it up.
Browsing /fragments
The /fragments page lets you filter by era, coalition, role, theatre, category, and size. Useful for:
- Scoping out what kinds of threats are available before building.
- Seeing the shape of the library (e.g. how many WWII Persian Gulf fragments — answer: zero, that combination doesn't exist).
- Understanding why a recipe placed what it did.
Fragment vs cell vs seed
Easy way to remember the three terms:
- Cell = a slot in the catalog (Map / Era / Scenario).
- Seed = the starting
.mizfile for a cell. - Fragment = a small piece the engine drops into the seed.