AbnormalityIconData

Version support

Version	Status
v92	Full
v90	-
v86	-

AbnormalityIconData.xml defines icon mappings: links abnormality IDs to icon asset names for UI display.

AbnormalityIconData is organized across regional variant XML files:

Suffix	File
(base)	`AbnormalityIconData.xml`
`_CN`	`AbnormalityIconData_CN.xml`
`_EP`	`AbnormalityIconData_EP.xml`
`_JP`	`AbnormalityIconData_JP.xml`
`_KR`	`AbnormalityIconData_KR.xml`
`_NAEU`	`AbnormalityIconData_NAEU.xml`
`_RUS`	`AbnormalityIconData_RUS.xml`
`_THA`	`AbnormalityIconData_THA.xml`
`_TW`	`AbnormalityIconData_TW.xml`

DSL support

Entity: abnormalityIconData Operations: create, update, delete, upsert

Quick recipes

Create

spec:
  version: "1.0"
  schema: v92

abnormalityIconData:
  create:
    - abnormalityId: 100001
      iconName: "icon_crit_dmg.dds"

Create multiple

spec:
  version: "1.0"
  schema: v92

abnormalityIconData:
  create:
    - abnormalityId: 100001
      iconName: "icon_crit_dmg.dds"
    - abnormalityId: 100002
      iconName: "icon_defense.dds"
    - abnormalityId: 100003
      iconName: "icon_speed.dds"

Update

spec:
  version: "1.0"
  schema: v92

abnormalityIconData:
  update:
    - abnormalityId: 100001
      changes:
        iconName: "icon_crit_dmg_v2.dds"

Upsert

Creates the entry if it doesn’t exist, or updates it if it does.

spec:
  version: "1.0"
  schema: v92

abnormalityIconData:
  upsert:
    - abnormalityId: 100004
      iconName: "icon_new_buff.dds"

Delete

spec:
  version: "1.0"
  schema: v92

abnormalityIconData:
  delete:
    - 100001

Properties reference

Property	Type	Required	Since	Description
`abnormalityId`	`int`	Yes	v92	Abnormality ID this icon belongs to
`iconName`	`string`	No	v92	Icon asset filename

XML structure

AbnormalityIconData.xml
└── AbnormalityIconData (root)
    └── Icon (0..∞)
        @abnormalityId (required)
        @iconName?

Common pitfalls

Icon asset paths: The iconName is just the filename, not a full path. The game client resolves the actual asset location.
Optional iconName: While abnormalityId is required, iconName is optional. An entry without iconName creates a placeholder mapping.
One-to-one mapping: Each abnormalityId should have at most one icon entry. Creating duplicate entries for the same ID may cause undefined behavior.
Regional variants: Data is spread across regional variant files. The pipeline resolves the correct file automatically.
Companion schema: Ensure the abnormalityId references an existing entry in Abnormality.