Links
Tags
Creators
Details
0.6.4-alpha+26.1.2
Compatibility
Changes
Direction
Next: session 4 of the walkability cache — replace vanilla's per-node
getBlockState calls inside PathFinder with reads from the Rust
section store. The parity gate from 0.6.4-alpha gates that swap.
[0.6.4-alpha] — 2026-05-17
Added
-
Dispatcher latency probe (
/ferrite probe dispatcher on, default off). Captures queue-wait per priority lane and per-task wall time on the worldgen and light executors. Measurement on fast-flight load: task body is 4-10x the dispatcher's worst tail, so the dispatcher is not the bottleneck. Probe stays in tree for re-measurement under other workloads. -
Walkability cache infrastructure (sessions 1-3). Block-kind cache for the pathfinding subsystem: Rust section store (4096-cell flat arrays, evict on block change), JNI surface, Java bridge with 18-category block classifier, lazy section fill on path requests, and a parity gate that validates cache predictions against vanilla's node evaluator. Parity result: 6 critical mismatches out of hundreds of nodes checked per session (all structural 2-block-model limits). The performance swap (session 4) is the follow-on.
Removed
- Dead
SurfaceValidator.onServerTickmethod and its fields (zero callers).
Internal
- Threading audit (
docs/COMPATIBILITY.md): three-tier safety classification of every non-final static field on worldgen and entity-tick paths, plus Rust-side concurrency posture (zero unsafe statics, zero plain cells). - Doc index (
docs/DOC_MAP.md) and various doc updates across JOURNEY, FUTURE_PLANS, and per-subsystem writeups.
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:7IPSC6tn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:c2DHmFvV:7IPSC6tn"
}

