Links
Tags
Creators
Details
All versions
0.1.0
Alpha
Iridium 0.1.04 months ago 2,587
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Changes
Iridium 0.1.0 — Initial Release
First release of Iridium — an optimization mod for Minecraft 1.21.1 (Fabric).
What this mod does
- Entity Culling — entities outside the camera frustum are skipped during rendering
- Particle Culling — particles outside the frustum are ignored; simultaneous particle cap enforced
- Block Entity Culling — chests, furnaces and other block entities outside the frustum are skipped
- Animation Culling — entity animations outside the frustum are paused
- Nametag Cache — nametag text cached per frame (reduces string allocation)
- Dynamic FPS — minimized/unfocused window drops to ~5 FPS (~90% CPU/GPU savings)
- Hopper Throttle — empty hoppers check less frequently
- Explosion Ray Cache — explosion ray calculations cached (reduces TNT lag spikes)
- Random Tick Throttle — random ticks outside active player radius are reduced
Compatibility
Automatically detects installed mods and disables duplicate features to prevent conflicts:
- Sodium — disables conflicting render mixins; culling features remain active
- EntityCulling (tr7zw) — disables Iridium's entity/block entity culling when detected
- MoreCulling — disables Iridium's particle and block entity culling when detected
- ImmediatelyFast — disables Iridium's animation culling when detected
- Dynamic FPS (juliand665) — disables Iridium's Dynamic FPS when detected
- Lithium / FerriteCore / ModernFix — fully compatible, no conflicts
Notes
- All optimizations are optional and configurable via the ModMenu settings screen
- No visual quality is sacrificed — culling applies only outside the camera frustum
- Zero telemetry, zero network calls
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:uPR4WJVc:HksnGesr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uPR4WJVc:HksnGesr"
}

