DungeonRetry

Overview

DungeonRetry.xml defines dungeon wipe retry/resurrection tier configurations: per-tier costs, class-specific buff routing, and show items.

Version support

Version	Status
v92	Full
v90	-
v86	-

---

DSL support

Section: dungeonRetries Sub-entities: retry entries (CRUD), config Operations: create, update, delete, upsert, config File organization: SingleFile — DungeonRetry.xml

---

Quick recipes

Create

spec:
  version: "1.0"
  schema: v92

dungeonRetries:
  create:
    - retryId: 9001
      clearCount: 3
      cost: 500
      increaseCost: 1.5
      reviveLimit: 5
      classes:
        - type: "warrior"
          applyAbnormalities:
            - id: 55010001
              desc: "Warrior buff"
          showItem:
            templateId: 80001
            desc: "Revival scroll"

Update

dungeonRetries:
  update:
    - retryId: 9001
      changes:
        cost: 750
        reviveLimit: 3

Delete

dungeonRetries:
  delete:
    - 9001

Upsert

dungeonRetries:
  upsert:
    - retryId: 9001
      clearCount: 3
      cost: 500
      increaseCost: 1.5
      reviveLimit: 5

Config

dungeonRetries:
  config:
    retryLimitCost: 1000
    reshowRetryUITime: 30

---

Properties reference

Retry entry attributes

Attribute	Type	Since	Required	Description
retryId	int	v92	Yes	Retry tier identifier (entity key)
clearCount	int	v92	No	Clear count for this tier
cost	int	v92	No	Base retry cost
increaseCost	decimal	v92	No	Cost increase multiplier per retry
reviveLimit	int	v92	No	Maximum revive count
classes	list[RetryClass]	v92	No	Per-class retry configurations

Config attributes

Attribute	Type	Since	Description
retryLimitCost	int	v92	Maximum retry cost cap
reshowRetryUITime	int	v92	Seconds before retry UI reappears

---

Nested elements

RetryClass

Attribute	Type	Since	Required	Description
type	string	v92	Yes	Class type identifier (e.g., warrior, priest)
applyAbnormalities	list[Abnormality]	v92	No	Abnormalities applied on retry
showItem	ShowItem	v92	No	Item shown in retry UI

Abnormality

Attribute	Type	Since	Required	Description
id	int	v92	Yes	Abnormality ID
desc	string	v92	Yes	Abnormality description

ShowItem

Attribute	Type	Since	Required	Description
templateId	int	v92	Yes	Item template ID
desc	string	v92	Yes	Item description

---

XML structure

DungeonRetry.xml
└── DungeonRetry
    @retryLimitCost @reshowRetryUITime
    └── Retry (0..∞)
        @id @clearCount? @cost? @increaseCost? @reviveLimit?
        └── Class (0..∞)
            @type
            ├── ApplyAbnormality (0..∞)
            │   @id @desc
            └── ShowItem (0..1)
                @templateId @desc

---

Common pitfalls

• Config vs entity operations: Use config: for root-level settings (retryLimitCost, reshowRetryUITime). Use create/update/delete for individual Retry entries.
• Clear-and-replace: Classes use clear-and-replace semantics. Providing a classes list on update replaces all existing class children including their nested abnormalities and show items.
• Nested depth: RetryClass contains both a list (applyAbnormalities) and an optional nested object (showItem). Both are replaced when the parent classes list is provided.