2.6.3
Compatibility
Changes
Added - New option to enable/disable the update checker
Added - New enchantments from 1.21
Fixed - A small error in the config.yml (resouce-pack should have been resouce-pack-enabled)
You have to delete the config.yml file and the plugin will create a new one or you can modify:
resouce-pack: true
with
resource-pack-enabled: true
and add this at the bottom of the file:
#########################################################
# Enable or disable the update checker. If disabled, #
# you'll not see if there's a new version available #
#########################################################
update-checker-enabled: true
If you find any bugs or want to submit a suggestion, please join my Discord
If you like my plugin, PLEASE, let a review!!! ❤️
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:LShqAhqR:BAvZ7OX3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LShqAhqR:BAvZ7OX3"
}

