PassivityIconData

Version Support

Version	Status
v92	Full
v90	-
v86	-

PassivityIconData.xml defines icon mappings: links passivity IDs to icon asset names for UI display.

---

DSL Support

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

---

Quick Recipes

Create

spec:
  version: "1.0"

passivityIconData:
  create:
    - passivityId: 100001
      iconName: "icon_crit_dmg.png"

Create Multiple

spec:
  version: "1.0"

passivityIconData:
  create:
    - passivityId: 100001
      iconName: "icon_crit_dmg.png"
    - passivityId: 100002
      iconName: "icon_defense.png"
    - passivityId: 100003
      iconName: "icon_speed.png"

Update

spec:
  version: "1.0"

passivityIconData:
  update:
    - passivityId: 100001
      changes:
        iconName: "icon_crit_dmg_v2.png"

Upsert

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

spec:
  version: "1.0"

passivityIconData:
  upsert:
    - passivityId: 100004
      iconName: "icon_new_passive.png"

Delete

spec:
  version: "1.0"

passivityIconData:
  delete:
    - 100001

---

Properties Reference

Property	Type	Required	Since	Description
passivityId	int	Yes	v92	Passivity ID this icon belongs to
iconName	string	No	v92	Icon asset filename

---

XML Structure

PassivityIconData.xml
└── PassivityIconData (root)
    └── Icon (0..∞)
        @passivityId (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 passivityId is required, iconName is optional. An entry without iconName creates a placeholder mapping.
• One-to-one mapping: Each passivityId should have at most one icon entry. Creating duplicate entries for the same ID may cause undefined behavior.
• Coordinate with Passivity: Ensure the passivityId references an existing entry in Passivity.