Tags
Creators
Details
0.2-Sapling
Compatibility
Changes
Changelog Beta 0.2
π§ Biomentry v0.2.0 β Performance Improvements & New Features
This update introduces significant optimizations and new features to deliver a smoother, more customizable experience with enhanced plugin integration. (it's a softdependance, not absolutly needed to make the plugin works)
β¨ New Features
π PlaceholderAPI Integration
Biomentry is now fully compatible with PlaceholderAPI, allowing you to display dynamic biome-related data in other compatible plugins.
Available placeholders:
%biomentry_biome%β Displays the playerβs current effective biome (including cave detection).%biomentry_biome_raw%β Displays the raw Minecraft biome name the player is currently in.%biomentry_is_in_cave%β Returnstrueif the player is detected inside a cave,falseotherwise.%biomentry_notifications%β Returnsenabledordisableddepending on whether the player has biome notifications turned on.
π World Blacklist
You can now disable Biomentry in specific worlds by adding them to a blacklist in the configuration file.
βοΈ Optimizations & Improvements
-
Optimized Cave Detection
The cave detection system has been redesigned with throttling to reduce server load and improve overall performance. -
Faster Config and Language Loading
Configuration and language file handlers have been optimized to minimize disk I/O, resulting in faster plugin startup. -
Preprocessed Color Management
Color codes and gradients are now processed once during configuration loading, eliminating redundant calculations and improving responsiveness. -
Cleaner, Maintainable Code
Magic numbers have been replaced with named constants for better readability and easier maintenance.
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:tNjRtFnw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aVE0EPce:tNjRtFnw"
}

