There is no single Minecraft “entity limit” setting. To get more naturally spawning mobs on a Java server, adjust the mob category’s spawn limit in Paper’s world configuration. To make entities update farther away, change simulation distance instead—this affects ticking, not the spawn-count cap. Bedrock worlds and add-ons use different controls.
First identify which limit you mean
“Entity limit” can describe several different behaviors. Changing the wrong setting may have no effect on the problem you are trying to solve.
| What you want to change | Relevant control | What it does—and does not do |
|---|---|---|
| More naturally spawned mobs | Paper Java server: category values under entities.spawning.spawn-limits |
Raises a natural-spawn category limit. It does not guarantee a higher spawn rate or improve performance. PaperMC configuration |
| Entities update at a greater distance | Simulation distance | Sets how far game mechanics, including living entities, are updated. It is not a mob-count cap. PaperMC server.properties reference |
| Entities remain fully active farther away | Spigot entity activation range | Controls the range for full entity activity; entities beyond it tick at a reduced rate. It is not a population limit. Spigot configuration |
| See more of the world | Render or view distance | Affects what is rendered or sent to the client, not the mob spawn cap. Microsoft’s Bedrock distance guide |
| Change custom entity spawning in Bedrock | Add-on spawn rules, population pools, and density limits | Sets behavior for entities defined through add-ons; it is not a global vanilla mob-cap setting. Microsoft’s data-driven spawn rules |
Raise natural mob limits on a Paper Java server
Before editing
- Confirm the server runs Paper, and note its Minecraft and Paper versions. Paper configuration names and layouts can change; use the files generated by the installed version.
- Back up the world and configuration files before making changes.
- Choose the category you actually want to affect, such as monsters, rather than changing every category indiscriminately.
Find the setting and make a targeted change
- Open the applicable Paper world configuration file for the world you want to change.
- Locate
entities.spawning.spawn-limitsand raise only the relevant category value. - Check whether that world inherits its value from
paper-world-defaults.yml. Paper’s documentation explains that unspecified world values inherit from the defaults file, so an override may be needed for a per-world change. - Apply the change using the restart or reload behavior supported by your installed Paper version, then test the result and monitor server performance.
Paper’s configuration example illustrates a monster value of 70 by default and a Nether monster value of 90. These are documentation example values, not a guarantee of defaults for every Minecraft/Paper version or a recommended target. Paper’s documentation does not establish a universally safe cap, predictable TPS result, or guaranteed increase in spawn rates for every farm or server.
Understand per-player mob spawning
Paper also documents per-player-mob-spawns, which changes whether a mob limit is counted per player or across the server. Paper says enabling it produces “roughly the same number of mobs, but with a more even distribution.” Treat it as a distribution option, not a universal multiplier for the total number of mobs. PaperMC world configuration
#1 Best Overall
Use simulation distance for ticking range, not mob count
Paper documents simulation-distance in server.properties as a radius, in chunks, within which living entities are updated. Its documented range is 3–32 chunks. Raising it can make mechanics update farther away, but it does not itself raise category spawn limits and can add server workload. PaperMC server.properties reference
Mojang’s Java release explanation likewise notes that entities, blocks, and fluids are not updated outside simulation distance. If mobs exist but stop behaving as expected at a distance, investigate simulation distance rather than the spawn-count cap. Minecraft: Caves & Cliffs: Part II out today on Java
Other Java server software has different controls
Do not assume a Paper setting or file applies to vanilla, Fabric, Forge, or every Spigot server. Spigot’s spigot.yml reference documents options including mob-spawn-range and entity-activation-range; the latter changes how far entities remain fully active, not how many may spawn. For a true population-cap change on other server software, consult documentation for that software and its installed version or a compatible mod/plugin. Spigot configuration
Bedrock: distinguish world simulation from add-on spawning
For a Bedrock world
Simulation distance controls the area where game mechanics are processed; render distance controls what the player sees. Microsoft’s guide describes Bedrock simulation distance as defaulting to 4 chunks and reaching up to 12 depending on the device. The available maximum varies, so check the current settings UI on the device and build you use. Neither setting should be treated as a universal vanilla mob-cap adjustment. Microsoft’s Bedrock distance guide
Ticking areas keep selected chunks active, but they do not make mobs spawn anywhere without a nearby player: Microsoft says mobs do not spawn in ticking areas unless a player is within simulation distance. The guide documents a maximum of 10 ticking areas per world, with up to 100 chunks in each. These are ticking-area limits, not mob-population targets. Microsoft’s Bedrock distance guide
For a Bedrock add-on creator
Custom entities can use data-driven spawn rules that assign them to population pools with a pool limit. The minecraft:density_limit component can also constrain local populations. These tools configure custom add-on spawning; they do not edit a global vanilla mob cap across Bedrock platforms. Microsoft recommends density limits to prevent overpopulation and warns that too many entities in an area can negatively affect performance. Data-driven spawn rules · Entity Spawning Deep Dive
Quick Recap
Best Value
Rank #4
If raising a limit does not make more mobs appear
- Verify the server software and file. A Paper world setting will not apply to a different server type, and the wrong world configuration will not change the world you are testing.
- Check the category and inheritance. Confirm the relevant category was changed and whether the world inherits its value from
paper-world-defaults.yml. - Check what is actually failing. A spawn-count limit, ticking distance, activation range, and visibility distance are separate controls; changing one does not fix the others.
- Change values incrementally. More entities can increase performance costs. The cited documentation provides no universal safe target, so observe the server or device rather than assuming a particular number is safe.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
