Authoring Achievements

Achievements share a schema with quests: the same file layout, the same Text / Listing / Requires / Rewards groups, the same Parent inheritance, the same objective shape. What is different is what an achievement adds - scoring, a keyed map of criteria, and a capstone over a set. For the sub-schemas both share, see Shared Schemas.

The shared achievement file

{
  "Text":    { "TitleKey": "achievement.wilds_hunter_t1.title",
               "FlavorKey": "achievement.wilds_hunter.desc",
               "TextArgs": { "Flavor": ["@amount"] } },
  "Listing": { "Category": "combat", "Subcategory": "melee", "SortOrder": 80,
               "Chains": [ { "Id": "wilds_hunter", "Tier": 1 } ] },
  "Scoring": { "Points": 10 },
  "Criteria": {
    "kill-entity": { "Kind": "KILL_ENTITY", "Target": "", "MatchMode": "CONTAINS",
                     "Zone": "Emerald_Wilds", "Amount": 50 }
  }
}

Scoring

Scoring.Points (default 10) is what this achievement adds to a player's lifetime total. CountsTowardTotal is the one does-not-count switch, and it is honoured exactly as authored: write false for something nobody can earn any more, so a long-standing player's total stays comparable with a newcomer's. Nothing else flips it behind your back. A feat of strength (Meta.mmoskilltree.Feat) is a listing treatment - its own earned-only shelf, unpinnable, out of sight until somebody does it - so an author who wants a feat kept out of the points total writes the two together, which is what every shipped feat does:

"Scoring": { "Points": 0, "CountsTowardTotal": false },
"Meta": { "mmoskilltree": { "Feat": true } }

Meta.mmoskilltree

A key nothing here claims is reported by name at boot and the rest of the block still loads, so a typo costs one knob rather than the whole file.

The two per-skill stencils. A server's skill roster is not known when a file is written, so the two shapes that have to cover "every skill" are written once and stamped out against the live roster. PerSkill.IdPattern gives ONE ACHIEVEMENT per skill ("{skill}_10" yields mining_10, woodcutting_10, ...); PerSkill.Criterion gives ONE CRITERION per skill inside a single achievement, which is the shape of "do it in every skill". In any authored text, {skill} stands for a skill's id and {skillName} for its readable name.

Reuse and generators

A file may name another as "Parent": "<id>" and inherit every field it does not mention; leaves and groups merge per leaf and Criteria merges per criterion key, while Rewards.Auto, Rewards.Claim, Listing.Tags and Listing.Chains are each one leaf that replaces whole. Mark a base "Abstract": true so it never appears as content in its own right. The full rules, and the matching generator file, are on the quests page - they are identical for both stores.

Categories and point milestones as assets

Both are ordinary shared-schema content, so a pack declares its own category or its own points ladder and a server owner still outranks it.

A category

Server/ZiggfreedCommon/AchievementCategories/<Namespace>/<Category>.json is the presentation half of an achievement's Listing.Category leaf. The filename IS the category word content writes, lower-cased, so Combat.json is the category combat.

{ "Order": 40,
  "Icon": "Tool_Fishing_Rod",
  "TitleKey": "achievement.category.sailing",
  "Subcategories": ["harbour", "deep_water"] }

A point milestone

Server/ZiggfreedCommon/AchievementMilestones/<Namespace>/<Name>.json is one rung of the achievement-points ladder. Threshold is the milestone's identity, not the filename, so a file re-authoring 3000 replaces the shipped 3000 rung outright.

{ "Threshold": 3000,
  "TitleKey": "achievement.milestone.3000.title",
  "Rewards": {
    "Auto":  [ { "Kind": "Mmo_Xp", "Params": { "Skill": "ALL", "Amount": "1500" } } ],
    "Claim": [ { "Kind": "Item", "Params": { "Item": "Ingredient_Bar_Iron", "Count": "5" } } ]
  } }

Both layer

Server-first claims

Meta.mmoskilltree.ServerFirst enables a first-come-first-served race claim: the first player to unlock the achievement gets a permanent, server-wide first-claim record, surfaced in the achievement UI, and every later unlocker gets the normal achievement without the claim. When somebody who was racing loses the claim, what they are told is an authored feedback moment, so a server owner can re-word it or broadcast it.

The older shape (still read)

Everything written before 1.6.0 still loads: Server/MMOSkillTree/Achievements/<id>.json, the AchievementTemplates extends / params DSL, and a server owner's own mods/mmoskilltree/achievements/ files all go through a compat reader that registers them into the same engine. Author anything new in the shared shape above.

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

See also

• Shared Schemas - objectives, rewards, and the one Requires block.
• Authoring Quests & Bounties - the matching quest half, Parent inheritance and generators in full.
• Achievements - the player-facing UI, pinning, and progress guide.
• Feedback - the authored moment behind the unlock toast and the server-first notice.