Claiming rules
If listing creation fails after item escrow, inspect claims and the operation record before submitting the items again. Claims split items according to their actual stack limits, independently of GUI count badges. Insufficient inventory space leaves items in claims and asks the player to make room before trying again; nothing is dropped or deleted.- Claim-box entrance
- Claimable items
Categories, details and batch claims
Claims are categorized by asset source and paginated. Select a category, then select individual entries or the current page. Details retain real names, enchantments, lore, quantities and claim states. A batch opens an explicit confirmation and processes only the selected entries on the current page, up to 36 entries. It does not automatically continue across the whole claim box. Purchased mixed bundles are claimed from their actual stored contents, never from the display box. Entries without sufficient space are skipped and remain claimable. Confirmed successes are never repeated. An unconfirmed result, disconnection or changed session stops later entries; inspect results before starting another batch.- Source categories
- Select entries
- Final confirmation
Automatic claims
Personal automatic claims are disabled by default and require explicit opt-in on the automation page. Tasks process bounded batches while respecting native stack limits, inventory space, sessions and claim result checks. One pass is not guaranteed to claim every asset. Insufficient space leaves assets claimable. AnUNKNOWN result pauses subsequent tasks without automatic retries. Automatic claims, future-proceeds withdrawals and login withdrawals are independent settings; enabling one does not enable the others.
Uncertain results
If money or item delivery becomesUNKNOWN, stop retrying, record the operation ID, and ask an administrator to reconcile it.
See history and transaction receipts for individual results and operation IDs.