Nightingale settings problems come down to a short list. Work through it in order, using the panel Console to see what the server actually did at startup.
1. The settings file does not exist yet
The server ships ExampleServerSettings.ini as a template and reads ServerSettings.ini. If you edited the example file, nothing you did is being read.
- Stop the server.
- In Files, copy
ExampleServerSettings.initoServerSettings.ini. - Put your settings in the copy.
- Start the server.
2. You edited while the server was running
The settings are written back on shutdown, overwriting anything changed underneath. The order is always stop, edit, start.
3. The wrong password is being changed
There are two passwords and they do different jobs:
- The connection password is what players enter to join.
- The admin password is what unlocks admin commands.
Setting one when you meant the other looks like the setting being ignored.
4. Difficulty only applies to a new realm
The starting difficulty is used when the realm is created. Changing it later does not reshape an existing world. To play at a different difficulty you need a new realm.
5. A version update changed something
Nightingale's dedicated server is still evolving and settings occasionally move or get renamed between versions. After a game update, read the panel console from the top of the first start. It reports settings it did not understand.
Verify a change took effect
The connection password is the fastest test. Set one, restart, and try to join. If you are not asked for it, the settings file is not being read at all, and cause one above is almost certainly why.
Back up before you experiment
- Stop the server so the realm is fully written.
- In Files, download
ServerSettings.iniand the save folder.
What to send support
Open a ticket with the contents of your ServerSettings.ini pasted as text rather than a screenshot, with the passwords removed, and the first hundred lines of console output from a fresh start.





