Tags
Creators
Details
1.0.0+26.2
Compatibility
Required content
Changes
I See Your Chunks for Fabric 26.2
A Fabric mod that renders distant players standing on real terrain, far past render distance, instead of floating in the void. The server streams the already-resident chunks around each viewed player; the client accepts them and hands them to Voxy, which draws them through its own far renderer.
Server:
- FarChunkStreamer: send-only streaming of already-loaded chunks around revealed players, chosen nearest-first up to a configurable count and capped at the server's render distance, plus a one-chunk neighbour halo so Voxy's neighbour-dependent mesher can build the visible edge.
- Entity tracking mixins lift vanilla's distance/chunk caps per viewer: always for players and their (nested) mount chains, and for loose mobs only while they stand on a chunk that actually renders for that viewer.
- ChunkHolder.broadcast forwarding keeps streamed far chunks live.
- VisibilityFilter: spectator/invisible/vanish (melius-vanish) exclusions. Client:
- Widens the ClientChunkCache storage radius to accept far chunks, and re-applies it on config change so slider edits take effect without a reload.
- Hands each arriving far chunk straight to Voxy's VoxelIngestService, since Voxy otherwise only ingests chunks on unload and streamed chunks never unload.
- Entity render overrides that respect the frustum; mounts of a shown player render with it regardless of the distant-mob toggle or terrain.
Networking: opt-in ClientHelloPayload handshake with a ServerAckPayload reply carrying the server's render distance, so the client's terrain slider and chunk storage track what the server can actually deliver. Config + Mod Menu screen; en_us/fr_fr. Voxy required on clients (recommended, enforced with a runtime warning); dedicated servers neither need nor load it. Versioned single-source-set layout (26.2/src + 26.2/fabric). AGPL-3.0.
Optional dependencies
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:IM0DFLOO:BQKkrc1d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IM0DFLOO:BQKkrc1d"
}

