.png)
.png)
Make one change at a time so you can identify its effect. Before changing versions, importing a world or editing configuration, stop the server normally, wait for it to show offline, and create a completed backup in the panel. Keep a downloaded copy of important worlds too.
Change the right setting
For ordinary Java server settings, use the panel's Properties screen if available, or edit server.properties in Files while the server is stopped. The motd controls the message displayed in the multiplayer list; the service name shown in the panel is separate. Keep the assigned network ports unchanged. The server.properties reference explains common settings such as difficulty, view distance and the whitelist; available options depend on your installed server version.
For a private server, manage allowed players through the console's whitelist commands rather than manually rewriting whitelist.json. For example, whitelist add PLAYERNAME allows that player's Java name. Grant operator access only to trusted administrators. See the player data reference.
Investigate lag without losing progress
A single “Can't keep up” warning during startup or exploration is a clue, not proof that you need a larger plan. Note whether it repeats, how many players are online, and whether it coincides with new terrain, farms or plugins. Capture a short relevant console excerpt and the panel's CPU/memory readings. Ask support before changing Java memory flags or replacing the server software.
If a different or empty world appears after a change, stop and check the selected world name and files before saving more changes. Do not delete the existing world or use Reinstall as a reset button. Back up the complete world data, including dimensions, player data and any plugin-specific world folders, before attempting a restore.
