Overview
Estimate memory using player count, plugins, mods, view distance and world activity. The safest approach is to document the current setup first, create a backup and then make controlled changes while watching the server logs and resource usage.
Before starting: confirm that you have a recent backup and access to the server console or control panel.
Recommended process
- Create a current backup before making changes.
- Check the service requirements, versions and available resources.
- Change one setting or component at a time so problems are easy to isolate.
- Review the server console and log files after each change.
- Test with a small number of users before applying the change broadly.
What to check
- Versions: server software, mods, plugins and client files must be compatible.
- Resources: review CPU, memory, disk space and network usage.
- Logs: warnings and errors often identify the exact file or component causing the issue.
- Backups: keep at least one copy outside the live server.
- Testing: reproduce the issue with the minimum number of components enabled.
Common mistakes
Avoid changing several settings at once, deleting files without a backup, using outdated tutorials for a different software version, or assuming that more RAM will fix a CPU or configuration problem.
Related guides
- Paper vs Purpur: Which Server Software Should You Use?
- Forge vs Fabric for Minecraft Servers
- How to Reduce Minecraft Server Lag
- Minecraft Server Backup Best Practices
24 Play customers can contact support for help with supported hosting services and control-panel features.