Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
Due to my lack of updates to this plugin, its compatibility with newer MC versions has been very dependent on me to update NBT-API, an API that is shaded into the plugin. This was meant to make installing the plugin simpler for server owners, but quickly became a hindrance for server owners since they would have to wait for me to update the plugin solely to update the API.
To finally address this issue, I no longer shade the API into the plugin and it is now the server owner's responsibility to install and update the plugin version of NBT-API. Hopefully, this will allow the plugin to keep going without me holding it back. NBT-API can be downloaded on Modrinth here.
Since this is a major change to how the plugin works and I want to draw attention to that, I am calling this version 2.0.0, despite the lack of major feature additions/changes to the plugin itself.
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:4h6EFh3D:FqYZz6Aj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4h6EFh3D:FqYZz6Aj"
}

