Authoring Quests & Bounties

A quest is a per-entry pack asset with objectives and rewards. A bounty is just a repeatable quest tagged into a rotating board pool - there is no separate "Bounty" asset type. This page covers the Quest schema, then the BountyBoard schedule asset that pulls tagged quests into a rotation.

Folder layout

YourPack.zip
├── manifest.json
└── Server/MMOSkillTree/
    ├── Quests/
    │   └── Bounty_Cache_Copper.json
    ├── QuestTemplates/
    │   └── Bounty_Kill_Standard.json
    └── BountyBoards/
        └── Daily.json

Field names are read for their shared schemas (Requirements, Cost, Reward, ObjectiveSpec) - see Shared Schemas for those tables; this page only lists the fields unique to Quest and BountyBoard.

Quest fields

Localization keys

Prefer titleKey/flavorKey (and, per objective, textKey) over the deprecated raw displayName/description/displayText literals - a raw literal skips localization entirely and cannot be translated by the localization pipeline. Leaving displayText unset on an objective lets the objective text renderer auto-generate a localized, pluralized sentence from type/target/amount, which is usually enough.

Template DSL

Quests support the shared extends/params template DSL (override field objectiveOverrides, extras field extraObjectives, matched by objective id). This is how the shipped bounty pack generates dozens of near-identical bounty entries from a handful of QuestTemplates/*.json skeletons. Full mechanics: Template Extension.

Minimal quest example

{
  "Name": "Simple_Kill",
  "Payload": {
    "id": "simple_kill",
    "category": "misc",
    "objectives": [
      { "id": "main", "type": "KILL_ENTITY", "target": "*", "amount": 5, "matchMode": "CONTAINS" }
    ],
    "rewards": [
      { "type": "XP", "skill": "SWORDS", "amount": 500 }
    ]
  }
}

Every-field example (real bounty template)

{
  "Name": "Bounty_Gather_Standard",
  "Payload": {
    "category": "bounty",
    "repeatable": true,
    "cooldownSeconds": 79200,
    "autoClaimRewards": false,
    "npcViewId": "bounty_board",
    "visibility": { "hidden": true },
    "tags": ["bounty", "board:{{boards}}", "diff:{{difficulty}}", "weight:{{weight}}"],
    "objectives": [
      { "id": "main", "type": "BREAK_BLOCK", "target": "{{target}}", "amount": 1, "matchMode": "CONTAINS" }
    ],
    "rewards": [
      { "type": "CURRENCY", "currencyId": "bounty_token", "amount": 1 }
    ]
  }
}

{
  "Name": "Bounty_Cache_Copper",
  "Payload": {
    "extends": "bounty_gather_standard",
    "id": "bounty_cache_copper",
    "params": { "boards": "daily", "difficulty": "normal", "weight": "2", "target": "Ore_Copper" },
    "objectiveOverrides": { "main": { "amount": 30 } },
    "rewards": [
      { "type": "CURRENCY", "currencyId": "bounty_token", "amount": 160 },
      { "type": "XP", "skill": "MINING", "amount": 1400 },
      { "type": "COMMAND", "command": "/give {player} Ingredient_Bar_Copper --quantity=8" }
    ]
  }
}

Bounty authoring: BountyBoard

The board asset is only the schedule - which tagged quests get drawn into which slots, on what cadence, and who can accept each difficulty. The bounty content itself is authored as ordinary Quest entries tagged ["bounty", "board:<id>", "diff:<x>", "weight:<n>"], npcViewId: "bounty_board", visibility.hidden: true.

Rotation, selection, slots, reroll (shared with ShopPool)

This same shape drives the Token Shop's rotating pools too - see Shop.

TURN_IN / deliver bounties and the claim-at-board lifecycle

A bounty can require the player to physically deliver items at the board rather than just complete an objective in the field:

• Author an explicit TURN_IN objective inside the bounty quest's objectives[], scoped by turnInNpcId. Two shipped shapes: a plain deliver bounty is a single TURN_IN objective against a concrete item id (the Bounty_TurnIn_Standard template, extended by the Bounty_Deliver_* entries - the player brings items gathered elsewhere); a gather-and-deliver bounty is TWO objectives, a BREAK_BLOCK gather step plus a TURN_IN deliver step for a portion of the haul (the Bounty_GatherDeliver_Standard template, extended by entries like Bounty_Mine_Iron).
• Because bounties force autoClaimRewards: false, rewards park as COMPLETED_UNCLAIMED until the player opens the board again and claims them - the claim step happens at the board, not automatically on objective completion.
• Deliver-style bounties reward CURRENCY and XP only by convention, not a hard engine constraint - a claimed board bounty can safely carry a /give item reward (the Claim button is inventory-space-checked, the same as any other bounty), but doing so right after the player just emptied that inventory space to turn in items is awkward, so the shipped pack keeps deliver bounties CURRENCY + XP only.

Minimal board example

{
  "Name": "Simple",
  "Payload": {
    "order": 5,
    "slots": [ { "filter": { "difficulty": "normal" } } ]
  }
}

Every-field example (real: Daily board)

{
  "Name": "Daily",
  "Payload": {
    "titleKey": "ui.bounty.board.daily",
    "descriptionKey": "ui.bounty.board.daily.desc",
    "order": 0,
    "rotation": { "type": "interval", "period": "daily", "anchor": "utc", "offsetMinutes": 0 },
    "selection": { "type": "weighted_random", "seed": "period" },
    "combatLevelRequirements": { "normal": 25, "hard": 60 },
    "slots": [
      { "filter": { "difficulty": "training" } },
      { "filter": { "difficulty": "training" } },
      { "filter": { "difficulty": "easy" } },
      { "filter": { "difficulty": "normal" } },
      { "filter": { "difficulty": "normal" } },
      { "filter": { "difficulty": "hard" }, "optional": true }
    ],
    "rerollCost": { "currency": "bounty_token", "amount": 25, "maxPerPeriod": 3 }
  }
}

The public pack that ships this content is the MMO Skill Bounty Pack and the MMO Skill Quest Pack; see Add-ons for install links. Precedence for both Quest and BountyBoard content resolves as