Configuration

Configuration

Server settings control gameplay. Client settings control your local board layout. JSON definition files control the actual tasks, guilds, and rewards.

Settings files

Close the world or stop the server before editing TOML settings. Edit the existing sections rather than adding a second [rewards] or [tasks] section, then start again.

File	Purpose
config/taskbound-client.toml	Local display preference on each client
config/taskbound-server.toml	Server gameplay settings; if your world uses serverconfig/taskbound-server.toml, edit that active world file
config/taskbound/data/	Editable JSON definitions for that installation

In multiplayer, change the server's gameplay files. A client's JSON does not override server tasks. In Prism Launcher, open the instance's Minecraft folder to find config.

Server defaults

[rewards]
use_numismatics_rewards = true
numismatics_spurs_per_emerald = 1
use_custom_currency_rewards = false
custom_currency_item = "minecraft:emerald"

[tasks]
maximum_active_tasks = 3
repeat_cooldown_ticks = 24000
offer_refresh_ticks = 6000

Setting	Meaning
maximum_active_tasks	Active and completed-but-unclaimed task limit; 1-64
repeat_cooldown_ticks	Default cooldown for the same template after a reward claim; 24000 ticks is 20 minutes at normal tick rate; 0 removes the default cooldown
offer_refresh_ticks	Personal board/guild offer rotation; 6000 ticks is five minutes; effective automatic interval is at least 20 ticks
use_numismatics_rewards	Automatically convert newly generated emerald payouts to spurs when available
numismatics_spurs_per_emerald	Automatic Spur conversion rate; 1-1024
use_custom_currency_rewards	Enable an item currency that takes priority over Numismatics
custom_currency_item	Registered item ID for that custom currency; one item per emerald

Templates can override the repeat cooldown. Timers and cooldowns use game ticks: 20 ticks per second or 1200 per minute at normal server speed. Currency and definition changes do not rewrite already generated task snapshots. Currency details.

Client default

[ui]
compact_task_list = false

This is the board's Relaxed/Compact preference. The journal has its own fixed row layout.

Editable definitions

Launch once to create:

config/taskbound/
  .initialized
  data/taskbound/
    task_givers/
    task_categories/
    task_templates/
    rewards/
    level_rewards/

Use another namespace, such as data/mytasks/, for your own content. A file's id must match its namespace and path within its definition folder. For example, data/mytasks/task_templates/watch/zombie_patrol.json declares mytasks:watch/zombie_patrol.

Keep IDs lowercase without spaces. Display names can contain spaces. Renaming an ID also means updating every file that references it.

Apply JSON changes

1. Back up the files outside config/taskbound/. For a live server, also back up the stopped world.
2. Edit normal JSON: double quotes, no comments or trailing commas. Save all related files together.
3. Run /reload or /taskbound reload with operator permission.
4. Check the result and logs/latest.log. Reopen the board and inspect a new offer.

A failed reload leaves the running server's previous valid definitions active. A fresh start has no previous in-memory catalog, so fix invalid files before restarting. A successful reload clears unaccepted offers and their refresh timers; accepted tasks retain their saved text, objectives, and payouts.

Keep .initialized after normal first launch. It prevents later starts from restoring deliberately deleted definitions. Changes to first-launch defaults do not silently replace a customized installation.

Restore clean defaults

The public source package includes default_configs/ as a clean reference for 1.0.0.

1. Stop the game/server and back up Taskbound settings and definitions outside the live config folder.
2. Move the entire old config/taskbound/ folder aside. Copy default_configs/config/taskbound/ into its place. Overlaying files alone leaves extra custom definitions behind.
3. If desired, also replace the server/client TOML settings with their reference files, using the active server-config location for your world.
4. Check for world datapack overrides; disable or update them if you want only the defaults.
5. Start again and check for loading errors. The reference omits .initialized; the first start creates it. Keep it afterward.

Alternatively, moving the entire backed-up config/taskbound/ folder aside allows first launch to generate the default definitions again. Removing only .initialized restores missing files but preserves existing edited files, so it is not a full reset.

Restoring configuration does not reset player reputation, claimed level gifts, completion history, or accepted task snapshots. See datapacks for world-specific overrides.