Shared Schemas

Quests, achievements, mastery nodes, currencies, shop entries, and bounty boards all reuse four small sub-schemas instead of each rolling their own gate/cost/reward/objective shape. This page documents each one field-by-field, once. The per-type authoring pages (Quests & Bounties, Achievements, Masteries, Shop) link back here instead of repeating the tables.

Envelope vs. body casing

Every type covered by these schemas is a raw-Payload asset (the pre-1.4.0 authoring pattern, kept deliberately for these eleven content-pack types - never copy it for a brand new type). Two different casing rules apply at two different levels of the same file:

• The asset envelope (Name, Payload) is PascalCase - the codec throws at server start if a key does not start upper-case.
• The Payload body (id, displayName, objectives,cost, ...) is authored in lowerCamelCase by convention - every shipped example in content-packs/ uses lowerCamelCase throughout. Field keys are read case-insensitively, so PascalCase body keys also parse, but do not mix conventions within one file.

{
  "Name": "Bounty_Cache_Copper",          // <- PascalCase envelope key
  "Payload": {                             // <- PascalCase envelope key
    "id": "bounty_cache_copper",           // <- lowerCamelCase body key
    "displayName": "Cache: Copper Ore",    // <- lowerCamelCase body key
    "objectives": [ { "id": "main", "type": "KILL_ENTITY", "target": "*", "amount": 1 } ]
  }
}

The filename is PascalCase and becomes the asset key. For a per-entry type (Quest, Achievement, Mastery, Currency, BountyBoard, ShopEntry, ...) the runtime id comes from either the inner Payload.id field (ShopEntry falls back to the filename, lowercased, when id is absent; Quest and Achievement have no such fallback - a missing Payload.id logs a warning and the entry is dropped) or the filename itself, lowercased (Mastery, Currency, BountyBoard, ShopPool, Shop, templates). Each type's own authoring page states which.

Requirements (gate block)

Used by Quest requirements, ShopEntry/ShopPool/Shop requirements, BountyBoard requirements, and achievement requiresFeatures. This is the shallow form; it is ergonomic sugar that desugars 100% into a PrerequisiteGroup (below) via toGroup().

Empty on every field is ungated (Requirements.NONE).

PrerequisiteGroup (recursive form)

What requirements.prerequisites above actually decodes, and what a mastery track/node's own requirements key, or a currency's visibility key, decodes directly.

An empty group (every field absent) passes vacuously. In AND mode every leaf and sub-group must pass; OR needs one; NOT inverts the AND result.

Cost (price object)

Used by ShopEntry cost and Mastery node cost (extended with statSacrifice on masteries - see Masteries).

"cost": {
  "combine": "all",
  "currencies": { "mastery_point": 2, "life_essence": 500 },
  "items": [ { "id": "Ingredient_Lightning_Essence", "count": 1 } ]
}

Reward (unified one-shot reward list)

An array of reward objects, granted once (on quest completion, achievement unlock, or shop purchase). type selects the shape; it defaults to COMMAND when omitted, for back-compat.

Optional on every reward type: nameKey / descriptionKey (explicit localization keys - XP/BOOST_TOKEN/CURRENCY/parseable-/give rewards need none of these, they auto-render), and icon (inline item-id icon override). A deprecated raw displayName/description literal still parses as a fallback but should never be authored - never bake a balance number into a .lang value, and a raw literal skips localization entirely.

"rewards": [
  { "type": "CURRENCY", "currencyId": "bounty_token", "amount": 160 },
  { "type": "XP", "skill": "MINING", "amount": 1400 },
  { "type": "COMMAND", "command": "/give {player} Ingredient_Bar_Copper --quantity=8" }
]

ObjectiveSpec (quest objective / achievement criterion)

One objective/criterion entry. Quest objectives[] and Achievement criteria[] both wrap the same ObjectiveSpec core, but with type-specific matching defaults - see the callout below.

ObjectiveType roster

Only the "quest-producible" values below can advance a quest objective; achievements accept every one of them through the generic achievement dispatch.

See also

• Authoring Quests & Bounties - Quest and BountyBoard fields, examples.
• Authoring Achievements - Achievement fields, the triggerType trap, points.
• Masteries - the mastery-only statSacrifice cost extension and modifiers[] grammar.
• Shop - ShopEntry/ShopPool/Shop, which consume Cost and Reward directly.
• Template Extension - the extends/params DSL that generates these bodies at scale.