Links
Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated last week
All versions
2.8.4+1.21.1
Release
Colorful Blocks 2.8.4 for 1.21.1last week 36
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
New Features
- Added a throwable paint bucket: hold right-click to charge, release to throw, and every concrete block within the landing radius gets painted. The radius grows with charge time, up to 13 blocks at 10 seconds. Throwing costs 1.5 durability per painted block (capped at 500), and the bucket comes back as an empty bucket once it runs out.
- Added 10 custom advancements on a new
color_actiontrigger, covering painting, throwing and cleaning, including three challenges (paint at least 50 blocks with a single throw, paint red/green/blue, and clean a black block back to white). - Added a cast sound when the bucket is thrown, and a splash of color particles where it lands.
- Added a colored particle trail behind the bucket while it is in flight.
- Updated the paint bucket texture and its tintable overlay.
Fixes
- Fixed colored items rendering untinted on 26.1.2. The item model's
minecraft:dyetint samples the vanillaminecraft:dyed_colorcomponent, but mined drops,/givecand the color picker's concrete preview only wrote the mod's own color component, so the tint had nothing to read. All three now share one helper that writes both. - Fixed the color picker's concrete preview block always rendering white on 26.1.2, for the same missing-component reason.
- Fixed
/givecstoring a bare 24-bit color instead of opaque ARGB. A/givecblock and a block painted with the picker therefore compared unequal at the same color, which made the durability-aware recipe treat them as different and spend durability. - Fixed the ModernUI tooltip color leaking into later, unrelated tooltips. ModernUI keeps its fill color in a static array, so the override is now snapshotted and restored.
- Fixed a ModernUI method rename being able to throw an injection error into the render path. The injection is optional now, so a missing target degrades to "no tint" instead of crashing, and member resolution is latched so it logs once per launch, not once per frame.
- Fixed painting a vanilla concrete block not showing on the client until the block re-synced.
- Fixed the clean agent completing cleaning advancements on blocks that were already white, and changed its check to "became white" so the two cleaning challenges no longer finish on the first use.
- Fixed the advancement screen background not rendering on 1.21.1.
- Fixed a
No data fixer registered for colorblockmc:paint_bucket_projectileerror printed on every world load on 1.21.1. - Fixed an unsupported mixin compatibility level warning printed on every launch on 26.1.2.
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:VuBMNaL4:cAafPdyQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VuBMNaL4:cAafPdyQ"
}

