Tags
Creators
Details
1.3
Compatibility
Changes
[Added] New command /kit gui which shows GUI with all kits
[Added] New Database kits.db which now contains all the kits, kits are no longer stored in config.yml
[Added] New options in config.yml: kits-enabled and database-file. In kits enabled you can turn off kit system, if you want to use another plugin for kits. I recommend not to change database-file.
[Migration] All the kits will be migrated automaticly after installing and restart. After migration, I recommend deleting config.yml and restart again, because sometimes the file does not include new features like kit-enabled.
[Known Issue] If you're using HrdaNick, /vanish will send left/join message with your normal nick, not with your custom nick.
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:oAjBZoeB:lrkQTWfU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oAjBZoeB:lrkQTWfU"
}

