1. Back Up
Copy current config, save path, and mod list before editing serverconfig.xml.
BackupUse this serverconfig.xml planning page to sort settings by risk, keep backups, explain rules to players, and connect config changes to troubleshooting paths.
Safe Edit Order
Server config edits can affect visibility, joining, EAC behavior, performance, world rules, and player trust. Write down what changed.
Copy current config, save path, and mod list before editing serverconfig.xml.
BackupStart with name, description, password, message, region, and player-facing rules.
Low riskTreat EAC, world generation, progression, save paths, and mod requirements as high impact.
High riskRestart once, join from a clean client, and confirm the server appears as expected.
Verify| Config area | Common user question | Safe handling |
|---|---|---|
| Identity | How do players find the server? | Keep server name, description, region, and password rules clear. |
| Access | Why can't players join? | Check password, whitelist, player cap, version, EAC, and mod requirements. |
| EAC | Should EAC be enabled? | Make the rule visible and avoid changing anti-cheat settings casually. |
| World and save | Will config changes affect the world? | Back up before touching world, seed, save, difficulty, or progression settings. |
| Mods | Do players need the same mods? | Document server-side, client-side, and both-sides requirements. |
| Performance | Why is the server lagging? | Track player count, region, hardware, mods, restarts, and recent updates. |
Config FAQ
Check status, ports, firewall, listing delay, region filters, version, and server name before rewriting config.
Troubleshooting guideOnly after you understand player impact and server rules. Treat EAC as a high-risk setting, not a quick fix.
Mods may require player instructions, load-order notes, server-side installation, or a fresh save. Pair config changes with the mod install guide.