Links
Tags
Creators
Details
All versions
0.7.5-alpha
Alpha
0.7.5-alpha4 days ago 810
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client and server
Changes
[0.7.5-alpha] - 2026-10-23
Added
- Ore placement kernel, on by default. Same blocks and random
draws as vanilla, 9% less ore time on a 24-core desktop and 15% on a
4-core server (pregen about 6% sooner). An oracle replays 1 in 64
veins; a full check of 1.5M veins in the overworld and nether found
no differences. Off:
/ferrite ore offor-Dferrite.orekernel=off. Counters:/ferrite ore report. Odd ore in new chunks? Open an issue with seed, coordinates and the report line. - Entity tracker probe.
/ferrite probe tracker on|report|resetreports tracker cost in ms per tick. Off by default. With 1021 zombies on a 4-core server: 0.45 to 0.66 ms/tick, under 3%. - Surface rule compiler, on by default. The 26.3 material rule
tree is compiled into one class per chunk shape, still calling the
vanilla rules in vanilla order, so datapacks work as written.
Surface time drops 16-27% on a 24-core desktop and 18-33% on a
4-core server; pregens finish 3-4% sooner. An oracle reruns vanilla
on 1 in 64 chunks and keeps vanilla blocks on any mismatch; a full
check of 240M blocks over five world types and three dimensions
found none. Steps aside when another mod changes the material rule
classes. Off:
/ferrite rules offor-Dferrite.rules=off; force on:-Dferrite.rules=on. Counters:/ferrite rules report. Odd surface blocks in new chunks? Open an issue with seed, coordinates and the report line. - Ore kernel and rule compiler together. Pregens finish about 8% sooner on a 4-core server. On a 24-core desktop wall time stays flat because workers already sit partly idle, but worker CPU drops 9%. Both oracles ran at 1 in 64 and found no mismatches.
Fixed
- Biome validator counts exact ties as ties. Over 2000 samples on 26.3 it reads 1999 pass, 1 tie, 0 fail.
- Dead toggles now say so.
/ferrite surface dispatch,/ferrite aquifer rust,/ferrite aquifer parityand/ferrite biome routereport inactive instead of success, and-Dferrite.bulkChunkDensity=truelogs a boot warning.
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:c2DHmFvV:M5T7xVKr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:c2DHmFvV:M5T7xVKr"
}

