Mastering Server Performance with ChunkEntityLimiter
Running a Minecraft server is a balancing act. You want players to build massive farms, explore dense biomes, and enjoy the chaos of a hundred creepers, but you also need the server to stay responsive. When entity counts spiral out of control, tick rates plummet and everyone suffers. That is where ChunkEntityLimiter steps in — a high-performance plugin designed to intelligently cap mobs and items without breaking the game’s natural feel.
What Is ChunkEntityLimiter?
ChunkEntityLimiter is a lightweight yet powerful entity and item limiter built for modern server platforms including Folia, Paper, Bukkit, Purpur, and Spigot. Unlike crude clear-lag plugins that wipe everything periodically, this tool uses a dual-check system: it enforces a per-chunk limit and a surrounding-chunks limit around each player. The result is targeted cleanup that prevents lag spikes from mob grinders or massive item drops while preserving important entities like named pets, bosses, and equipped mobs.
Key Features That Set It Apart
Native Folia Support
Folia’s regional threading architecture demands plugins that respect its multi-threaded design. ChunkEntityLimiter is fully optimized for Folia, ensuring that entity checks run smoothly across independent regions without causing synchronization bottlenecks.
Smart Cleanup Logic: Oldest First
Instead of randomly deleting entities, the plugin sorts removable entities by spawn time and removes the oldest ones first. This means a freshly spawned zombie from a natural spawn cycle stays alive, while the 200 zombies that have been crammed in a mob farm for hours get cleared. The logic keeps the world feeling alive and fair.
Dual-Layer Limiting
Two limits work together: a strict per-chunk cap and a softer radius-based cap for chunks surrounding a player. The radius multiplier (configurable) allows a bit more breathing room near active players, so you do not accidentally clear entities they are actively interacting with. This dual approach is far more nuanced than a single global limit.
Precise Item Counting
Item drops can be counted by stack size or by entity count. With count-item-stack-amount: true, a stack of 64 cobblestone counts as 64 toward the limit, not 1. This prevents a single dropped stack from bypassing the limiter while still allowing a reasonable number of distinct item entities.
Granular Notifications and Performance Monitoring
Server admins can fine-tune who sees cleanup reports and overload warnings — nobody, only operators, or all nearby players. A built-in performance profiler tracks execution times for classification, sorting, and cleanup phases, helping you optimize the check interval without guesswork.
Protection That Respects Player Effort
ChunkEntityLimiter categorizes every entity as either protected or removable. By default, named entities, leashed mobs, tamed animals, equipped creatures, and bosses are all protected. They are skipped during cleanup unless the clean-protected-if-over-limit option is enabled, which only removes protected entities after all normal ones have been cleared and the limit is still exceeded. This layered protection ensures that a player’s prized horse or a wither boss fight is never interrupted by automated cleanup.
Commands and Permissions at a Glance
Managing the plugin is intuitive with the /chunklimit command (aliases /cl and /climit). Here are the core subcommands:
- /chunklimit reload — Reloads the configuration file instantly. Requires
chunklimiter.reload(default: op). - /chunklimit stats — Displays detailed entity statistics for the current chunk and surrounding radius. Available to all players by default.
- /chunklimit notify [type] [scope] — Sets notification preferences for cleanup reports or overload warnings. Scope can be
none,op, orall. Example:/cl notify report op. - /chunklimit performance [reset] — Views performance metrics like classification and cleanup times. Useful for tuning the check interval.
Configuration That Adapts to Your Server
The config.yml is extensive yet well-commented. You can set a default entity limit (e.g., 100 per chunk), a separate item limit (300), and custom limits for specific mobs like zombies or creepers. Ignored types let you exclude villagers or iron golems from counting entirely. The check interval can be set to 600 ticks (30 seconds) or 1200 ticks (60 seconds) to balance responsiveness with CPU load. For Folia servers, disabling clean-all-loaded-chunks and relying only on player-radius checks is recommended to avoid global scans that conflict with region threading.
Setting up ChunkEntityLimiter is straightforward. You can download the plugin and drop it into your server’s plugins folder, or if you are using a launcher like foxygame.net, you can install it directly from the launcher’s built-in mod menu — a convenient, flexible, and modern Minecraft launcher that simplifies managing your server’s plugins. This approach saves time and ensures you always have the latest version without hunting through forums.
Why ChunkEntityLimiter Beats Traditional ClearLag Plugins
Most clear-lag solutions blindly remove all ground items or all hostile mobs on a timer. That approach can wipe out a player’s freshly dropped gear or a carefully bred animal. ChunkEntityLimiter’s oldest-first sorting and protection checks mean that only truly excess entities are removed. The dual-layer limit prevents a single chunk from hogging resources while still allowing natural density around players. Combined with precise item counting and configurable notifications, it gives server owners surgical control over performance without sacrificing gameplay quality.
Final Thoughts
ChunkEntityLimiter is a must-have for any Minecraft server administrator who wants to maintain high TPS without resorting to heavy-handed entity wipes. Its intelligent cleanup logic, Folia compatibility, and granular configuration make it a standout choice. Whether you run a small community server or a large network, this plugin will keep your worlds lag-free while respecting the effort players put into their builds and mobs. Take the time to tune the limits to your server’s unique needs, and you will notice the difference immediately.