Tags
Creators
Details
Licensed MPL-2.0
Published 2 years ago
Updated last week
All versions
v2.1.0+1.21.1-fabric
Release
Tiny Flowers v2.1.0+1.21.1 for Fabriclast week 83
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Known Issues
- This is the first 2.x.x release for 1.21.1 and 1.21.11. It is not compatible with existing worlds.
- Upgrading an existing world will cause all Tiny Flowers items and blocks to disappear from your world.
- Only one type of tint can exist per flower model part. If a model part declares multiple
tintindexvalues in its definition, the first one will be used. - (1.21.1) The dry foliage tint type is not available (as it's not in the game yet).
- Any flower types using this will instead be tinted using the normal grass color.
- (1.21.1) Flower type transformations do not emit particles.
- These particles use the same type as Eyeblossoms, which do not exist in this version.
- (1.21.1) Force picking (ctrl + middle click) a Tiny Garden in the world where the first flower is Pink Petals results in a Pink Petals item with extra data.
- Placing this item only places one Pink Petal, not the full garden.
Added
- Tiny Flowers can now be placed inside Flower Pots.
- New
#tiny_flowers:supports_vegetationblock tag.- For now this follows Vanilla's
#minecraft:supports_vegetation, but is here to better support versions prior to 26.1 when the tag was added. - Adding new blocks to this tag means that most Tiny Flowers can be placed on them, but not other vegetation (like grasses and regular flowers).
- This is now the default tag that's used when a flower variant does not specify and tags.
- For now this follows Vanilla's
Changed
- Tiny Poppies' height has been knocked down a pixel or two.
Fixed
- Using Florists Shears on vanilla tiny flowers in the world no longer rotates the block to your facing direction.
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:S0Lqneqb:bUhCGgIK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:S0Lqneqb:bUhCGgIK"
}

