Links
Tags
Creators
Details
1.5.1-26.1
Compatibility
Required content
Changes
-
Updated to 26.1
-
Tweaked Smooth Stone Bricks texture to better mesh with Smooth Stone
-
Fixed bugs with various blocks' models
The silver lining of rewriting basically all of the model generation code was that I caught a bunch of bugs (things like top slabs not having models).
Sorry this took so long. 26.1 was probably the biggest backend update there's been in as long as I've been making mods, and it coincided with the busiest I've ever been at work. Hopefully things are smoother and I can stay more on top of updates going forward. In addition to the changes listed above, some backend world generation stuff also changed, and while I've done my best to replicate things exactly as they were under the new systems, things like the generation of fallen leaf patches or berry bushes in the Autumnal Forest might be very slightly different to how they were before. Hopefully if there are any discrepancies, they shouldn't be noticeable to a degree that impacts gameplay.
To everyone who waited for me to get this out - thank you for your patience! I know there are people hoping for 1.21.1 backports, and I haven't forgotten about those. I was just preoccupied in getting the main branch updated in what time I had for modding. I think the now-looming 26.3 update is also going to be a bit of an involved one, given the implications of the Dappled Grove, but after that, I'll try and get a backport done.
Also, I changed the numbering system - I figure Mojang doing it was as good a time as any for me to do the same, because I hadn't been happy with it for a while. Previously the first number incremented whenever Minecraft updated (with the BFB version being the second number), which ended up looking a bit silly as we got up to 9.X.X, despite BFB not being on its ninth version. So now it's just 1.[BFB major version].[BFB minor version] - [Minecraft version]. Hopefully a bit more intuitive going forward, even if jumping back to 1.X.X from 9.X.X is a bit confusing.
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:EpwT0cx1:CJ8QeWVB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EpwT0cx1:CJ8QeWVB"
}

