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. default is 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 merge comes from default.

The name of a world block is the folder name of the world, the one /ttscore info lists.

One line instead of thirty: the `mechanics` preset

Every world block can start with a preset, and then tune whatever it wants on top:

world-settings:
  default:
    mechanics: legacy      # the whole 1.8 factions behaviour: cannons, anvils, spawners, hits, anti-freecam
  creative:
    mechanics: modern      # plain 1.21 for this world
  survival:
    mechanics: custom      # the raid.* settings written in this block (and inherited from default) rule

legacy sets every raid.* setting to the values of a real 1.8 factions server, the same table the parity bench checks against WineSpigot. What you write under raid.* in that world is ignored while the preset is on: switch to custom to tune single settings.
modern turns the whole raid engine off for that world. A creative or lobby world next to a factions one, on the same server.
custom (the default) is what TTSCore did before presets existed: the file rules.
performance.* settings are never part of a preset.
Presets are per world: a server can mix them, a world cannot.

/ttscore info prints mechanics first, and marks the raid.* lines that come from the preset rather than from the file.

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.