1. Start with the real player count
Plan for the people who will play regularly, not the number you hope to reach. A small vanilla or Paper world for a few friends can start around 2–3 GB of memory. Mods, large view distances, pregenerated maps, and busy farms need more.
2. Pick Paper unless a modpack decides for you
Paper is a sensible beginner default for Java Edition because it supports plugins and includes useful performance improvements. Use Fabric, Forge, NeoForge, or another loader only when your chosen modpack requires it.
3. Accept the Minecraft EULA yourself
Read and accept the Minecraft EULA when the panel prompts you. A host should not pretend that this agreement does not exist or accept it invisibly on your behalf.
4. Protect operator access
Use a unique account password, enable two-factor authentication when available, and grant operator permissions only to people you trust. Never paste panel credentials or API keys into Discord.
5. Configure a whitelist first
Keep the whitelist enabled while testing. Confirm the spawn area, difficulty, game rules, permissions, and plugin configuration before publishing the address.
6. Make and download a backup
Create a backup after the first successful boot and before every major update. A backup stored on the same VPS helps with mistakes but is not disaster-proof, so download copies of worlds you cannot afford to lose.
7. Watch performance before upgrading
Check memory, CPU, tick rate, and console warnings during a real play session. Upgrade because measurements show a limit—not because a plan promises an arbitrary player-slot number.
8. Keep a simple update routine
Back up, read the release notes, update Paper and plugins, start the server, then test joining and basic commands. Avoid changing the game version and every plugin at the same time.