GPWildernessCleaner reduces lag from entity buildup on survival servers that use GriefPrevention. It runs on a timer and removes selected entity types only outside GP claims (wilderness). Anything inside a player or admin claim is left alone.

Unlike generic clear-lag plugins, this plugin is built around claim boundaries: it uses GriefPrevention’s claim data so farms, bases, villagers, and builds inside claims stay safe while wilderness areas are trimmed.

Why use it?

• Large wilderness farms and mob caps can push servers to thousands of passive mobs and dropped items.
• Full-world entity clears are risky on GP servers — they can wipe animals in unclaimed areas players rely on, or conflict with claim logic.
• GPWildernessCleaner targets wilderness only, with configurable filters and per-chunk caps so land and aquatic mobs don’t disappear entirely (helping natural respawn feel better).

Removed in wilderness (when enabled):

• Dropped items
• Hostile mobs
• Land passive mobs (with optional per-chunk cap)
• Aquatic mobs — fish, squid, dolphins, etc. (with optional per-chunk cap)
• Projectiles, XP orbs, area effect clouds, falling blocks, primed TNT
• Extra entity types via config list

Never removed (defaults):

• Players
• Villagers and wandering traders
• Tamed animals
• Named or scoreboard-tagged mobs
• Armor stands, item frames, paintings
• Anything inside a GriefPrevention claim (when claim respect is enabled)

Vehicles are off by default; you can enable them if you want.

Per-chunk caps (passive & aquatic)

Instead of deleting every passive or fish in a chunk, you can keep a small number per wilderness chunk and only remove the excess. That cuts lag while leaving some animals for spawning. Set caps to 0 for full wipe in that category (older, harsher behavior).

Scheduling & announcements

• Automatic runs every N minutes (default: 10)
• Optional countdown broadcasts before each run
• Optional summary after auto-runs (removed count, claim-skipped count, kept-by-cap count)
• Optional run on server startup

Commands and Description

• /gpwclean or /gpwclean status

Show enabled state, interval, time until next run, chunk caps

• /gpwclean run

Run cleanup immediately

• /gpwclean reload

Reload config

Permission: gpwildernesscleaner.admin (default: OP)

Safety

If GriefPrevention is required by config but not loaded, cleanup does not run — avoids clearing the whole world when claim detection isn’t available.

PlugMan-friendly: scheduled tasks are cancelled on disable so reloads don’t stack duplicate timers.

Requirements

Server: Paper (or compatible fork) 1.21+ (built against 1.21.11 API; Java 21) Soft dependency: GriefPrevention — strongly recommended; claim checks depend on it

Installation

• Drop .jar in your server’s plugins/ folder.
• Ensure GriefPrevention is installed.
• Start or restart the server.
• Edit plugins/GPWildernessCleaner/config.yml as needed.
• Use /gpwclean reload after config changes.