Repository navigation
Fix a missing asset
Use this when a mission cannot find a unit, weapon, model, texture or sound. Work in a copy of the mod.
- Open the mod folder.
- Open Project → Validation and click Run validation. Select the relevant finding and read its location.
- Open Project → Dependencies and click Build graph.
- Open Not in project. The Referenced by column shows which project file asks for the asset.
- In All files, use Filter to find that referring file. Select it and inspect NEEDS and USED BY.
| Display | Meaning |
|---|---|
| Red entry in Not in project | The Toolbox classifies the reference as missing. |
| Grey entry | The file is outside the project. It may be stock content; the graph cannot identify every stock model or texture. |
| Unreferenced | No project reference was found. This is not proof that the game never loads the file. |
The stock tank ODF, avtank.odf, contains this entry in [GameObjectClass]:
weaponName1 = "gatstab"If a working copy says "gatstabb", the graph reports gatstabb.odf as missing, referenced by avtank.odf.
- Open the working copy of
avtank.odfin a text editor. - Correct
gatstabbtogatstaband save it. Keep the surrounding ODF unchanged. - Return to Dependencies and click Build graph again.
- Confirm that
gatstabb.odfhas disappeared from the missing list. - Run validation again, then test the mod.
This exact typo-and-correction exercise was checked through the running Dependencies page.
Locate the actual asset. For a stock file, extract it only if you need a local copy to inspect or modify. Stock assets do not all need to be bundled with your mod.
For custom content, copy the intended file into the package and include its dependencies. Do not rename an unrelated file just to make the warning disappear.
For textures, follow the reference through the material file. A correctly converted DDS still needs the filename used by that material.
Checked on 23 October 2026. Starter guides: v0.1.30, validation notes. Mapping guides: v0.1.29, validation notes.