Tags
Creators
Details
0.6.2-alpha+26.2-neoforge
Compatibility
Changes
First Slabbed builds for NeoForge on Minecraft 26.2 and 26.3, one jar each from the same source. They carry the full 0.6 feature set of the Fabric 26.2/26.3 line: placement heights are recorded where you aim and kept for good, lowered slabs support the same objects, pistons carry stored heights, rails slope to meet their neighbours, fence posts meet a nearby slab ceiling, hung decorations keep their seat, the settings screen and the two height-nudge key bindings.
The 26.2 jar needs NeoForge 26.2.0.88 or newer; the 26.3 jar needs NeoForge 26.3.0.48-beta or newer. Both run on Java 25. No Fabric API or Forgified Fabric API. Cushions (26.3 content) rest on lowered blocks on the 26.3 jar.
Differences on NeoForge:
- Lowered blocks are drawn through NeoForge's own block-model hooks rather than the Fabric renderer API. The result is the same geometry; mods that replace the chunk renderer (Sodium) have not been checked on this build.
- The settings screen opens from the mod list's config button as well as
/slabdy settings. - Climbing a lowered scaffolding's drawn volume goes through NeoForge's scaffolding hook.
- Slabbed must be installed on both the client and the server on NeoForge (its synced chunk and entity data are registered as required attachment types).
- The two manual height-nudge keys do nothing on a server that does not run Slabbed.
- No Sable or Relatively Placed Blocks compatibility on these builds yet (the Fabric 26.x line has none either).
For Minecraft 26.2 (NeoForge 26.2.0.88 or newer) and 26.3 (NeoForge 26.3.0.48-beta or newer), Java 25. No Fabric API needed.
This is an alpha. If anything misbehaves, please open a report at https://github.com/peetsamods/slabbed/issues with your game version, loader and Slabbed version.
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:F5GAIMvI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5nraCxl9:F5GAIMvI"
}

