1.0.0.3-GV-333-CL1
Compatibility
Changes
🚀 EpicClearLag Plugin – Features Overview
⚡ Core Features
Automatic Item Clearing
Removes dropped items every set interval (default: every 6 minutes).
Sends warning messages to players before clearing (e.g., "Auto clear starting in %time% seconds!").
Fully configurable timing and messages in config.yml.
Entity Clearing
Removes unneeded mobs/entities to reduce lag.
Supports protected mobs list (certain entities never get cleared).
Skips certain blocks/entities to protect farms & important builds.
TPS Monitor
Constantly monitors server TPS (Ticks Per Second).
If TPS drops below a configured threshold, extra clearing can happen automatically.
🛠️ Admin Commands
/clearlag
Instantly clears all dropped items/entities (manual trigger).
Sends feedback to all players.
/clearlag reload
Reloads the plugin configuration without restarting the server.
/clearlag tps
Displays current server TPS.
🔔 Messaging System
Broadcast Messages
Sends countdown messages before clearing starts (e.g., 60s, 30s, 10s).
Sends confirmation message after clearing is complete (e.g., "Cleared %items% items and %entities% entities!").
Fully customizable messages in config.yml.
Placeholder Support
%time% → Remaining time until clear.
%items% → Number of items removed.
%entities% → Number of entities removed.
📂 Configurable Settings (config.yml)
Interval time for auto-clear.
Entities/items to protect from clearing.
Warning intervals before clearing.
Customizable messages.
TPS threshold for lag-based clearing.
🔧 Technical
Supports Paper/Spigot 1.17 → Latest (including 1.21.x).
- Lightweight & optimized – minimal performance impact.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Uy8FooXi:HQyDIb5H"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Uy8FooXi:HQyDIb5H"
}

