Safe change steps
- Stop the Romestead dedicated server.
- Find the active config file and make a backup copy.
- Change only the player limit value first.
- Restart the server and confirm it still loads the correct world.
- Test with two or three players before filling all slots.
- Watch for lag, rubberbanding, delayed saves, or CPU/RAM spikes.
- If performance drops, reduce the player limit or move to a better host.
Player limit planning
| Group size | Hosting expectation | Risk to watch |
|---|---|---|
| 1-2 players | Good for home PC testing | Mostly setup and connection issues. |
| 3-5 players | Needs stable upload and enough RAM | Lag spikes, save pauses, and Wi-Fi problems. |
| 6-8 players | Better on a strong PC, VPS, or managed host | CPU headroom, upload, and world activity load. |
| More than your group actually needs | Not recommended for first test | Harder troubleshooting with no real benefit. |
Common mistakes
- Raising max players before confirming basic direct connect works.
- Changing max players, world size, port, and password at the same time.
- Blaming the player limit when the real issue is upload speed or UDP
8050. - Leaving too many open slots on a weak home PC.
- Skipping backups before changing config values on a live world.
When to move hosting
If the server is stable with two players but starts lagging with a larger group, the player limit is revealing a host capacity problem. Check CPU, RAM, upload speed, and player distance. If the group wants regular sessions, a VPS or managed host can be easier than keeping a gaming PC online.
Related Romestead server guides
Use config.json explained for settings, config file location if edits do not apply, server lag fix if more players create rubberbanding, and hosting options if your group needs a stronger host.