When an item never spawns, the cause is often a mismatch between types.xml (what should spawn), mapgroupproto.xml (where buildings can hold it) and cfglimitsdefinition.xml (the allowed usages, tiers, categories and tags). This validator compares the three files.
How to use the tool
Load types.xml (the mission's db/ folder) with the “Choose” button.
Load mapgroupproto.xml and cfglimitsdefinition.xml (mission root), then cfglimitsdefinitionuser.xml if it exists.
Read the errors (red): undeclared values or invalid XML — those entries will not load properly.
Read the warnings (orange): these are items that may never spawn on this map.
Fix your files (e.g. with the types.xml editor), reload them and repeat until there are no errors.
What is checked
- Every usage, value (tier), category and tag in types.xml and mapgroupproto.xml exists in cfglimitsdefinition.xml (or the user file).
- Items with nominal > 0 use usages/tiers that at least one mapgroupproto.xml group offers; otherwise they cannot spawn in buildings.
- Duplicate types, min greater than nominal, lifetime 0, groups without a container.
Frequently asked questions
- Does a warning always mean a bug?
- No. An item spawned only by an event or by cfgspawnabletypes.xml does not need a building usage. Warnings flag a risk, not a certainty.
- Are my files uploaded or stored?
- No: they are read and analysed in your browser's memory and disappear when you close the page.
