Tags
Creators
Details
Licensed LGPL-3.0-only
Published 7 months ago
Updated 2 weeks ago
All versions
3.0.6
Release
Chisel-3.0.66 months ago 34
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
[3.0.6]
Added
- Added back Carpet blocks for all colored wool variants.
- Added back Lavastone variants: Array, Chaotic Bricks, Cuts, Jellybean, and Slanted.
- Added Durability to Chisels:
- Iron Chisel: 512 uses.
- Diamond Chisel: 5096 uses.
- Obsidian Chisel: 10048 uses.
- Added an Item Overlay to the Chisel's inventory icon, showing the block currently stored inside.
- Added new Connected Texture (CTM) and Multiblock model types:
- Multiblock 2x2, 3x3, and 4x4 support.
- Connected Top-Bottom-Side (CTM TBS) support.
- Horizontal (CTMH) and Vertical (CTMV) connection support.
- V4 model support (4-variant random textures).
- Added CTM support to Bookshelves.
- Added a
clientAuthrun configuration for development.
Changed
- Refactored
CTM_MULTI_PASS_MULTIBLOCKtemplates to support multiple texture layers. - Improved CTM logic and variant registration for better performance and flexibility.
- Promoted version from Beta to Release!.
- Updated and localized descriptions for numerous blocks.
Fixed
- Fixed Lavastone multiblock models incorrectly using water textures instead of lava.
- Updated Lavastone models to use the correct parent model and layers.
- Fixed numerous texture issues across multiple block families:
- Factory: Fixed various technical and metal textures.
- Electrum: Fixed inconsistent texture patterns.
- Stone/Dirt/Cobblestone: Fixed various alignment and missing texture issues.
- Diorite/Andesite/Granite: Improved CTM transitions.
- Wood Planks: Fixed several orientation issues (Dark Oak, Acacia, etc.) and added missing Braced variant textures.
- Military/Shingles: Added missing textures for Imperial/Rebel Camo and various Shingles.
- Fixed a duplication bug in the Chisel menu.
- Fixed several server-side crashes related to menu operations and block events.
- Fixed many cases of missing or incorrect blockstate definitions.
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:GOQwOWlB:TGPYVUxG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GOQwOWlB:TGPYVUxG"
}

