Tags
Creators
Details
5.0
Compatibility
Changes
Changelog
26.2.0
Rebuilt the whole thing from scratch. Decompiled the old jar, fixed a bunch of bugs, and turned it into a proper multi-platform project. Now works from 1.20.1 all the way up to 26.2.
New stuff
- Works on 1.20.1 through 26.2+
- Fabric version (finally). Two jars because Mojang removed obfuscation in 26.1, so old and new versions can't share one:
SmartOptimizer-Fabric-26.2.0.jarfor 26.1+SmartOptimizer-Fabric-1.20.1-26.2.0.jarfor 1.20.1–1.21.11
- Folia support (uses the region scheduler when it detects Folia, falls back to the normal Bukkit scheduler otherwise)
- Tab completion on the commands
- Config gets validated on load now — if you put something dumb in there it clamps it to a sane value instead of breaking
- TPS fallback for Spigot (uses Paper's TPS API when it's there, reads tick times when it isn't)
Bug fixes (stuff that was broken in 26.1.2)
- Mob AI check was using
distance()which does a square root every call — switched todistanceSquared(), way faster - Chunk unloading straight up never worked for worlds that hadn't had a player in them yet. Dead code. Fixed
- Spawn chunk was being recalculated for every single chunk (O(n²) for no reason) — now it's once per pass
- Crashed if the command wasn't registered — added a null check
- Saving the config wiped out all your comments — doesn't anymore
Other
- Author is now endermanking_
- Paper jar is built against the 1.20.1 API targeting Java 17, so it runs everywhere from 1.20.1 to 26.2
- Fabric 26.2 jar: MC 26.2, loader 0.19.5, Fabric API 0.159.0+26.2, Java 25
- Fabric 1.20.1 jar: MC 1.20.1, yarn 1.20.1+build.10, loader 0.15.11, Fabric API 0.92.2+1.20.1, Java 17
What runs what
| Jar | Minecraft | Platform | Java |
|---|---|---|---|
| Paper | 1.20.1 – 26.2+ | Paper, Folia, Purpur, Pufferfish, Spigot, Bukkit | 17+ |
| Fabric | 26.1 – 26.2+ | Fabric Loader 0.19+ + Fabric API | 25+ |
| Fabric 1.20.1 | 1.20.1 – 1.21.11 | Fabric Loader 0.15+ + Fabric API | 17+ |
26.1.2
Old Paper-only version. This was before the rebuild.
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:lEJHtKfF:elMBsPca"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lEJHtKfF:elMBsPca"
}

