All versions
1.1.0+26.2
Release
Decorative Workstations 1.1.03 days ago 33
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Changelog
1.1.0 Fabric (Minecraft 26.2)
New Features
- 7 right-click cyclable blocks, replicating vanilla animations:
- Composter: Cycles through its 9 fill levels.
- Smoker: Switches between lit and unlit.
- Blast Furnace: Switches between lit and unlit.
- Cauldron: Cycles through 8 stages (empty, water, lava, powder snow).
- Brewing Stand: Displays 0 to 3 bottles.
- Bell: Rings when clicked or hit with a projectile.
- Lectern: Shows or hides a book model without opening an interface.
- Inspection Mode: Added a master switch (
inspectionFeatureEnabled), a configurable outline thickness (highlightLineWidth), and an inline text documentation field. - Translations: Added German, Spanish, and Brazilian Portuguese translations.
- See-Through Mixin: Added
DecoSeeThroughMixinto release GPU resources and fix rendering bugs.
Technical Changes & Fixes
- Code Refactoring: Merged duplicate block classes into a single, highly configurable generic class (
DecoBlock<T>) and renamedDecoRegistrytoModBlockRegistrar. - Inspection Mode & Rendering: The visual outline changed to a 12-edge wireframe box, mode persistence rules were updated, and outline rendering logic moved to
RenderPlatform26_2. - Configuration: Restructured accepted values for render distance (
maxRenderDistance), added validation for outline thickness, and improved global handling/logging of config reading errors. - Dependencies & Build: Updated Fabric API to
0.158.0+26.2, added mixin configurations, and adjusted jar version naming.
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:PMg729qN:f2b2RUVu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PMg729qN:f2b2RUVu"
}

