Players get kicked, lag, or stall when many join at once — why?
When a crowd of players joins at the same time, both your CPU and your bandwidth spike as the server loads chunks for everyone at once. That surge is what causes the kicks, lag, and stalls — and a few tweaks smooth it right out.
Why a join surge hits so hard
Every player who joins pulls a fresh set of chunks around them, and the server has to load (and sometimes generate) all of them. When many people arrive together, the CPU is busy with chunk loading while your bandwidth carries all that world data at once. If either runs short for a moment, players time out or the whole server stalls until it catches up.
How to smooth out join surges
- Open the Files tab and lower view distance and simulation distance in
server.propertiesso each join loads fewer chunks. - Pre-generate your world (with a plugin or mod) so joins load existing terrain instead of triggering heavy world generation on the spot.
- In the Startup tab, make sure you have adequate RAM and a proper RAM Buffer (Xmx) set, so a spike doesn't push the server out of memory.
- Watch the Console tab during a join wave — a misbehaving plugin or mod that fires on player join can amplify the lag.
Tip: Pre-generating chunks is one of the biggest wins for servers that lag when players spread out or teleport. It's worth doing once for any busy community.
Frequently asked questions
Players get kicked with "timed out" — what's happening? That's usually chunk-load lag on join. Reduce your view distance and pre-generate the world, and the timeouts typically disappear.
What if it's high ping rather than lag? High ping specifically points to network latency rather than server load. Choose the region closest to your players (Washington for NA, Germany for EU) — see the region and latency guidance in our VPS section for more.