-
Notifications
You must be signed in to change notification settings - Fork 36
Custom Stats
WARNING: EXPERIMENTAL
LCPs can define additional "canonical"/non-custom stats that will appear for all combat entities that contain anything (equipment, features, traits, etc) that reference the stat.
COMP/CON cannot track stat dependencies in LCPs at this time, so all new stats must be scoped to a single LCP. Cross-LCP stat definition, unlike eg. Tags, is not available at this time.
custom_stats.json
[
{
"key": string,
"title": string,
"trackable": boolean,
"default": number | string,
"icon": string,
"sort": number
}
]StatController.RegisterCustomStat() is called when a pack is activated. The stat is applied to all entities via applyRegisteredCustomStats() during setStats().
Internal identifier. This must be globally unique. See Item ID Guidelines for more information.
The display name of the stat
trackable determines if this is a max-only stat like Hull or Grit, or a current/max stat like HP or Heat. trackable = true furnishes a current property and a user-settable current value tracker in Active Mode.
The base value of the stat, before bonuses and modifications. This defaults to zero. It can be an integer or a string in the form of X/Y/Z where X, Y, and Z are integers that represent the default value at NPC tier 1/2/3.
UI icon used to represent the stat. Can be any MDI Icon in the form mdi-ICON_ID
Where this stat appears in stat block style UI. May be negative for guaranteed first position.
Pilot Data
Licensed Data
Other
- Manifest (lcp_manifest.json)
- Base Actions (actions.json)
- Downtime Actions (actions.json)
- Environments (environments.json)
- Manufacturers (manufacturers.json)
- SITREPs (sitreps.json)
- Statuses & Conditions (statuses.json)
- Tables (tables.json)
- Lists (lists.json)
- Tags (tags.json)
- Custom Stat Data (custom_stats.json)