• chunk-loading-radius - how many chunks around each player get loaded ahead of time. Higher feels smoother but uses more RAM and CPU. 3 is a good start.
• max-chunks-to-load - how many chunks the plugin may load per server tick. Stops a sudden rush of loading from lagging the tick.
• max-cache-size - how many chunks are kept in a quick-access memory cache.
• cache-expiration-time - time in milliseconds before a cached chunk is dropped. 30000 = 30 seconds.

Lets the loading radius shrink or grow on its own based on how the server is doing.

• high-tick-threshold / high-memory-threshold - when tick time (ms) or memory use (%) goes above these, the radius drops to protect performance.
• low-tick-threshold / low-memory-threshold - when things are calm and you are below these, the radius is allowed to grow back.

A safety mode that clamps the radius down hard when the server is struggling.

• radius - the small radius used while in maintenance mode.
• tick-time-threshold / memory-threshold - the points where auto-maintenance kicks in.
• auto-maintenance - let the plugin turn this mode on and off by itself. Turn it off if you only want to control it with /maintenance.

Background worker threads used for chunk jobs. 0 means auto (picked from your CPU cores). Leave at 0 unless you really want a fixed number.

Every chunk has a "heat" value. Visited chunks get hot, ignored chunks cool down, and cold chunks get unloaded to free memory.

• heat-decay-rate - how fast heat cools off. Closer to 1 cools slower.
• heat-decay-interval - how often (ms) cooling runs.
• cold-threshold - heat below this counts as cold and can be unloaded.
• min-chunk-age - a chunk must be loaded at least this long (ms) before it can be unloaded. Stops load/unload flapping.
• visit-heat-increase - how much heat a chunk gains when used.
• proximity-heat-bonus - heat given to chunks near a player.
• safety-radius - chunks within this many chunks of any player are never unloaded.

Stops ChunkManager from fighting other plugins that keep chunks loaded on purpose. Works with Chunky, WorldBorder, vanilla /forceload, spawn chunks and redstone chunk-loaders.

• respect-force-loaded - never unload a chunk that is marked force-loaded.
• respect-plugin-tickets - never unload a chunk another plugin is holding open with a chunk ticket.
• pause-unload-during-pregen - while a pre-generator is busy making chunks in a world, ChunkManager stops unloading in that world so it does not undo the work.
• pregen-detect-seconds - how many seconds of quiet before a world counts as "done generating".
• pregen-chunk-threshold - how many fresh chunks (made away from players) within that window mean a pre-gen is running. Lower = more sensitive.

Tip: stand in a chunk and use /cminspect to see exactly why it is being kept loaded.

ChunkManager can pre-generate chunks itself with /cmpregen. It throttles on TPS so it does not lag the server.

• chunks-per-tick - how many chunks to generate each tick.
• tps-threshold - it only generates while TPS is at or above this, then waits if the server dips.
• actionbar-updates - show live progress in the action bar.

• memory.gc-min-interval - shortest time (ms) allowed between cleanups, so it does not spam the garbage collector.
• memory.low / critical-threshold - memory fill levels (0.85 = 85%) that trigger cleanups and warnings.
• gui - the /cm menu. update-interval is in ticks, cooldown is in ms between clicks.
• performance.export-metrics - write metrics to file. metrics-interval is in seconds.

enabled is the switch that matters here - it turns the whole advanced block on or off. The three features it runs:

• chunk-analyzer - rates how heavy each chunk is to tick (mob farms, redstone, etc).
• region-optimizer - groups chunks into regions and pre-loads the busy ones players keep returning to.
• prefetcher - watches movement and loads chunks ahead of where players are heading.

The numbers under each one are tuned internal defaults - you do not need to touch them, the enabled toggle is the real control.

Give ranks a bigger loading radius. Grant chunkmanager.radius.6 for a radius of 6, and so on. The highest tier a player has wins. Off by default.

Runs a cleanup pass at set times of day (great for quiet early-morning hours).

• times - 24h clock times to run, like '04:00'.
• What it actually does - it runs the smart unloader hard, clearing out cold, unused chunks across your worlds in one go to free memory.
• aggressive-target - how many chunks per world it tries to unload in that pass. Higher frees more at once. It still skips chunks near players, frozen, force-loaded or held by other plugins.
• log-results - print how much was cleaned to console.

• keep-regions-loaded - keep chunks inside WorldGuard regions loaded at all times.
• check-on-unload - before unloading a chunk, make sure it is not inside a protected region.
• region-whitelist - only these region names are affected. Empty means all regions.
• scan-interval - how often (seconds) to re-scan regions.

Caps how many entities a single chunk can hold and culls the extras to fight entity lag. All limits are per chunk. Named mobs, players and equipped armor stands are always kept. Off by default.

• total-limit - hard cap on entities in one chunk.
• hostile-limit / passive-limit / item-limit - separate caps for monsters, animals and dropped items.

Slows down the plugin's own chunk work when TPS drops.

• min-tps - at or below this, chunk work is heavily held back.
• target-tps - the TPS it tries to keep the server at.

A simple on/off for the load-priority system. The idea is that when a lot of chunks are queued at once, the ones closest to players are meant to load first instead of in random order. Nothing else to set here - just on or off.

A "chunk ticket" is a tag that asks the server to keep a chunk loaded for a while, even with no player nearby. With this on, ChunkManager can hand out its own short tickets (for example to keep an area warm right after a teleport) so a chunk does not instantly unload and reload.

• default-duration - how long (seconds) a ticket lasts before it expires and the chunk is free to unload again. 300 = 5 minutes.

Off by default. This is ChunkManager's own ticket system - it still respects tickets from other plugins through the preloaded-chunks settings above.

Loads chunks at the destination before a player arrives, so they do not land in an unloaded void.

• teleport-preload.radius - chunks loaded around a teleport target.
• portal-preload.radius - chunks loaded around the other side of a portal.

Trims the loading radius for laggy (high-ping) players to ease their connection, while low-ping players keep the full radius. The three numbers are the ping (ms) borders: above medium loses 1 chunk, above high loses 2, very high loses 3. Off by default.

If GeyserMC is installed, Bedrock players get a smaller radius since their view distance is lower. radius-reduction is how many chunks to trim for them.

Measures which chunks are the most expensive to tick (mob farms, redstone, etc). Feeds /cmtop and the map overlay. update-interval is in ticks.

On Folia, shows TPS and MSPT per region with /cmrtps. update-interval is in ticks.

Draws your hottest / most expensive chunks onto Dynmap or BlueMap.

• top-count - how many of the top chunks to show.
• refresh-interval - how often (seconds) the overlay redraws.

• logging-level - console detail. Use FINE for more, WARNING for less.
• language - plugin language. en, es, fr, de, pt, it, ru, ja, ko, zh, ar.
• broadcast-maintenance-changes - announce maintenance mode to everyone.
• world-blacklist - worlds ChunkManager fully ignores. Nothing is loaded, unloaded or managed in these.