2.0.0
Compatibility
Changes
š Where Am I? (Biome Edition) - v2.0.0
š Major Update! This release brings full coverage for missing vanilla biomes, milestone achievements, new utility commands, code optimizations, and expanded language support!
š ļø Fixes
- Missing Biome Names Fixed: Resolved an issue where certain biomes (especially the starting biome in new worlds) would display blank names. An automatic fallback translation system is now active so biome titles are never empty.
- UI Animation Smoothness: Fixed a minor off-by-one / boundary calculation error during the HUD notification fade-out animation.
⨠New Features
- Expanded Biome Support: Added ~20 missing vanilla biomes (sunflower_plains, old_growth_taiga, wooded_badlands, eroded_badlands, bamboo_jungle, sparse_jungle, stony_shore, frozen_river, frozen_peaks, stony_peaks, the_void, outer End biomes, and more!).
- New Utility Commands:
/whereami statsā View your exploration progress and discovered biomes count./whereami listā See a list of biomes you have already visited./whereami resetā Reset your personal biome discovery data.
- Exploration Milestones: Added custom toast notifications when discovering 10, 20, 30, 40, and 50 biomes, as well as a special achievement toast for discovering all biomes!
- Expanded Localization (20 Languages): Added full support for 10 new active languages: š®š¹ Italian | šµš± Polish | š³š± Dutch | ššŗ Hungarian | šØšæ Czech | š¹š¼ Traditional Chinese | šŗš¦ Ukrainian | šøšŖ Swedish | š»š³ Vietnamese | š¹š Thai
ā” Improvements & Optimizations
- Enhanced Color Coding: Assigned fitting, climate-accurate color categories to all newly added biomes.
- Modded Biome Readiness: Refactored internal code architecture to be more flexible, preparing seamless compatibility for modded biomes in future updates.
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:O88nL5jE:Fw8L3AJs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O88nL5jE:Fw8L3AJs"
}

