Links
Tags
Creators
Details
All versions
0.7.3-alpha+26.2
Alpha
Ferrite 0.7.3-alpha+26.22 months ago 2,745
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Changes
[0.7.3-alpha] - 2026-09-03
Added
- Chunkforce auto mode, default off. Engages forced generation
when a player sustains ~40 blocks/s;
/ferrite chunkforce auto on. Off by default: a 10-run interleaved bench at 90 blocks/s measured 8.1 missing chunks against vanilla's 0.9, worse in every pair. /ferrite arrivalmonitor,/ferrite arrival benchand/ferrite arrival suite. Counts unloaded chunks inside each view distance every 5 s (~50 us/tick at view distance 10), plus an automated flight bench.-Pferrite.autobench=x,z,speed,seconds,runsruns a suite headless./ferrite probe stagesand/ferrite pregen order. Per-stage wall timer on the chunk pipeline and a selectable pregen request order (ring, scan, diag). Diagnostics only, default off; readings are in docs/JOURNEY.md.
Fixed
- Own nametag missing in F5 with nametag mods (#15). A leftover client mixin blanked the local player display name. Removed.
Changed
- Entity query index and collider skip are now default on. Opt-in
since 0.7.0. Evidence: 10.8M oracle checks with zero mismatches, and
a 1022-zombie farm on a shared 4-core server going from 15.5 TPS to
a locked 20 TPS. Kill switches:
-Dferrite.entityquery.cache=falseand-Dferrite.entityquery.colliderskip=false. With Lithium installed the gain is smaller; the two coexist. - Lower default-config footprint (26.2.x dev build, JDK 25, jcmd;
commands in docs/PIANO_STATUS.md):
- ~4.4 MB of off-heap physics buffers no longer allocate while physics is off.
- Rust worker pool starts on first use instead of at the title screen: zero idle native threads, was 6.
- Cramming reuses its spatial hash buckets across ticks.
- Two leaks closed: parity-capture lists cleared on server stop, and the opt-in nav cache frees native memory on chunk unload.
- Monitors stop timing entities while reports are off, removing ~100k allocations/s at horde scale. No measurable mspt change on a 24-core desktop; the saving is GC pressure and slow-CPU time.
- Fabric Loader 0.19.5 in the dev and CI build. Minimum stays 0.18.4.
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:bnfACxd6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:c2DHmFvV:bnfACxd6"
}

