Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 6 months ago
Updated 3 hours ago
All versions
1.7.0
Release
Random Optimization 1.7.03 hours ago 29
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client-side
Server-side
Client and server
Changes
Performance Optimizations
- Brought structure location optimizations and the MC-249136 mitigation to 1.21.1. Both supported versions can now exclude candidate chunks that cannot possibly generate the target structure before reading chunk storage, significantly reducing blocking scans caused by locating rare structures.
- Expanded resource pack indexing: In addition to ZIP archives, it now covers directory/Path-based resource packs, Forge/NeoForge mod resources, and vanilla resources.
- Reduced repetitive ZIP scans, directory traversals, file existence checks, and missing directory exceptions during resource reloads.
optimize_pack_lookupnow uniformly controls the indexing of ZIP archives, Path resource packs, and vanilla resources; modifying it still requires a game restart.
Compatibility
- Fixed a crash with FancyMenu: Correctly handles its
LinkFileSystemresource paths and file system root directories, safely falling back to the vanilla implementation when indexing fails on non-standard paths. - Fixed resource pack root path enumeration errors, ensuring root-level resources and namespaces can be correctly discovered.
- Automatically disables overlapping Mixins in Shipwreck Fix, lazyyyyy, and Boat Break Fix when the corresponding features are enabled; it will not interfere with these mods if the related features in Random Optimization are disabled.
- The expanded resource pack indexing continues to automatically coordinate with overlapping optimizations in Quick Pack and ModernFix.
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:Mjoo9rPv:vH7a2upA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Mjoo9rPv:vH7a2upA"
}

