Optionaldetachment_Deprecated single-rule link, kept for back-compat (and referenced by allied-rule). A detachment may have more than one rule ability — prefer detachment_rule_ids.
Optionaldetachment_ability_ids of every detachment-rule ability this detachment provides (a detachment rule may have multiple named parts). These match the enrichment abilities.json / raw-text-store ids, so the downstream lookup store[ability_id] resolves. Empty/absent until linked by author:reconcile.
Optionaldetachment_11e: the detachment-point cost (1–3) charged against the army's detachment-point budget. null when not yet assigned.
Optionalforce_11e: ids of the Force Disposition entities this detachment grants. Empty until assigned.
Optionaltags11e: detachment-type tags (e.g. 'dynasty', 'kabal'). A roster may include at most one detachment per shared tag — the 'you can only take one of X type of detachment' rule. Empty when the detachment carries no UNIQUE tag.
Optionalenhancement_Optionalstratagem_OptionalrestrictionsOptionalgranted_Construction keywords this detachment grants to matching units while it is selected (e.g. Houndpack Lance grants 'Battleline' to 'War Dog' units). A unit carrying any keyword in a grant's to_keywords gains that grant's keyword for army-construction purposes (datasheet-count caps, battlefield role). Empty/absent when the detachment grants no construction keywords. Distinct from combat keywords, which live in the ability DSL.
Optionalunit_Minimum unit counts the detachment requires while selected (e.g. Houndpack Lance: 'your army must include three or more WAR DOG units'). Each entry requires at least min units carrying keyword. Empty/absent when the detachment imposes no minimum.
Optionalgame_
A detachment option within a faction, providing a detachment rule, enhancements, and stratagems.
This interface was referenced by
0KdcBundledSchemas's JSON-Schema via thedefinition"detachment".