
Extended block shapes
This mod adds more shapes for many vanilla blocks, including shapes that do not exist in vanilla Minecraft, like vertical slabs, vertical stairs or quarter pieces. Most of the blocks have vanilla behaviours, like what their base block behaves.
Links
Tags
Creators
Details
3.0.0-fabric-1.21.1
Compatibility
Required content
Changes
- The mod no longer depends on Better Runtime Resource Pack (BRRP) mod.
- Fixed the issues that logs may lack
#buttonstag. - Fixed the issue that some wooden fence gates lack
#fence_gatestag. - Buttons of pumpkin and melon will no longer have
#wooden_buttonstag. - Pressure plates of pumpkin and melon will no longer have
#wooden_pressure_platestag. - Fixed the issue that
#pressure_plateslack its corresponding item tag. - Removed the feature in the configuration screen to avoid some specific recipes, and added a built-in datapack to avoid recipe conflicts, which is enabled by default and can be disabled through command
/datapack disbale .... - The command
/extshape:check-conflictadded a new parameter to filter namespaces.- Tests recipe conflicts of all namespaces if not specified.
- Tests recipe conflicts between the specified namespace and vanilla if only specified one.
- Tests the specified namespaces if specified multiple ones.
- Removed the BlockFamilies feature which lacks practical usage.
- Fixed the issue that various shapes of white oak wood, white oak log, herringbone planks, small log blocks of Blockus cannot be burnt in the furnace.
- Totally removed various shapes for sugar blocks, as it is a falling block and does not meet the criterion of creating various shapes.
- Fixed the issue that some fence gate blocks can be mined with axes.
- Removed block tag
extshape:pickaxe_unmineableand modified the implementation of block mining.
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:tb7kCxSW:QM1p0foX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tb7kCxSW:QM1p0foX"
}
