Minecraft dedicated server: a calm defaults-first setup

Minecraft is forgiving until it is not: chunk IO spikes, garbage collection pauses, and plugin chains turn “it ran fine at 3 players” into midnight Discord pings. This guide is about defaults you will not regret before you open the server to strangers.

Paper (or fork) vs Vanilla

For public multiplayer, Paper (and compatible forks) remain the pragmatic baseline: bug fixes, performance patches, and an API for moderation tools. The upstream Paper docs are the authority on install and migration — see Paper’s getting started for supported Java versions and download flow.

Pure Vanilla is fine for tiny co-op LANs. Once you add sleep voting, anti-cheat, or rollbacks, you are already halfway to a modded stack — own that choice early.

RAM and JVM: stop chasing “more heap”

Allocate enough heap for the world + plugins, but leave headroom for the OS page cache and native zlib offloads. A common mistake is setting -Xmx to “all the RAM” and starving the host. Start conservative, watch GC logs under load, then tune.

Ports and discovery

Default 25565 TCP is what players expect. If you change it, document it in MOTD and your community wiki. For public internet hosting, pair this guide with our port forwarding overview so UDP/TCP expectations match your edge router.

Backups before anything else

Snapshot the world folder on a schedule that matches how much progress you are willing to lose. Our backups and snapshots page works through RPO and RTO in concrete terms.

When to call a host

If you are fighting CGNAT, TLS for a custom domain, or repeatable blue/green updates, those are the problems a dedicated operator handles routinely rather than researching from scratch. Contact us with player count, mod list, and whether you already run Docker or bare metal.