Tags
Creators
Details
6.9.0-EOL
Compatibility
Changes
Release 6.9.0-EOL for 1.16.2+ [COMMEMORATING 1000+ DOWNLOADS]
weheheheheaayy long time no see
So, in the time I was gone, very recently, Spigot has changed something internally and getting the biome name via Spigot/Bukkit API no longer returns CUSTOM whenever there is a custom biome involved. Therefore,
What's New?
- The plugin no longer depends on JeffLib for placeholder registration and biome fetching on 1.21.3 and above (using Bukkit API)
- Unless there are breaking changes to PlaceholderAPI/Bukkit API, this release can be used for many more Minecraft updates to come.
This plugin was created in the intention of preserving support for all versions of Minecraft, and make it easier for me to rebuild it for newer versions without needing to dig into the code for every version. Atleast when I was searching for ways to get the player's biome (even if the biome was defined in a datapack), Spigot/Bukkit API did not give a way to get the custom biome name, instead it only returned CUSTOM. I was told by a developer ( @mfnalex ) that it was possible only through NMS, and that he had a library (JeffLib) that allowed me to skip the NMS BS and just get the namespaced biome directly.
The reason it is a plugin and not an expansion is because I use(d) the library (under his advice) to register the placeholders too. Now the reason has changed because it is no longer just an expansion, it also has a command and its own configuration.
I thank you all for downloading my plugin over a 1000 times. Thank you from the bottom of my heart for making learning Java feel worth. Hope we meet again soon! (well maybe not very soon, I am sure the plugin won't need updates any time soon!)
With 💖 from PseudoPanda
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:mZSgK9Zg:mxtvNw9O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mZSgK9Zg:mxtvNw9O"
}
