Nightingale ships an example settings file and reads a copy of it. Until that copy exists, the server runs on defaults, which is why a first attempt at configuring it often appears to do nothing.
Create the settings file
- Stop the server.
- In the panel open Files and find
ExampleServerSettings.iniin the server directory. - Copy it to
ServerSettings.iniin the same folder. The example file is a template and is not read. - Edit
ServerSettings.ini.
Always edit with the server stopped. Changes made while it runs are lost when it shuts down.
The settings that matter
- Connection password, what players enter to join. This is the one you share.
- Admin password, what you use to get admin commands. Keep it separate and keep it to yourself.
- Starting difficulty, which accepts easy, medium, hard or extreme. It sets the realm difficulty when the world is created.
- Server name, how players identify your server.
The other config file
Nightingale also has a GameUserSettings.ini in the saved config folder, which holds engine and gameplay level values. Most people never need to touch it. When you do, back it up first, change one value at a time, and check the panel console after each restart.
Slots
Your plan's slot count is applied through the MAX_PLAYERS variable on your server's Startup Settings page, reachable from the server overview. Nightingale is designed around small groups, so the plans reflect what the game itself supports. Upgrade the plan in the billing area if you need more.
Do not change the port
The port value must match the one allocated to your server, shown on the server overview. Changing it makes the server unreachable.
Apply and verify
- Save the file.
- Start the server.
- Read the panel console, then try to join. If the connection password is not being asked for, the settings file was not read and is probably still named
ExampleServerSettings.ini.





