All versions
10.2.0
Release
FramedBlocks 10.2.02 years ago 1,347
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
- Switch intangibility from configurable item to custom craftable item
- Add support for connected textures on the tinted glass face of one-way windows
- Forward infiniburn behaviour from camos on full faces
- Fix culling and texture connection behaviour on masonry corner
- Add Framed (Inner) Corner Slope Edge
- Add Framed Elevated (Inner) Corner Slope Edge
- Add Framed Elevated Double (Inner) Corner Slope Edge
- Add Framed Stacked (Inner) Corner Slope Edge
- Add Framed (Inner) Threeway Corner Slope Edge
- Use a more suitable sound type for fluid camos
- Fix framed blocks becoming invisible when mods forget to specify cull-faces in their models
- Improve occlusion behaviour between block camos with special occlusion checks
- Fix floor board and horizontal pane letting rain pass through
- Fix crash when the EMI plugin is loaded too early
- Fix camos on item models not getting tint applied
- Fix fluid texture mapping on fluid camos where flowing and still texture are identical
- Allow interacting with buttons and levers without camo when holding a framed block
- Make the one-way window pretend to be its camo in Jade when looking at non-window faces
- Fix occlusion on compound slope slabs
- Allow flipping slope source face on horizontal slopes and half slopes
- Prevent use of framed blocks with camo in the framing saw
- Add Framed Tank
- Add JEI integration for camo application recipe
- Add Framed Chain
- Fix various consistency issues with the framed chest
- Add double chest support to the framed chest
- Fix crash when placing framed fences or panes with DiagonalFences or DiagonalWindows installed
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:wbgfS34j:W3F9n96N"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wbgfS34j:W3F9n96N"
}

