Authoring Achievements

An achievement is a per-entry pack asset that tracks progress toward one trigger (or several, in multi-criteria mode) and awards points plus optional rewards on unlock. This page covers the Achievement schema; for the shared Requirements/Cost/Reward/ObjectiveSpec sub-schemas it reuses, see Shared Schemas.

Meta vs. normal achievements

Two shapes coexist under the same Achievement type, decoded through AchievementConfig.parseAchievement:

• Meta achievement - metaChildren is present. This bypasses triggerType/criteria parsing entirely and cascades to UNLOCKED once every listed child achievement is unlocked.
• Normal achievement - single-criterion (top-level triggerType/target/requiredAmount) or multi-criterion (a criteria[] array, which makes the top-level trigger fields ignored).

Achievement fields

Criteria array (multi-criterion achievements)

Each entry in criteria[] is its own ObjectiveSpec-shaped criterion: type (or triggerType alias - unlike the achievement top level, criteria accept both), target (wildcard-aware), amount (or requiredAmount alias, default 1), matchMode (default EXACT), qualifier, zone, displayText, textKey.

Points and milestones

Every achievement's points (default 10, whether or not it is hidden) adds to the player's lifetime achievement-point total, EXCEPT a featOfStrength achievement, which is excluded regardless of its authored points value (typically paired with points: 0 by convention, but the exclusion itself does not depend on that value). The plugin ships five built-in, fixed point-threshold milestones that fire automatically as the player's total crosses them - these are a Java-side default list, not a pack-authorable asset type.

Each milestone grants a scaling package of all-skill XP plus a global boost token on crossing (for example the 3,000-point milestone grants 1,500 all-skill XP and a 1.5x, 60-minute global boost; the thresholds and rewards scale up from there). A points gate is also available inside a PrerequisiteGroup via achievementPoints, for content that should only unlock after a player has racked up enough points.

Server-first claims

serverFirst: true enables a first-come-first-served race claim on that achievement: the first player to unlock it gets a permanent, server-wide first-claim record (surfaced in the achievement UI), and every later unlocker gets the normal achievement without the claim. Use this sparingly - it is meant for a handful of genuinely notable server milestones, not routine content.

Zero-point Feats of Strength

Set featOfStrength: true for a bragging-rights achievement that should never contribute to the player's point total or appear in normal browse listings until unlocked - the same listing treatment hidden gets, plus the point-total exclusion hidden alone does not get. Typically paired with points: 0 and a flavorful titleKey/descriptionKey, since the reward here is the title itself, not XP or currency.

Minimal example

{
  "Name": "First_Kill",
  "Payload": {
    "id": "first_kill",
    "triggerType": "KILL_ENTITY",
    "target": "*",
    "requiredAmount": 1,
    "category": "combat",
    "points": 10,
    "autoClaimRewards": [ { "type": "XP", "skill": "SWORDS", "amount": 100 } ]
  }
}

Every-field example (real: a template + an extending entry)

{
  "Name": "Bounty_Board_Counter",
  "Payload": {
    "triggerType": "COMPLETE_BOUNTY",
    "target": "{{board}}",
    "matchMode": "EXACT",
    "category": "quests",
    "subcategory": "bounties",
    "descriptionKey": "achievement.bounty_streak.{{board}}.desc",
    "descriptionArgs": ["@amount"]
  }
}

{
  "Name": "Bounty_Daily_T1",
  "Payload": {
    "extends": "bounty_board_counter",
    "id": "bounty_board_daily_t1",
    "params": { "board": "daily" },
    "requiredAmount": 5,
    "sortOrder": 50,
    "points": 15,
    "chainId": "bounty_board_daily",
    "tier": 1,
    "manualClaimRewards": [ { "type": "CURRENCY", "currencyId": "bounty_token", "amount": 100 } ]
  }
}

See also

• Shared Schemas - ObjectiveSpec, Reward, PrerequisiteGroup, Requirements.
• Authoring Quests & Bounties - the matching quest-side objective schema, with the opposite matchMode default.
• Template Extension - the extends/params DSL (override field criterionOverrides, extras field extraCriteria).
• Achievements - the player-facing achievement UI and progress guide.