
Better Tps
better-tps is an adaptive performance stabilizer for Minecraft servers (Bukkit/Spigot/Paper/Purpur 1.20+). It automatically tunes server settings in real-time to maintain a stable 20 TPS, ensuring a smooth experience for players even during high-load
1.6.0
Compatibility
Changes
β‘ Better TPS v1.6.0 β Chunk Lag Profiler, Action Bar HUD & Memory Telemetry
π What's New & Enhanced in v1.6.0:
- πΊοΈ Heaviest Chunks Lag Profiler:
- Implemented
/bettertps chunks(alias/bettertps topchunks): scans loaded chunks across all active worlds and scores tile entities, hoppers, monsters, animals, and item drops to identify exact high-strain chunks with block coordinates.
- Implemented
- π Real-Time Action Bar Performance HUD:
- Added
/tps hud(alias/bettertps hud): displays real-time live ticker on player action bar (TPS,MSPT,RAM usage, and activetuning profile).
- Added
- π§ JVM Memory & Telemetry Monitor:
- Added
/tps ram(alias/bettertps ram): displays visual RAM usage progress bar, allocated memory, CPU threads, and Java runtime specifications. - Added
/bettertps gcfor administrators to safely trigger JVM garbage collection and report reclaimed heap memory.
- Added
- π¨ Proactive Lag Spike Alerts with Sound:
- Automatically notifies online staff with audio cues when TPS drops below threshold (
below-tps: 18.0/above-mspt: 60.0).
- Automatically notifies online staff with audio cues when TPS drops below threshold (
- π§© PlaceholderAPI Expansion Hook:
- Added soft-dependency integration for PlaceholderAPI:
%bettertps_tps%%bettertps_tps_colored%%bettertps_mspt%%bettertps_mspt_colored%%bettertps_profile%%bettertps_health%%bettertps_ram_used%%bettertps_ram_max%%bettertps_ram_percent%%bettertps_auto%%bettertps_hud%
- Added soft-dependency integration for PlaceholderAPI:
- β‘ Paper 26.3 & Folia Live Verified:
- Verified on live Paper 26.3 test container (Java 25 LTS) with zero errors.
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:XC7ZA3cV:Gy3JKeX0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XC7ZA3cV:Gy3JKeX0"
}
