KOLOSOK · OPS MANUAL
Guide · Hosting

Running a Minecraft Java Server Without Learning Everything the Hard Way

This is the guide I wish existed before my first server melted at eight players: RAM sizing that matches reality, software that fits your goal, and the diagnostics that tell you why TPS dropped before anyone blames the host.

RAM: the number that everyone gets wrong

The most common hosting mistake is buying too much RAM. Minecraft's server loop is mostly single-threaded; a 16 GB allocation on a weak CPU performs worse than 4 GB on a strong one. Oversized heaps make Java's garbage collector pause longer, which players feel as periodic stutter.

SetupPlayersSensible RAM
Vanilla / Paper, no plugins2–53 GB
Paper + plugins5–154–6 GB
Paper + many plugins, big view distance15–306–8 GB
Fabric modpack (light)3–86–8 GB
Fabric/Forge modpack (heavy)3–108–12 GB
Launch flag baseline: -Xms4G -Xmx4G with G1GC. Keeping minimum and maximum equal avoids resize pauses. More than 10–12 GB for a single server almost never helps.

Choosing the server software

Paper

The default answer for 90% of servers. A Spigot fork with hundreds of bug fixes, better entity handling and plugin support. If you cannot name a reason to avoid it, use it.

Spigot

Use only when a specific plugin refuses to run on Paper. Otherwise it is strictly a downgrade.

Fabric / Forge

For modpacks. Fabric is lighter and updates faster; Forge has the bigger legacy catalogue. Do not mix plugins into modded servers — pick one ecosystem per server.

Vanilla

Pure Mojang jar. Choose it for technical farm servers or exact vanilla mechanics; everything else performs worse on it.

TPS: reading your server's pulse

TPS (ticks per second) is the server's heartbeat, targeting 20. On Paper, run /tps in console: 19–20 is healthy, 17–19 is "players notice", below 15 means something is structurally wrong. The second number to watch is /timings on (or spark profiler) output — it names the exact plugin, entity type or chunk region eating your tick.

20target TPS<18players feel it<15fix it todayMSPTper-tick cost

The usual TPS killers, in order of how often they are guilty: runaway mob farms with thousands of stacked entities, hopper lines moving items across long distances, map-art canvases with thousands of item frames, chunk-loaders keeping hundreds of chunks ticking, and one player's flying-machine redstone contraption. Each is fixable with entity culling, hoppers swapped for water streams, and plugin limits.

A starter plugin shelf

Do not install thirty plugins on day one. Each one is a dependency, an update burden and a potential lag source. A stable starter set: EssentialsX (homes, warps, basic commands), LuckPerms (permissions), Chunky (pre-generate the world so players never wait on chunk gen), Vault (economy bridge), and a backup plugin such as ArmoredElytra-style no — keep it simple: a cron job or plugin that zips the world folder on a schedule. Everything else can wait until a real need appears.

Skip on day one: multi-world managers, heavy minigame suites, economy shops with thousands of sign-based transactions, and any plugin last updated for an older Minecraft version than yours.

Backups: the least glamorous lifesaver

Rule: a backup you have not tested restoring is not a backup. Zip the world folder, verify the archive opens, and keep at least three generations — daily, weekly, and one "before the big update" snapshot. World corruption from crashes is rare; corrupted world folders from failed manual edits are not. Store backups off the server machine if you can, because a disk failure takes the copy with the original.

Onboarding players, or why servers stay empty

Technical stability is half the job. The other half: a spawn area that explains itself in ten seconds, a short welcome message with the three commands a newcomer actually needs, and rules visible in-game, not on a Discord nobody joined. Servers that grow share one trait — a returning player can figure out "what's new" without asking anyone. A small, regularly updated notice board at spawn outperforms any amount of advertising.

Health checklist before launch day: TPS at 20 with two players online, backups scheduled and restore-tested, view distance 8–10, spawn-protection enabled, and a whitelist if you are not ready for strangers.

FAQ

How much RAM does a Minecraft server need?

3–4 GB for small vanilla or Paper servers, 4–6 GB for 10 players with plugins, 8–12 GB for heavy modpacks. More is not better — oversized heaps lengthen garbage collection pauses.

What is TPS and what is a good value?

Ticks per second, targeting 20. Below 18 players notice lag; below 15 something is structurally wrong. Profile with spark or timings before touching hardware.

Paper, Spigot or vanilla?

Paper for most servers — it is a faster, more bug-fixed Spigot fork with plugin support. Vanilla only for pure technical farms or exact mechanics.

Do I need to pre-generate the world?

Strongly recommended. Chunk generation is the most expensive operation a server performs; generating it ahead of time with Chunky removes the classic "world holes and stutter while exploring" complaint.

Keep reading