Tags
Creators
Details
0.3-Seed.2
Compatibility
Changes
Changelog 0.3-SEED-2
π± Biomentry v0.3-SEED-2 β Changelog
This update introduces new biome title display options, improved compatibility, and several important bug fixes.
β¨ New Features
-
Boss Bar Display for Biomes
Titles can now be displayed using a Boss Bar at the top of the screen.- Configure
colorandstyleinbiomes.ymlper biome. - Supported Boss Bar colors:
BLUE,GREEN,PINK,PURPLE,RED,WHITE,YELLOW - Supported styles:
SOLID,SEGMENTED_6,SEGMENTED_10,SEGMENTED_12,SEGMENTED_20
- Configure
-
New Title Animation:
slide
A newslideanimation type has been added for biome titles, enabling a smooth sliding effect.- Set
animationType: slideundertitleInfoinconfig.yml
- Set
π Improvements
-
Commented
biomes.ymlFile
Thebiomes.ymlfile is now fully documented with comments explaining each parameter:title,subtitle,display,sound,separator,commands,particle, andbossBar- Easier customization and better understanding of available features.
-
Default Biomes Expanded
The config now includes default entries for all known Minecraft biomes up to version 1.21.7 -
Minecraft 1.21.x Support
Official compatibility with Minecraft 1.21.x (tested on 1.21.7).- Maven dependencies and
plugin.ymlhave been updated accordingly.
- Maven dependencies and
π Bug Fixes
- Fixed an issue where Boss Bar properties were not properly loaded by
ConfigManager. - Fixed a missing import in
BiomeListener.java. - Fixed the animation dispatch logic in
TitleAnimation.javato correctly handle all animation types.
π Next Step:
Biomentry v0.3-SAPPLING will focus on contextual conditions, cooldowns, and dynamic title behavior based on weather and time of day.
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:aVE0EPce:4JAb074L"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aVE0EPce:4JAb074L"
}

