Tags
Creators
Details
0.6.3-alpha+26.2-26.3
Compatibility
Required content
Changes
Slabbed 0.6.3-alpha+26.2-26.3 — Minecraft 26.2 and 26.3 (Fabric)
For Minecraft 26.2 and 26.3 on Fabric. Requires Fabric API and Java 25.
- Prevent chunk generation from freezing when Lootr initializes a chest minecart during chunk loading. The cart now takes its rail height on its first normal tick. Thanks to 1unarea for the report and thread dumps.
- Make block rendering read stable copies of stored heights and placement markers, avoiding reads from chunk data while it is being changed. This addresses the attachment-read race investigated for #96, reported by rompeballer; the exact intermittent crash has not been reproduced again, so the report is not yet confirmed resolved.
- Allow trapdoors above fences and walls without treating their invisible entity barrier as occupied building space. Real overlap still blocks placement, and ordinary underside placement remains supported. Thanks to ch66w and thomashahn42-hash for the placement reports.
The exact Minecraft 26.2/Lootr combination reported by iSeoull in #105 remains unverified. The confirmed chunk-loading reproduction used Minecraft 26.3 with Lootr 1.25.42.124. No blanket resolution of #105 is claimed.
Known validation limits: the full Lithium/Lootr suite is not green. Five redstone checks also fail on the prior release; four other failures are vanilla catalog expectations affected by Lootr. These checks remain outside this patch. Rapid world replacement with queued render jobs remains unproven.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| slabbed-0.6.3-alpha+26.2-26.3-sources.jar | Sources jar | 370.76 KiB |
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:xbkgi26B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5nraCxl9:xbkgi26B"
}

