⚡ ServerBooster

This release adds a new module for clearing abandoned ground items, along with a manual cleanup button, and fixes the Restore Vanilla Mob AI action.

New module: Ground Item Cleaner

Removes dropped items that have been lying on the ground for longer than an age you choose, so forgotten drops stop costing entity ticks and network traffic.

It ships disabled. Deleting player items is destructive, so turning it on is your decision.

What it can touch — and what it can never touch

Only dropped items. Armour stands, minecarts, item frames, paintings, boats and mobs are different entity types, so they cannot be selected by this module no matter how it is configured. That is not a list you could get wrong; it is simply what the module looks at.

On top of that, several protections are on by default:

Items nobody can pick up are spared. Plugins use these for decorative and display entities, and deleting them would break those plugins. Invulnerable items are spared, since plugins use that flag to mark special drops. Renamed items are spared. This looks at the name carried by the item itself — the one that stays with it after you pick it up — not the floating label shown over a drop. A blacklist of valuables ships filled in: netherite gear and blocks, elytra, totems, dragon egg, beacon, nether star, enchanted golden apples and shulker boxes. An optional whitelist, so you can instead clean only the materials you list. An optional strict mode that limits cleanup to piles merged by the Item Holograms module and ignores everything else. Why this exists when Minecraft already despawns items

Vanilla despawns an item once its own timer runs out, but merging a pile resets that timer. A spot where players keep dropping things can therefore hold a stack alive indefinitely, and it never ages out on its own.

So this module keeps its own record of how long an item has really been on the ground. That record survives chunk unloads and server restarts, and merging cannot reset it.

Fully configurable

Minimum age, sweep interval, worlds, protections, blacklist and whitelist, a cap on how many items a single sweep may remove (so cleanup never becomes its own lag spike), an optional countdown warning broadcast before automatic sweeps, an optional result announcement, and console logging.

New: manual cleanup

A Clean Ground Items button now sits in the module menu, next to Restore Vanilla Mob AI. It works even while the module is switched off, because clearing lag on demand is a different need from running cleanup on a timer. It always applies the same age threshold and protections, so a click can never wipe items a player just dropped.

The button also shows live counts before you press it: how many items are on the ground, how many are old enough to go, how many are still too young, and how many are protected.

There is a matching /sb clean command for console and scripts, guarded by the new serverbooster.clean permission (default: op).

Cleanup always explains itself. Instead of a bare "nothing was removed", every cleanup reports how many items were scanned, how many were too young, how many were protected, and how many were filtered out by your lists — so you can see at a glance why something stayed.

Fixed: Restore Vanilla Mob AI did nothing

Reported by server owners: the restore action ran without errors but left mobs frozen, and the only thing that worked was clearing the AI flag by hand with a vanilla command.

Minecraft has two independent switches that can disable a mob's AI. ServerBooster was clearing one of them and leaving the other untouched, so any mob holding the second flag stayed frozen no matter how many times it was restored. Both are now cleared, independently, so one failing cannot block the other.

As before, this only ever affects mobs ServerBooster itself froze. Mobs held without AI by other plugins — NPCs, bosses, quest mobs — are never touched.

Compatibility

Paper, Spigot and Purpur from 1.17 through 26.x Java 17+ The Ground Item Cleaner reports itself as unavailable on Folia rather than running unsafely Config comments are preserved when toggling modules from the menu The Web Dashboard remains EXPERIMENTAL Upgrading

Drop in the new JAR. config_item_cleaner.yml is created on first start with the module disabled, so nothing changes until you switch it on.

One thing worth knowing: editing a config file by hand does not take effect until you run /sb reload or toggle that module in the menu. If a change seems to do nothing, that is usually why.