ServerBooster v26.1.1-HOTFIX

This patch delivers a major overhaul to the Web Monitor module, critical security hardening across the entire web stack, and targeted performance fixes identified through a full codebase audit.

Note: The Web Monitor Dashboard is currently in EXPERIMENTAL phase. It is disabled by default and must be manually enabled in web.yml. Features, endpoints, and configuration options may change in future releases without prior notice.


Web Dashboard — Complete Rewrite (EXPERIMENTAL)

• Two-tier data collection system: Fast metrics (TPS, MSPT, memory, players) update every 2 seconds. Heavy data (entity breakdown, chunk hotspots) updates every 10 seconds. This eliminates main thread impact when the dashboard is in use.
• Client-awareness gate: Data collection is completely skipped when no one is viewing the dashboard. Zero overhead when unused.

FULL CHANGELOG - https://github.com/SrCodexStudio/ServerBooster/releases

This patch delivers a major overhaul to the Web Monitor module, critical security hardening across the entire web stack, and targeted performance fixes identified through a full codebase audit.

Note: The Web Monitor Dashboard is currently in EXPERIMENTAL phase. It is disabled by default and must be manually enabled in web.yml. Features, endpoints, and configuration options may change in future releases without prior notice.


Web Dashboard — Complete Rewrite (EXPERIMENTAL)

• Two-tier data collection system: Fast metrics (TPS, MSPT, memory, players) update every 2 seconds. Heavy data (entity breakdown, chunk hotspots) updates every 10 seconds. This eliminates main thread impact when the dashboard is in use.
• Client-awareness gate: Data collection is completely skipped when no one is viewing the dashboard. Zero overhead when unused.

FULL CHANGELOG - https://github.com/SrCodexStudio/ServerBooster/releases

ServerBooster v26.1​

Full compatibility update for Minecraft's new year-based versioning, plus major stability, security, and bug fix improvements.

Minecraft 26.1.x Compatibility​

• Full support for the new version scheme — ServerBooster now correctly detects and runs on Minecraft 26.1, 26.1.1, 26.1.2, and any future 26.1.x
  hotfix releases.
• Updated NMS resolution — Internal server class lookups now handle Mojang-mapped class names used in 26.1, with automatic fallback for older
  versions.
• Supported version range: 1.17 - 26.1.x — Covers Paper and Spigot from 1.17 through the latest 26.1.x release.

FULL CHANGELOG + FREE - https://github.com/SrCodexStudio/ServerBooster/releases

Full Changelog - https://github.com/SrCodexStudio/ServerBooster/releases

Bug Fixes​

• Block Limiter off-by-one fixed — Limits now work correctly. A limit of 4 allows exactly 4 blocks, not 3. This affected all category limits (hoppers,
  chests, crafting tables, enchanting tables, etc.), custom material limits, and entity placement limits (item frames, paintings).
• Block Limiter cache poisoning fixed — Previously, after a denied placement, the count cache could store incorrect values for up to 5 seconds,
  causing additional false denials. Cache is now properly invalidated on every placement attempt.
• Block Limiter deny message now shows accurate count — The message no longer includes the temporarily placed block in its count.
• Hologram checksum migration — Items stacked before this update are now automatically migrated to the new checksum format without data loss.
  Previously, updating could reset stacked items to 1.

Full Changelog - https://github.com/SrCodexStudio/ServerBooster

Hotfix: Hopper Furnace Behavior + Stability Patches​

Hopper Optimizer Fix​

• Fixed: Hoppers below furnaces were pulling fuel and input items instead of only pulling from the output slot (vanilla behavior)
• Now correctly respects vanilla slot restrictions for all special containers:
  • Furnace / Blast Furnace / Smoker: Only pulls from output slot (slot 2)
  • Brewing Stand: Only pulls from potion slots (0-2), not fuel or ingredient slots
  • Chests, Barrels, etc: Unchanged, pulls from all slots

ServerBooster v3.0.1 [TEASER]
Major Stability & Performance Update

​

What's New in v3.0.1

Comprehensive audit of all 12 modules. 36 issues identified and fixed, including 5 critical memory leaks, 2 exploit patches, and major performance optimizations.



Critical Fixes

• Memory Leak Fixed: The lag machine detector stored direct chunk references in memory, preventing garbage collection. Servers running for hours would see steadily increasing RAM usage. Now stores only coordinates, auto-evicts after 5 minutes.
• Memory Leak Fixed: After /reload, the plugin's background task system would silently stop working. Update checker, entity processing, and other async tasks would fail. Now properly re-creates the task system on every reload.
• Performance Fixed: The VillagerOptimizer copied ALL entities in the world (items, projectiles, mobs) every 30 seconds just to find villagers. On busy servers this caused lag spikes. Now uses server-optimized villager-only lookup.
• Exploit Patched: Players could use pistons to push limited blocks to new positions, bypassing block placement limits entirely. Piston movements now update block tracking.
• Exploit Patched: Explosions (TNT, creepers) destroyed tracked blocks without updating the limiter. Explosions now properly clean up tracking data.

Performance Improvements

• ChunkBlockLimiter: 1,400x faster
  Before: Every block placement scanned 1.44 MILLION blocks.
  After: Uses tile-entity scanning + spatial index + LRU cache.
• HopperOptimizer: No more chunk scanning
  Before: Iterated ALL loaded chunks in ALL worlds every 8 ticks.
  After: Maintains a registry of hopper locations. Only visits known hoppers.
• VillagerOptimizer: Smarter player detection
  Before: Expensive entity search per villager per cycle.
  After: Player positions computed once and reused with simple distance math.
• NMS Reflection: Cached lookups
  Field lookups that ran on every entity tick are now cached at startup.
• EntityOptimizer: Respects VillagerOptimizer
  No longer accidentally re-enables AI on intentionally lobotomized villagers.

Bug Fixes

• Elytra config was never read - Typo in code meant riptide trident settings were always ignored
• /sb info showed 8/12 modules - Missing 4 modules from the status display
• maxItemsPerTransfer had no effect - Config loaded but never used in hopper logic
• Physics detector didn't reload worlds - World list was stuck from first startup
• Physics threshold was mislabeled - Comment said "nanoseconds" but code compared event counts
• Chunk key collisions - Negative coordinates could collide with positive ones
• Particles crashed on 1.20.5+ - Particle names were renamed in newer versions
• Data loss on crash - Block tracking save used unsafe file operations
• Save race condition - Auto-save could lose track of unsaved changes
• Memory leak on world unload - Tracking data stayed in RAM forever after world unload

VillagerOptimizer Improvements

• Profession-only targeting - Only affects villagers with a job (Librarian, Farmer, etc.). Normal villagers and Nitwits are ignored.
• Faster detection - First check runs 1 second after startup instead of 30 seconds.
• Timer no longer resets near players - Previously, standing near a villager would reset the stuck timer every cycle, preventing optimization. Now the timer keeps counting.

Item Stacking (HologramItemManager)

• Despawned item cleanup - Items that despawned naturally left stale data in memory. Now cleaned up every 5 minutes.

Technical Info

• Java: 17+
• Platforms: Paper, Spigot
• Versions: 1.17.x - 1.21.x

Thank you for supporting ServerBooster!
Your purchase helps keep this project alive and actively maintained.
​