How to Configure Mob Cap Per World

Why Per-World Mob Caps Matter

Not every world on your server has the same needs. A survival world benefits from higher mob counts for gameplay, while a lobby or creative world needs almost zero hostile spawns. When you configure mob cap per world minecraft, you allocate entity resources where they matter and save CPU everywhere else.

Global vs Per-World Configuration

The global mob cap in bukkit.yml applies as the default for all worlds. Paper lets you override these values on a per-world basis using the paper-world.yml file inside each world folder. If a per-world file exists, its values take priority.

Setting Up Per-World Overrides in Paper

Navigate to your world folder, for example world_nether/paper-world.yml. Add or edit the spawning section:

entities:
  spawning:
    spawn-limits:
      monsters: 30
      animals: 5
      water-animals: 2
      water-ambient: 5
      ambient: 1

Repeat this for each world that needs custom values. Worlds without a paper-world.yml file fall back to paper-world-defaults.yml.

Recommended Values by World Type

World Type	Monsters	Animals	Ambient
Survival Overworld	50-70	8-10	1
Nether	30-40	0	0
The End	20-30	0	0
Creative/Build	0	3	0
Lobby/Hub	0	0	0
Resource/Mining	40-50	5	1

Per-Player Mob Spawns and Per-World Interaction

When Paper's per-player-mob-spawns is enabled (which we recommend), the per-world spawn limits are divided among players in that specific world. This means a world with 2 players and a monster cap of 50 gives each player roughly 25 monster slots. See the mob cap explained guide for how this calculation works.

If you configure mob cap per world minecraft alongside per-player spawns, you get fine-grained control: each world has its own ceiling, and within that ceiling each player gets a fair share.

Disabling Spawns Entirely

For lobby and hub worlds, set all spawn limits to 0 and also disable mob spawning in the world's gamerules:

/gamerule doMobSpawning false

Setting the spawn limits to 0 in Paper prevents new spawns. The gamerule ensures nothing spawns through other mechanisms. Together they guarantee a mob-free world.

Performance Impact

Reducing mob caps in worlds that do not need mobs directly lowers entity tick time. If you run 5 worlds but only 2 need mobs, you can cut entity processing significantly by zeroing out the other 3. Profile with Spark to measure the improvement.

See an optimized server in action: Astroworld MC, IP play.astroworldmc.com, Java + Bedrock.

Quick Setup Steps

• Set global defaults in bukkit.yml and paper-world-defaults.yml.
• Create paper-world.yml in each world folder that needs custom caps.
• Enable per-player-mob-spawns: true in Paper defaults.
• Set all caps to 0 for lobby/creative worlds.
• Test and profile. Configure mob cap per world minecraft based on actual needs, not guesses.