Tags
Creators
Details
Licensed ARR
Published 6 years ago
Updated 5 days ago
All versions
17.0.0-beta.6
Release
The Checkpoint Update (Fabric/NeoForge)5 days ago 2,408
Compatibility
Minecraft: Java Edition
26.1.x
Platforms
Fabric
NeoForge
Supported environments
Client-side
Changes
Changelog
- Added Vanilla support for Smart Occlusion and Safe Distant Entities. Enjoy!
- Removed the Safe Distant Entities option since the option is always safe now
- Ok Zoomer will migrate your config file automatically until The Rebirth Update: Part 3
- Fixed flickering when using Smart Occlusion in long distances (including the Longview-dependent default of 128x maximum zoom)
- Fixed massive memory usage caused by a bad interaction between Ok Zoomer's See Distant Entities feature and Very Many Players' Use Optimized Entity Tracking feature
- Ok Zoomer will ask for VMP to disable said optimization. The developer has acknowledged the optimization's tradeoff of consuming more RAM in exchange of extra performance, and considering VMP's actual target (servers with many players) and the fact Ok Zoomer cannot work around the limitation of VMP not handling high tracked entity distances well, I consider disabling this optimization to be the best way forward
- Updated See Distant Entities's distance multipliers to be less overkill when it comes to entities
- Cleaned up the codebase massively
- Fixed zoom overlays being zoomed in if Persistent Interface is disabled
- Fixed scroll transitions not working if either the start or end transitions are instant
- Updated to Wrench Wrapper 0.9.3, restoring smaller JAR files
- Optimized assets using oxipng
- Removed mentions of Sodium in the config options since it's no longer relevant here
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:aXf2OSFU:ycdBK0pX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aXf2OSFU:ycdBK0pX"
}

