Edit configuration safely

The two Nusa files

nusa-global.yml and nusa-world.yml live in the server working directory, normally beside the JAR and server.properties. Check your launcher/service working directory if they appear elsewhere.

Current modules read global settings. nusa-world.yml reserves defaults.feature-flags: {} and worlds: {}. Adding a world key does not establish an implemented per-world override. Its YAML structure is still parsed at startup.

Change one thing at a time

1. Record the current value and back up the file.
2. Stop the server before manual editing.
3. Find the key in the index and read its type, bounds, dependencies, and gameplay effects.
4. Use a UTF-8 text editor and spaces for indentation, not tabs.
5. Start again, inspect startup/doctor output, and test the behavior you changed.

All saved Nusa options in this reference require a full restart. Plugin reload does not replace live pools, codecs, listeners, or startup settings.

Common YAML mistakes

feature-flags:
  ai-precompute-queue: true
ai-precompute-queue:
  threads: 0
  exclude-mob-types: [minecraft:villager]

true is a boolean; 'true' is a string and may be rejected. Zero worker threads means automatic sizing, not disable. Merge snippets into existing parents rather than duplicating feature-flags.

Defaults and recovery

Startup creates missing files but does not rewrite existing operator files to add keys. Missing keys use implementation defaults; invalid known values fail startup.

To undo changes, stop, restore the prior configuration, and restart. Restoring config does not convert world data already saved with zstd; read world rollback.