Tags
Creators
Details
1.4.0+mc1.21.4-2026-03-27
Compatibility
Changes
PerfTriage 1.4.0
A configuration-focused update that makes PerfTriage much easier to tune on live servers.
This release adds a proper config file and moves core detection / dump parameters out of hardcoded values and into user-editable settings.
New
config/perftriage/config.json/perftriage reload/perftriage config
Configurable settings
- Trigger MSPT threshold
- Trigger consecutive ticks
- Recovery MSPT threshold
- Recovery consecutive ticks
- Auto-dump cooldown
- World scan budget
- Hotspot sample count
- Hotspot Top-N size
- Hotspot per-tick budget
- Hotspot total budget
- Text / JSON report output toggles
Why this matters PerfTriage is designed for real servers, and different servers need different sensitivity and scan budgets. This update makes the mod much more practical to deploy and tune without rebuilding the jar.
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:L2ZM4ewm:AhsKM1kb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L2ZM4ewm:AhsKM1kb"
}

