1.1.0
Compatibility
Required content
Changes
[1.1.0] – August 24, 2026
More precise measurements, more reliable results.
Note: Scores from version 1.0.0 cannot be compared with results from version 1.1.0. The results will be measured differently and at a different location. Please treat old data files as separate files. Address the series.
New
- "Worst Tick" column in the chat and results file: the TPS (transactions per second) of the slowest individual Ticks. This replaces "Min TPS," which was essentially always at the average and therefore nothing indicated.
/tntmarkrequires OP (Operator) permissions on the server (Level 2). This feature is disabled in single-player. The host can use all commands without restrictions, even without cheats enabled. New players need a robust and well-designed online environment.
Modified
- The benchmark now runs at a height of 250 blocks, where TNT is represented as a compact cube. It no longer directly impacts the player; instead, it's positioned above the game area. The first wave created a crater, which was the point of origin for all subsequent waves. These factors distorted the results and made them dependent on the starting point.
- We are now only measuring the time window around the explosion itself, rather than... The entire ignition phase. This results in the spark plugs becoming noticeably more visible.
- Large waves completely ignite simultaneously. Previously, explosions occurred around 30,000 TNT was used in the initial tests before the final deployment.
- Fewer side effects globally. During a run, block drops disabled; TNT, items, and falling blocks in the benchmark area will be reset after each Neat and tidy.
Resolved
- "Benchmark is already running!" after a major change. The world was in the middle of After leaving Lauf, they were unable to establish a new benchmark.
- Settings are correctly reset. GameRules and Render Distance following a period where performance was based on standardized values, rather than previous performance.
- License is consistent WITH – the
LICENSEfile still used CC0.
Please provide the text you would like me to translate.
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:Dfl9cuzX:524vh6fN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Dfl9cuzX:524vh6fN"
}

