Set the customer-facing basics
The validated Necesse server workflow exposes a save name, player-slot count and optional server password. Additional server behavior is stored in server.cfg, while world-specific settings travel with the world save.
Safe setup checklist
- Choose the intended save name before players begin progressing.
- Set a realistic player-slot limit for the community.
- Set an optional join password if the world should be private.
- Start the server and verify the correct world loaded before sharing the address.
- Back up the save before changing world-level settings or installing Workshop content.
Move an existing Necesse world
Stop the server before replacing a Necesse save. Upload the complete compatible world/save data through the validated Runic workflow, keep server.cfg and world settings associated with the intended save, then start and verify progression before deleting the source backup.