Why your 300-mod Minecraft pack is lagging (and what fixes it)
A modpack that lags on one host will usually lag on every host. Before you open a “my TPS is bad” ticket, work through these five checks.
1. Pre-generate your world
Un-generated terrain is the single biggest source of tick spikes in a fresh pack. Run Chunk Pregenerator for a 2,000-block radius before you invite players, then set your view distance sanely (8–10 for modded).
2. Check your view distance and simulation distance
Modded view distance above 10 is usually a mistake. Every extra chunk means more entities, more block updates and more networking.
3. Find the laggy mod
Use Spark (/spark profiler start) and look at the top of the tree. It is usually one of: a mob farm
with 400 entities, a badly written pipe network, or a world-save routine running on the main thread.
4. Give the JVM the right flags
On our Paper and Forge images we ship Aikar flags with a GC tuned for 8–16 GB heaps. If you are running a custom jar, copy the flags rather than inventing your own.
5. Then look at hardware
Minecraft is single-thread bound for the main tick loop. A Ryzen 9 9950X at 5.7 GHz will beat a 32-core EPYC on a 120-player survival world every single time, because the world tick only uses one thread.
Try it yourself. Every plan runs on the hardware discussed here — game hosting from ₹299/month with NVMe storage and 1 Tbps DDoS protection. Compare plans or ask us on Discord.
Deploy on hardware you can benchmark.
Deploy on AMD EPYC or Ryzen hardware with NVMe storage, 1 Tbps DDoS protection and a panel you'll actually enjoy using.