# Changelogs: ### Added: - Nothing ### Fixed: - **ItemsAdder: items dropped by players were never cleared.** On servers with ItemsAdder, every item a player threw out was treated as ItemsAdder content and skipped by the clear, while block drops were removed normally. Now only real ItemsAdder custom items are protected; normal drops are cleared again. The same fix applies to Nexo and Oraxen. ### Removed: - Nothing

# Changelogs: ### Added: - Nothing ### Fixed: - **Smart Stacking now really stacks non-stackable items.** Identical potions, stews or tools were never merged, although the config promised it. They now stack into one pile with a name tag (e.g. `Mushroom Stew x5`). Damaged tools are left unstacked on purpose. - **Hoppers no longer destroy items from stacked piles.** A hopper picking up a pile like `Stone x94` kept 64 and the other 30 vanished. Now everything goes into the hopper, and whatever does not fit stays on the ground. ### Removed: - Nothing

# Changelogs: ### Added: - Nothing ### Fixed: - **Smart Stacking: name tags disappeared and items were lost.** When a stacked pile (e.g. `Stone x94`) lay next to a normal item stack, Minecraft merged the pile into that stack, which removed the name tag and almost all of the items. ClearLag now handles these merges itself, so the pile keeps its name tag and its full count (`Stone x94` + 5 stone becomes `Stone x99`). Your `max-stack-limit` setting and death-item protection still apply. ### Removed: - Nothing

# Changelogs: ### Added: - Nothing ): ### Fixed: - **Armor stands no longer disappear when placed.** Sometimes placing an armor stand took the item from the player but placed nothing. The mob spawn limiter counted armor stands as mobs and blocked them once an area was full, and it could even remove armor stands that were already standing. Armor stands are now completely ignored by the mob spawn limiter. - **The armor stand / item frame limiter no longer eats items.** When the limit is reached, the placement is blocked and the player keeps the item. Players with `clearlag.bypass.limit` can always place them. - **The armor stand / item frame limiter now stays off when it is not in your config.** Older configs without this section had the limiter running silently (10 per chunk, 100 per world). It is now off unless you turn it on, like in the default config. ### Removed: - Nothing (:

# Changelogs: ### Added: - **Per-world auto-clear messages** The auto-clear countdown and success messages (and their sounds) went to every online player regardless of the world they were in. The new list limits them to players in the named worlds (case-insensitive). An empty list — the default, also when the key is missing from an existing config — keeps the old behaviour of messaging every world. ### Fixed: - Nothing ### Removed: - Nothing

# Changelogs: ### Added: - Nothing ### Fixed: - **Holograms and shop items from other plugins no longer get cleared.** Until now ClearLag only protected holograms from DecentHolograms, HolographicDisplays and FancyHolograms. Chest-shop plugins that create their own holograms and floating display items (for example mc-PlayerShop) lost them on every auto-clear. ClearLag now recognises these on its own, no matter which plugin placed them: hologram/display entities, click hitboxes, and floating items that can never be picked up, never despawn, have no gravity or sit on another entity. Normal dropped items are not affected. On by default, can be turned off with `hooks.holograms.plugin-displays-immune: false`. - **Item Merge no longer touches shop display items.** A shop's floating item could previously be merged with a matching dropped item next to it and disappear. ### Removed: - Nothing

# Changelogs: ### Added: - **Dry-Run for clears.** `/clearlag clear <items/entity/all> --preview` shows what a clear would remove without removing anything. You get the total, split into items and entities, a ranking of the most common types and a breakdown per world. It uses the exact same rules as a real clear, so exclusions, plugin hooks, WorldGuard regions, death-item protection, mob stacking and per-world profiles all behave identically. `--dry-run` and `-p` work as well. - **New permission** `clearlag.preview` lets staff run the preview without giving them the right to actually clear. - **Skip-If-Empty.** New option `auto-clear.skip-if-empty`. When there is nothing worth clearing, the countdown broadcasts and the clear itself are skipped. No more "Clearing in 60 seconds..." followed by "0 entities have been removed" on a quiet server. You can set how many entities count as worthwhile (`min-entities`) and skip the countdown and the clear independently. - **Villager / AI Throttle.** New section `villager-optimization`. Turns off the AI of villagers while no player is within the configured radius, and turns it back on the moment somebody comes close, right-clicks the villager or hits it. Villagers are the most expensive vanilla mob to tick, and since they must never be removed, this is the only way to get that time back. Other pathfinding-heavy mob types can be added to the list. Frozen mobs are tracked and always restored on enable, reload and shutdown, so nothing stays frozen. Mobs that were disabled by an operator or another plugin are never touched. Note: while frozen, a villager does not restock trades and does not walk to its bed, so keep the radius large enough for your trading halls. - **Anti-Crash Item Limits.** New section `anti-crash-items`. Blocks items with metadata large enough to crash a client or stall the server: oversized display names, huge amounts of lore, extreme enchantment levels, books with absurd page counts or page lengths, shulker boxes nested inside each other, and items whose total data size is far beyond anything legitimate. Checked when an item is dropped, renamed in an anvil, or signed as a book. Three modes: `strip` (trim and keep the item), `cancel` (block it) and `log-only` (only report, change nothing) so you can see what your server would catch before enforcing anything. Staff with `clearlag.anticrash.alert` get notified, rate-limited. - **Performance History.** New section `metrics-history` plus the command `/clearlag history <30m/24h/7d>`. TPS, MSPT, CPU, RAM, entity, item, chunk and player counts are written to a local database and kept for a configurable number of days. The command shows averages, lowest TPS, peaks, the worst period in the window and a coloured trend line, so "was the server laggy last night?" can finally be answered. New permission `clearlag.history`. The database driver is downloaded by the server automatically. If that fails, only this one feature switches itself off with a warning. ### Fixed: - Chunk scans no longer freeze the server for a moment. `/clearlag chunkfinder` and the Auto-Unload task used to walk every loaded chunk within a single tick, which on a large server caused exactly the lag spike Auto-Unload is meant to prevent. The scan is now spread over several ticks with a configurable budget (new section `chunk-scan`). Set `chunk-scan.time-sliced: false` to get the old behaviour back. - `/clearlag chunkfinder` now also shows how many items and how many mobs are in each chunk, so you can tell at a glance whether a hot chunk is a dropped-item pile or a mob farm. - `/clearlag clear` with an invalid type now shows the correct usage instead of silently doing nothing and reporting "0 entities removed". ### Removed: - Nothing removed in this version.

# Changelogs: ### Added: - Nothing new in this release. ### Fixed: - Item merging removed dropped items silently. When two stacks of the same item were merged, the absorbed one was deleted without announcing it, so other plugins were never told and could not prevent it, and nothing about it appeared in the debug log. It now uses the same removal path as every other feature and is reported as item merging. - The debug log can now be used to rule the plugin out. With that last gap closed, every entity ClearLag deletes is written to the console while debug mode is on, without exception. If something disappears from your world and no removal line appears for it, ClearLag was not the cause — which makes it far quicker to tell whether a missing mob or item is down to this plugin, another plugin, or your server settings. ### Removed: - Nothing removed in this release.

# Changelogs: ### aAdded: - Every entity ClearLag deletes is now written to the console while debug mode is on, together with the feature that caused it — scheduled clear, manual clear, kill mobs, AI-Optimization, mob spawn limiter, mob stacking, projectile limiter or nuke — plus the entity type, its custom name and its coordinates. Until now the debug output only ever reported what was kept, so a report of "ClearLag removed my mob" could neither be confirmed nor ruled out. If something disappears and no removal line appears for it, ClearLag was not the cause. - Dropped items are now reported with their actual item type instead of just "item", so they can be matched directly against the excluded items list. - The reason a mob was spared is now named in the log: whether it survived because it has a custom name, because it is breedable, or because it carries the exclusion tag. ### Fixed: - Mob stacking removed mobs without announcing it, so other plugins were never told and could not prevent the removal, and nothing about it appeared in any log. It now uses the same removal path as every other feature. - The debug line for a spared mob was easy to mistake for a removal notice — it looked like a deletion but was in fact printed the moment a mob was protected. It now states clearly that the mob was kept. - Removal messages for AI-Optimization and for item clearing were written before the removal was actually carried out, so they could report removals that never happened. - The version number reported by the plugin did not match the release it shipped in, which made it impossible to tell from the version alone whether a fix was included. ### Removed: - The separate removal messages for AI-Optimization and for item clearing. Both are replaced by the single unified removal message, which reports the same information in one place. The distance that triggered an AI-Optimization despawn is still included there.

# Changelogs: ### Added: - Debug logging `[AIOptRemove]` for AI-Optimization mob despawns including location coordinates and player distance. - Debug logging `[ClearItem]` for item auto-clear decisions (`kept (excluded)` / `removed`). ### Fixed: - Issue where entities in `auto-clear.excluded-entities` were still being removed by AI-Optimization distance despawns when `use-exclude-lists: true`. ### Removed: - Legacy `[DEBUG] Removed mob:` debug log format in favor of structured `[AIOptRemove]` logs.