HomeGuidesGetting started

The seven beginner mistakes we see every week

Kill instead of stop, a modpack on 2 GB, a plugin for the wrong version. Here is how to avoid them.

1 min readUpdated 2026-09-14Diese Anleitung auf Deutsch lesen →
  1. Killing instead of stopping. Kill skips saving. Worlds get corrupted this way. Use Stop; use Kill only when Stop hangs.
  2. Too little RAM for the job. A vanilla server for five friends is fine on 2 GB. A modpack with 150 mods wants 6-8 GB. Check the RAM guide before ordering.
  3. Plugins for the wrong software. Bukkit/Spigot/Paper plugins do not run on Forge or Fabric, and mods do not run on Paper. The installer only shows what fits your server.
  4. Editing server.properties while the server runs. The server overwrites the file on stop. Stop first, edit, start.
  5. Uploading a world into the wrong folder. The world folder must sit directly in the server root and be named exactly as level-name in server.properties (default world).
  6. Forgetting the EULA. Minecraft Java refuses to start until eula=true in eula.txt. The panel asks you the first time.
  7. Letting the days run out. Turn on auto-renew in the dashboard and keep a little balance, or set a reminder. A suspended server keeps its files, but nobody can join.