PremiumSlot

Overview

PremiumSlot.xml defines premium slot configurations: groups of slots (SlotSet) each containing positional entries (Slot) that represent item usage, item rewards, or skill activations with cooldown and limit constraints.

Version support

Version	Status
v92	Full
v90	-
v86	-

This schema uses a 2-level nesting structure (PremiumSlot -> SlotSet -> Slot) stored in a single XML file. The root element carries a data attribute (dailyResetHour).

---

DSL support

Entity: premiumSlots Operations: create, update, delete, upsert, root

---

Properties reference

PremiumSlot (Root element)

Attribute	Type	Since	Description
dailyResetHour	int	v92	Hour of day (0-23) when daily slot limits reset

Managed via the root operation block.

SlotSet

Attribute	Type	Since	Required	Description
slotSetId	int	v92	Yes	Unique identifier for the slot set (primary key)
slots	list[Slot]	v92	No	Child slot entries (max 10 per XSD)

Slot

Attribute	Type	Since	Required (create)	Description
pos	int	v92	Yes	Slot position within the set (key within SlotSet)
type	SlotType	v92	Yes	Slot behavior type
templateId	int	v92	Yes	Item or skill template ID
limitType	SlotLimitType	v92	Yes	Limit scope for cooldowns and usage counts
coolTime	int	v92	No	Cooldown duration in seconds
coolTimeAlwaysSpend	bool	v92	No	Whether cooldown is consumed even on failure
amount	int	v92	No	Quantity consumed per use
getTemplateId	int	v92	No	Reward item template ID (for GetItem type)
getAmount	int	v92	No	Reward item quantity (for GetItem type)

---

Enum types

SlotType

Value	Since
UseItem	v92
GetItem	v92
Skill	v92

SlotLimitType

Value	Since
character	v92
account	v92

---

DSL examples

Root attribute update

spec:
  version: "1.0"

premiumSlots:
  root:
    dailyResetHour: 6

Create

spec:
  version: "1.0"

premiumSlots:
  create:
    - slotSetId: 1
      slots:
        - pos: 1
          type: UseItem
          templateId: 200100
          limitType: character
          coolTime: 3600
          coolTimeAlwaysSpend: false
          amount: 1
        - pos: 2
          type: GetItem
          templateId: 200200
          limitType: account
          getTemplateId: 300100
          getAmount: 5

Update

spec:
  version: "1.0"

premiumSlots:
  update:
    - slotSetId: 1
      changes:
        slots:
          - pos: 1
            coolTime: 7200

Delete

spec:
  version: "1.0"

premiumSlots:
  delete:
    - 1

Upsert

spec:
  version: "1.0"

premiumSlots:
  upsert:
    - slotSetId: 2
      slots:
        - pos: 1
          type: Skill
          templateId: 500100
          limitType: character
          coolTime: 1800
          coolTimeAlwaysSpend: true

---

XML structure

PremiumSlot (dailyResetHour)
└── SlotSet (id)
    └── Slot (pos, type, templateId, limitType, coolTime?, coolTimeAlwaysSpend?, amount?, getTemplateId?, getAmount?) [max 10]

---

Notes

• Single file: PremiumSlot uses FileOrganization.SingleFile — all slot sets live in one PremiumSlot.xml file.
• Composite key: Slots are identified by the combination of SlotSetId + pos. The same pos value can appear in different slot sets.
• Root attribute: The dailyResetHour attribute lives on the root <PremiumSlot> element. Use the root operation block to manage it, separate from CRUD operations on slot sets.
• Optional attributes: coolTime, coolTimeAlwaysSpend, amount, getTemplateId, and getAmount are only written to XML when specified in YAML.
• Update granularity: Updates target specific slots by pos within a slot set. Only specified attributes are modified.