These four cover nearly every HumanitZ ticket.
1. Settings revert after a restart
- The server writes
GameServerSettings.iniwhen it shuts down, so anything you type while it is running is thrown away. - Stop the server, wait for it to report offline, then edit and save.
- The in game settings menu does not apply to a dedicated server. Only the file counts.
2. The server will not start or is not listed
- Remove the word Official from your server name. HumanitZ treats that name specially and the server may refuse to start or list.
- Read the first lines of the Console after a start attempt. A broken settings file is reported there.
- If the file is damaged, restore it from a backup or delete your changes and let the server write a fresh one, then reapply the changes one at a time.
3. The world reset
- The save is written on a clean shutdown. Use Stop rather than Kill, and give it time to finish.
- Download a copy of the save folder from the Files tab before any large change.
- If the server was updated and the save is from an older build, the world may not load. The console reports it during boot.
4. Players cannot join
- Check
MaxPlayersin the settings file. - Confirm the password has no stray space.
- Make sure everyone is on the same game version and restart the server after a game update.
- Give players the direct connect route with
IP:Portrather than relying on the browser.
5. The server is slow or restarts on its own
If the console shows the process being killed rather than a game error, the server ran out of memory. Lower the player limit or move to a larger plan. A scheduled nightly restart, set up in the Schedules section of the panel, keeps a long running server healthy.
Open a ticket from Support in the Client Area with the last 50 lines of console output if none of this fits.





