Mob Cap Explained, Why Your Server Has No Mobs

What Is the Mob Cap?

The mob cap is a limit on how many mobs can exist in a world at the same time. Once the cap is reached, no new mobs spawn until existing ones despawn or die. When players report "there are no mobs," the mob cap explained minecraft answer is almost always that the cap has been reached by mobs loaded in other areas.

How the Mob Cap Is Calculated

In vanilla Minecraft, the mob cap formula is:

cap = constant * chunks_eligible_for_spawning / 289

The constant differs by mob category:

Category	Constant
Monster	70
Creature (passive)	10
Ambient (bats)	15
Water Creature	5
Water Ambient	20

289 equals 17 squared, which is the number of chunks in a 17x17 area around each player. On a multiplayer server, the eligible chunk count grows with each player, but so does the number of loaded chunks where mobs accumulate. This is why mob cap explained minecraft issues get worse as player count rises.

Why Mobs Disappear on Busy Servers

On Paper and Spigot, the mob cap is often configured lower than vanilla for performance. If you set spawn-limits.monsters to 30 in bukkit.yml, the server allows far fewer monsters globally. With 20 players spread across the map, those 30 mob slots fill up instantly in dark caves and unlit areas, leaving surface players with an empty world.

Caves are especially problematic. A single unexplored cave system can hold dozens of mobs that count against the cap but are never interacted with. Lighting caves or reducing simulation distance helps reclaim those slots.

Configuring the Mob Cap

bukkit.yml

spawn-limits:
  monsters: 50
  animals: 8
  water-animals: 3
  water-ambient: 10
  ambient: 1

Paper per-player mob cap

Paper offers per-player mob spawning, which distributes the cap evenly among online players instead of sharing a global pool. Enable it in paper-world-defaults.yml:

entities:
  spawning:
    per-player-mob-spawns: true

This single setting solves most mob cap explained minecraft complaints. Each player gets their own share of the cap, so one player's loaded caves do not starve another player's spawns.

For per-world configuration, see our per-world mob cap guide.

Performance vs Gameplay Trade-off

Lowering mob caps improves TPS because fewer entities need to be ticked each server tick. However, setting caps too low makes the game feel lifeless. We recommend starting with the values above and adjusting based on Spark profiling data. If entity ticking is not your bottleneck, you can afford higher caps.

Need a server built for performance? Astroworld Hosting runs NVMe SSDs with optimized Paper configs on every plan.

Troubleshooting Checklist

• Enable per-player mob spawns in Paper.
• Check current mob counts with /spark health or a mob counting plugin.
• Light up caves near player bases to prevent passive cap consumption.
• Review mob spawning configuration for spawn rate tuning.
• Lower simulation distance to reduce the area where mobs load. See view distance guide.