Tags
Creators
Details
0.5.0-beta.8
Compatibility
Changes
Slabbed 0.5.0-beta.8 — Minecraft 1.21.11 Fabric
Fixed
- Fixed a client crash that could occur while Minecraft rebuilt chunk meshes near a renderer-region boundary. Beta.7 used a development-only class name when recognizing the bounded renderer view, so production could rethrow an expected out-of-region lookup instead of ending the scan safely. Beta.8 uses a mapping-safe renderer check.
Verification
- Reproduced and regression-tested the production mapping failure.
- Tested visible rain, repeated short-grass mesh rebuilds, and chunk unload/reload without recurrence.
- Rechecked and closed the already-fixed fence-gate visual report (#12) and Terrain Slabs log-carrier report (#22).
Rain appears to have triggered or coincided with the rebuild that exposed #35; it was not the direct cause. The reported blue flashes and 0-1 FPS behavior were not independently proven and should be re-reported with a fresh log if they remain after beta.8.
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:5nraCxl9:ZC0xIDuA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5nraCxl9:ZC0xIDuA"
}

