2.0.1
Compatibility
Changes
OptimizationForLB v2.0.1
OptimizationForLB v2.0.1 is an active, all-in-one performance optimization engine for Paper, Purpur, and modern Minecraft server software. Moving far beyond simple warnings, it actively manages server workload with automated mob stacking, redstone clock throttling, smart chunk CPU controls, and emergency TPS recovery sequences.
What is New in v2.0.1
- Active Entity Stacking: Merges nearby mobs of the same type into single entities with clear stack labels (e.g.
5x Zombie), reducing entity tick loops and AI CPU overhead. - Redstone Clock Throttler: Automatically throttles abusive high-frequency redstone clocks and lag machines without disrupting legitimate player contraptions.
- Smart Chunk CPU Management: Automatically unloads unattended chunks outside player view buffers to eliminate idle chunk CPU ticking.
- Automated TPS Auto-Fix: Automatically executes an emergency recovery sequence when TPS drops to or below 15.0 (clears items, stacks mobs, purges chunks, and runs GC).
- New Commands: Added
/opt autofixto trigger emergency recovery on demand and/opt stackfor manual mob stacking passes.
Complete Feature Set
1. Active Performance Optimizers
- Mob Stacker: Groups nearby entities by type up to configurable stack sizes. Bosses and player-named entities are protected.
- Redstone Rate Limiter: Limits update rates per chunk per second to neutralize rapid clock lag.
- Smart Chunk Unloader: Frees memory and halts tick processing for unoccupied chunks.
- Emergency Auto-Fix: Recovers server TPS automatically during severe lag events.
- Ground Item Cleaner: Periodic dropped item sweeps with customizable warning countdowns.
- Aggressive RAM Trimmer: Frees clogged heap memory on demand or automatically.
2. Monitoring and Auditing
- 1-Minute Health Reports: Audits TPS, RAM, Mobs, Items, Chunks, and overall Server Health Score every 60 seconds.
- Smart TPS Alerts: Alerts when TPS drops below 17.0, with recurring warnings at or below 15.0.
- Player Latency Monitoring: Detects players with high ping and displays connection quality badges.
- Visual Status HUD: Clean progress bar HUD for TPS and RAM usage via
/opt status.
Commands & Permissions
/opt status- Display visual server TPS, RAM HUD, and ping (Permission:optimizationforlb.admin)/opt autofix- Trigger emergency TPS recovery sequence (Permission:optimizationforlb.admin)/opt stack- Trigger immediate mob stacking pass (Permission:optimizationforlb.admin)/opt health- Broadcast 1-minute server health summary report (Permission:optimizationforlb.admin)/opt clearitems- Clear dropped items across all worlds (Permission:optimizationforlb.admin)/opt purgechunks- Unload inactive chunks to free memory (Permission:optimizationforlb.admin)/opt trimram- Trigger aggressive RAM reduction (Permission:optimizationforlb.admin)/opt gc- Trigger JVM Garbage Collection pass (Permission:optimizationforlb.admin)/opt ping- Check player connection quality badge (Permission:optimizationforlb.admin)/opt reload- Reload v2.0.1 configuration and timers (Permission:optimizationforlb.admin)/opt help- Display command help list (Permission:optimizationforlb.admin)
Configuration Example (config.yml)
plugin:
prefix: "&8[&cOptimizationForLB&8] "
alerts:
display-mode: "CHAT" # Options: CHAT, ACTION_BAR, BOTH
sound-effects:
enabled: true
sound: "BLOCK_NOTE_BLOCK_BASS"
entity-stacker:
enabled: true
interval-seconds: 15
search-radius-blocks: 6.0
max-stack-size: 50
name-format: "&e{count}x &c{type}"
redstone-limiter:
enabled: true
max-updates-per-second-per-chunk: 150
notify-admins: true
smart-chunk-manager:
enabled: true
interval-seconds: 30
player-buffer-radius-chunks: 3
auto-fix:
enabled: true
trigger-tps: 15.0
cooldown-seconds: 60
actions:
clear-ground-items: true
stack-entities-pass: true
purge-inactive-chunks: true
trigger-jvm-gc: true
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:5qcwyLB4:xqvI4D8d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5qcwyLB4:xqvI4D8d"
}

