Originally posted by Max:

Hey modders!

In the last update, the format of the loadouts file was changed to require an “ordinal” field, which broke several mods. I’m really sorry about that! However, since compatibility got broken anyway, in the next release (roughly targeted at next Thursday) we’re switching loadouts to an explicitly backward-incompatible format which allows finer customization. The changes are:

The loadouts block is an object rather than an array, and each loadout must be specified under a unique ID (any string is fine, but using your mod name as part of it reduces the likelihood of mod conflicts). This allows mods to override parts of a loadout.
Each loadout can specify an ordinal field to determine where in the list it appears. The defaults use ordinals 1-3, and if the ordinal is not specified, it’s assumed to be 0 (i.e. the loadout will appear before the existing ones).
The content field in each loadout is also an object rather than an array, and its entries also support the ordinal field with the same meaning.
Kingdoms can specify a custom loadout file to use by specifying a loadouts field in their population JSON pointing at a custom loadouts JSON path or URI."

"I’m afraid mixing into the loadouts is just broken in the current release. I’ll see if I can get a hotfix out on Monday that would use the new system. If it’s critical for the mod to work in the meantime, removing the loadout temporarily is probably easiest."