Skip to content
← Back to blog

Minecraft after the holidays: view-distance 32 kills the server, not the player count

Quick reality check: On Monday the clans come back. Not ten people one after another — twenty at once, Discord open, view-distance on 32 because “you can see further”. The server that held 20 TPS at 03:00 in the holidays with four players sits at 8 TPS at 18:00. Not because to…

Quick reality check: On Monday the clans come back. Not ten people one after another — twenty at once, Discord open, view-distance on 32 because “you can see further”. The server that held 20 TPS at 03:00 in the holidays with four players sits at 8 TPS at 18:00. Not because too many slots filled. Because every client wants chunks, and Paper simulates the world for everyone who is online.

view-distance and simulation-distance eat more RAM and tick than the player number on the price page. If you did not notice that in summer, you notice it in the first week of school.

What actually creates load

  • View-distance 32: each player loads a huge disc of chunks. Twelve people at 32 are not twelve people at 8. It is an open world that never stops streaming.
  • Simulation-distance: redstone, farms, hoppers, mob AI. What you turn off at night runs in parallel at 18:00 — in every loaded chunk.
  • Plugins that tick: CoreProtect, ChestShop, WorldGuard plus a cheap economy plugin. Idle 2 GB, peak 8 GB. Same box, different hour.
  • Vanilla or old Spigot: Paper spreads ticks differently. “Vanilla so it feels real” is paid in TPS once the clan is there. Compare: Paper vs Spigot.

The number in the panel at 03:00 is the wrong number. Peak is the first evening everyone joins at once.

What to change before the first school day

  1. View-distance 8–10. 12 already feels “far” and kills the single core. 32 is streaming, not a server. Want distance: OptiFine/Sodium on the client, do not hold the world for everyone.
  2. Simulation-distance below view-distance. Seeing may go further than ticking. Farms off-world: off, or a farm world with a cap.
  3. Paper, not hope. Paper or Purpur, current builds. Turn on TPS and timings before the clan arrives — Paper TPS.
  4. RAM for the peak, not idle. Vanilla, 10 people: often 4–6 GB. Plugins, WorldEdit, a few farms: closer to 8–12 GB. Numbers: Minecraft hardware. If the process dies it is often out of memory, not “too few slots”.
  5. No Discord bot on the same box in prime time. A ticket bot next to Paper is often fine. Lavalink plus a clan join is not. We walked through that here.

Why this week hurts

Holidays end, Discord fills up, Rust force wipe on 3 September for people who play both. Two peaks in five days. If you left Minecraft on “it will be fine” over summer, the bill arrives the first evening — in TPS, not on a Nitrado invoice.

Here a game server is CPU and RAM in the panel, traffic unlimited. No slot cap pretending 20 is the load. The load is view-distance times concurrent clients.

Order a Minecraft game server → All game servers · Hardware · Paper TPS

More

Explore NexoraHost