How to change the mob spawn rate on a Minecraft server?

Want more chaos or a calmer world? Tweak your Minecraft server’s mob spawn rate in minutes without tanking performance. Upgrade your experience on our premium Minecraft hosting.

Prerequisites

• Access to the Oxygenserv panel (your login and password)
• Server running Spigot/Paper (the bukkit.yml file must exist)
• A backup of bukkit.yml before editing
• File editor in the panel (or SFTP access)
• Console access or operator rights to test in-game

Detailed steps

1. Stop your server cleanly
   Log in to the Oxygenserv panel and open your server page. Click the red “Stop” button and wait for the console to say the server stopped. If it hangs for 60 seconds, use “Force stop,” then wait another 10 seconds before editing files.
2. Open and back up bukkit.yml
   Go to the “Files” tab and open bukkit.yml (it’s in the server root). If it’s missing, you’re likely on Vanilla: install Spigot/Paper, start the server once, stop it, and the file will generate. Make a copy first (Duplicate or Download). Keep YAML indentation intact (spaces only, no tabs) to avoid startup errors.
3. Set mob caps with spawn-limits
   In bukkit.yml, find the spawn-limits: section. These caps limit how many mobs can exist at once per world. Common defaults (Paper/Spigot):
   spawn-limits:\n monsters: 70\n animals: 10\n water-animals: 5\n water-ambient: 20\n water-underground-creature: 5\n ambient: 15
   Increase for more mobs (e.g., monsters: 90), decrease to reduce load (e.g., monsters: 50). Change in 10–20 steps and test between tweaks.
4. Tune spawn frequency with ticks-per
   Still in bukkit.yml, locate the ticks-per: section. Higher values mean fewer spawn attempts (less CPU). Typical values:
   ticks-per:\n animal-spawns: 400\n monster-spawns: 1\n water-spawns: 1\n ambient-spawns: 1
   To slightly reduce CPU pressure, set monster-spawns: 2 or 3. Avoid huge jumps; if spawns feel too sparse, lower the value again.
5. Save and restart the server
   Click “Save” (green button). Open the “Console” and hit “Restart.” Watch startup: you’ll see “Done (X.XXXs)! For help, type “help”” when it’s ready. If you get errors like “while scanning a simple key,” you have a YAML issue—fix the indentation or restore your backup.
6. Validate in-game
   Join the server and move to a typical spawn area (plains, nighttime for monsters). Ensure /gamerule doMobSpawning true and a non-peaceful difficulty (/difficulty normal). Press F3 to monitor nearby entities (“E:” line). If nothing spawns, check light levels, weather, biome, and make sure you aren’t on Peaceful.
7. Fine-tune spawn range and distances (optional)
   For deeper control, edit spigot.yml under world-settings: default:. Lower mob-spawn-range to shrink the candidate area around players:
   world-settings:\n default:\n mob-spawn-range: 6
   You can also reduce engine load by lowering simulation-distance and view-distance in server.properties (e.g., simulation-distance=8, view-distance=8), then restart and test.

Tips & optimization

– Make small changes: +10 to +20 on monsters is usually enough. Above ~100, expect TPS drops on modest hardware.
– On Paper, enable per-player spawns for fair distribution: in paper-world-defaults.yml → world-settings: default: per-player-mob-spawns: true (restart required).
– Shrink spawn reach: mob-spawn-range: 4–6 in spigot.yml cuts candidate chunks and reduces load.
– Measure impact: /timings on, play 5 minutes, then /timings paste; if entities dominate, lower your limits.
– Remember: spawn-limits doesn’t affect spawners or command-summoned mobs—use plugins or specific gamerules for those.

FAQ

I don’t have bukkit.yml. What now?

It doesn’t exist on Vanilla. Install Spigot or Paper, start the server once, stop it, and the file will appear. If it doesn’t, confirm your server jar is set to Spigot/Paper and the panel launches the correct file.

After changes, mobs stopped spawning

Check /gamerule doMobSpawning true and difficulty (not Peaceful). Validate YAML syntax (no tabs, correct indentation). Ensure you didn’t set values too low (e.g., monsters: 0). Some anti-lag plugins can block spawns as well.

What’s the difference between spawn-limits and ticks-per?

spawn-limits sets the MAX number of mobs per world. ticks-per controls how often spawn attempts run (higher = less often). Use both to balance density and performance.

Performance tanked after increasing spawns, how do I fix it?

Lower monsters by 10–20, raise monster-spawns slightly (e.g., 2–3), reduce mob-spawn-range, and lower simulation-distance. Profile with /timings to confirm improvements.

Test, measure, adjust—that’s the winning loop for a fun, smooth server. Need help dialing it in? We’re here to guide you to the sweet spot.

Related articles

• Introduction to the world of Minecraft servers
• What type of server for my Minecraft server? Spigot vs Paper
• How do you choose the right features for your Minecraft server?