Datapacks

World datapacks

Use a world datapack when Taskbound changes should apply to one world. Editable config/taskbound/data/ files provide the installation's base definitions; enabled world datapacks override definitions with the same ID.

Install an override

Inside the world's datapacks folder, create:

my-taskbound-pack/
  pack.mcmeta
  data/
    taskbound/
      task_templates/
        hunter/
          catalog/
            1_01_pest_control.json

For Minecraft 1.21.1, pack.mcmeta is:

{"pack":{"pack_format":48,"description":"My Taskbound changes"}}

Copy the Pest Control definition from config/taskbound/data/taskbound/task_templates/hunter/catalog/1_01_pest_control.json to that path and edit it. Keep its id unchanged. The copied file replaces the entire definition, not individual fields.

Run /reload as an operator after saving. Use /datapack list if you need to check which packs are enabled. With a ZIP datapack, pack.mcmeta and data/ must be directly at the archive root.

Add content

Use the same five definition folders beneath data/<namespace>/:

• task_givers
• task_categories
• task_templates
• rewards
• level_rewards

The Village Watch example can be a datapack: put its four files beneath data/mytasks/ and include pack.mcmeta. The optional gift file belongs in data/mytasks/level_rewards/.

Keep giver/category/template references consistent and save all related files before one reload. Recipes, loot tables, and tags belong in normal Minecraft datapack directories; they are not loaded from the five Taskbound config folders.

Overrides and removal

A same-ID datapack definition takes priority over config. Removing that override can reveal the original config definition; it does not necessarily delete the content. To hide a giver supplied underneath, use a full, valid giver override with enabled: false.

To remove a single template, also remove its ID from the category that references it. A category cannot have an empty template list. See removing tasks and givers.

If several packs override the same ID, the world's datapack priority determines the winner. Check active packs before editing a config file that appears to have no effect.

What reload changes

Successful reloads clear unaccepted offers so the next batch uses the new definitions. Accepted tasks keep their saved text, objectives, and rewards. Failed validation retains the running server's previous valid catalog; check the reported file and logs/latest.log, fix it, and reload again.