CrestCostData
Version support
Section titled “Version support”| Version | Status |
|---|---|
| v92 | Full |
| v90 | - |
| v86 | - |
CrestCostData.xml defines crest cost tiers: detach money costs and maximum point limits for each crest level.
DSL support
Section titled “DSL support”Entity: crestCosts
Operations: create, update, delete, upsert
File organization: SingleFile — CrestCostData.xml
Quick recipes
Section titled “Quick recipes”Create
Section titled “Create”spec: version: "1.0" schema: v92
crestCosts: create: - level: 10 detachMoney: 500 maxLimitPoint: 50Update
Section titled “Update”spec: version: "1.0" schema: v92
crestCosts: update: - level: 10 changes: detachMoney: 750 maxLimitPoint: 55Delete
Section titled “Delete”spec: version: "1.0" schema: v92
crestCosts: delete: - 10Upsert
Section titled “Upsert”spec: version: "1.0" schema: v92
crestCosts: upsert: - level: 10 detachMoney: 500 maxLimitPoint: 50Properties reference
Section titled “Properties reference”Cost attributes
Section titled “Cost attributes”| Attribute | Type | Since | Required | Description |
|---|---|---|---|---|
level | int | v92 | Yes | Crest level (used as identifier) |
detachMoney | int | v92 | No | Gold cost to remove a crest |
maxLimitPoint | int | v92 | No | Maximum glyph points available at this level |
Root attributes
Section titled “Root attributes”| Attribute | Type | Since | Description |
|---|---|---|---|
setChangeNeedItemTemplateId | int | v92 | Item template required for crest set changes |
XML structure
Section titled “XML structure”CrestCostData.xml└── CrestCostData @setChangeNeedItemTemplateId └── Cost (0..∞) @level (required) @detachMoney (required) @maxLimitPoint (required)Common pitfalls
Section titled “Common pitfalls”- Level as identifier: The
levelfield is used as the entity key — each level value must be unique within the file. - Related schema: CrestCostData works alongside CrestData, which defines the individual crest items and their point costs.