Safe rename steps
- Stop the Romestead dedicated server.
- Find the active config file in the server install folder.
- Make a backup copy before editing.
- Change only the server name value first.
- Keep the name simple while testing: letters, numbers, spaces, and a short group tag.
- Save the file and restart the server.
- Ask one friend to search the exact name and also try direct connect.
Why the new name may not show
| Symptom | Likely cause | Fix |
|---|---|---|
| Old name still appears | Server list cache or wrong config edited | Wait a few minutes, then confirm active config location. |
| Server disappears from list | Restart delay, filter, or connection issue | Test direct connect before changing more settings. |
| Name changes but friends cannot join | Port, password, or firewall issue | Return to UDP 8050 and password checks. |
| Server fails to start after rename | Broken JSON punctuation | Restore backup config and edit again carefully. |
Good server name pattern
Use a name your group can search exactly, such as RiverCrew Romestead or Alex Co-op World. Avoid very long names, symbols, or names that look like many other public servers. If your server is private, do not put the password in the name.
Before blaming the server list
- Direct connect can work even when the browser list is delayed.
- A changed server name does not fix a blocked port.
- A changed server name does not fix a wrong password.
- If the active world changed too, check config values before inviting the full group.
Related Romestead server guides
Use config file location if the name does not apply, config.json explained for settings, server not showing in list for browser delays, and password not working if friends can find the server but cannot join.