Per-world settings and reload
The shape of the file
config-version: 1
settings:
license-key: "TTS-XXXXX-XXXXX-XXXXX-XXXXX"
verbose: false
world-settings:
default:
raid:
enabled: true
tnt:
fuse-ticks: 80
merge: true
world_nether:
raid:
tnt:
fuse-ticks: 20
settings:applies to the whole server. Your licence key lives here.world-settings:holds one block per world.defaultis inherited by every world.- A world block writes only what it changes. In the example the Nether has a one-second fuse and still merges TNT, because
mergecomes fromdefault.
The name of a world block is the folder name of the world, the one /ttscore info lists.
Seeing what a world really uses
/ttscore info world_nether
prints every setting with the value in force in that world, and marks each one as written in that world or inherited from default. Run it without a world and it uses the one you are standing in.
Set settings.verbose: true and the server prints the same thing to the console each time a world loads or the file is reloaded.
Reloading
/ttscore reload reads the file again and applies it to every world that is loaded. Players stay online.
A value outside its allowed range is not applied. The console names the key and the server keeps the default for it, so a typo cannot leave a cannon world with a fuse of zero.
Updates
Defaults are not written by hand. The server declares them and writes any missing key into default when it starts, with its comment. After an update, new settings appear in your file at their vanilla value and the values you had set are kept.