Console setup wizard | NusaSpigot Docs

Follow four steps

Run nusa setup in the console; add / in game. Console/operators are allowed, or grant nusaspigot.command.setup. The feature-flags.tuning-wizard flag must be enabled.

nusa setup
nusa setup survival
nusa setup 100
nusa setup auto

The sequence is Server → Players → Hardware → Review. Answers are commands, not ordinary chat. 100 is an example concurrent-player estimate, not a capacity guarantee or a change to max-players.

For a direct preview:

nusa setup survival 100 auto

Explicit hardware uses logical cores and RAM in GiB, for example nusa setup survival 100 4 8. Input bounds are players 1..100000, cores 1..256, and RAM 1..1024 GiB. These are parser bounds, not recommended server sizes.

Choose a profile

Choice	Main effect
`survival`, `skyblock`, `minigame`	Select DEFAULT and restore native behavior switches and VANILLA goal cadence in the plan. They do not infer every game mechanic from a profile name.
`hub` or `lobby`	Select HUB, enable the behavior master switch, and apply five static-lobby gameplay restrictions.

HUB stops entity collisions, natural/periodic spawning, controlled block/chunk ticks, weather, and villager ticking. Read the preset effects first. Farms and survival progression may depend on these systems.

Automatic hardware and density

auto reports JVM-visible logical cores, visible system/container memory, and maximum heap. The planning memory budget uses current heap rounded up to GiB, not all host RAM. Processor names may be unavailable. Detection does not measure free memory or dedicated CPU capacity.

Recommendations are capped by processors available to the JVM. Console defaults use crowded density for HUB and spread density for other profiles. There is no separate console density argument. The wizard does not change JVM heap or server.properties.

Review, apply, or cancel

Read each old -> new change and its gameplay effect.
Use nusa setup preview <page> to review every page of that exact plan.
Run nusa setup apply only after all pages are reviewed. The original file is backed up in nusa-config-backups/ before atomic replacement.
Enter stop, wait for exit, and start again to activate saved settings.

nusa setup cancel discards the plan. Sessions expire after ten minutes. A changed configuration revision invalidates apply; preview again. Unsupported atomic replacement leaves the original and backup intact.

To restore settings, stop the server, copy the right backup to nusa-global.yml, and restart. This does not restore worlds.