BossGage

Version support

Version	Status
v92	Full
v90	-
v86	-

---

BossGage.xml defines boss HP gage display settings: per-boss visibility rules, UI layering, and shaking effect conditions.

Boss entries are identified by the combination of huntingZoneId and templateId.

---

DSL support

Entity: bossGages Operations: create, update, delete, upsert, config File organization: SingleFile — BossGage.xml

---

Quick recipes

Create

spec:
  version: "1.0"
  schema: v92

bossGages:
  create:
    - huntingZoneId: 620
      templateId: 1000
      range: 40
      layer: 1
      canDouble: false
      eraseWhenDead: true
      hideHPBar: false
      shakingCondition: "HP <= 30"

Update

spec:
  version: "1.0"
  schema: v92

bossGages:
  update:
    - huntingZoneId: 620
      templateId: 1000
      changes:
        range: 60
        layer: 2
        eraseWhenDead: false

Delete

spec:
  version: "1.0"
  schema: v92

bossGages:
  delete:
    - huntingZoneId: 620
      templateId: 1000

Upsert

spec:
  version: "1.0"
  schema: v92

bossGages:
  upsert:
    - huntingZoneId: 620
      templateId: 1000
      range: 40
      layer: 1
      canDouble: false
      eraseWhenDead: true
      hideHPBar: false
      shakingCondition: "HP <= 30"

Config (root settings)

spec:
  version: "1.0"
  schema: v92

bossGages:
  config:
    active: true
    default:
      range: 30
      layer: 0
      shakingCondition: "HP <= 50"
      showCondition: "HP > 0"

---

Properties reference

Boss attributes

Attribute	Type	Since	Required	Description
huntingZoneId	int	v92	Yes	Hunting zone identifier (part of composite key)
templateId	int	v92	Yes	Boss template identifier (part of composite key)
range	int	v92	No	Display range of the boss gage
layer	int	v92	No	UI layer for the boss gage
canDouble	bool	v92	No	Whether the gage can double
eraseWhenDead	bool	v92	No	Whether to erase gage when boss dies
hideHPBar	bool	v92	No	Whether to hide the HP bar
shakingCondition	string	v92	No	Condition expression for shaking effect

Config attributes

Attribute	Type	Since	Required	Description
active	bool	v92	No	Whether boss gage system is enabled
default	Default	v92	No	Default values for new bosses. See Default.

---

Nested elements

Default

Defines default values applied to boss gage entries.

Attribute	Type	Since	Required	Description
range	int	v92	No	Default display range
layer	int	v92	No	Default UI layer
shakingCondition	string	v92	No	Default shaking condition expression
showCondition	string	v92	No	Default show condition expression

---

XML structure

BossGage.xml
└── BossGage
    @active (required)
    ├── Default
    │   @range (required)
    │   @layer (required)
    │   ├── Effect
    │   │   @shakingCondition (required)
    │   └── Info
    │       @showCondition (required)
    └── BossList
        └── Boss (0..∞)
            @huntingZoneId (required)
            @templateId (required)
            @range (required)
            @layer (required)
            @canDouble (optional)
            @eraseWhenDead (optional)
            @hideHPBar (optional)
            └── Effect
                @shakingCondition (required)

---

Common pitfalls

• Composite key: Boss entries require both huntingZoneId and templateId. Delete operations must specify both values, not a single ID.
• Config vs entity operations: Use config: for root-level settings (active, default). Use create/update/delete for individual boss entries in the BossList.
• Default nesting: In YAML, default is a flat object with range, layer, shakingCondition, and showCondition. In XML, shakingCondition is under a nested Effect element and showCondition is under a nested Info element.
• Boolean attributes: canDouble, eraseWhenDead, and hideHPBar are optional in XML. When omitted, the game uses its built-in defaults.