2.2.9
Compatibility
Changes
Added ability to save tags to the database instead of YAML files. The settings.db-only-tags option in config.yml will use the data.yml storage type.
Added ability to edit tag vouchers inside the Tag Editor.
Improved menu click safety to prevent errors from empty slots or clicks outside plugin inventories.
Improved fallback handling for invalid or missing materials in menu and voucher configurations.
Improved safety for missing optional configuration sections.
Fixed Folia scheduler compatibility for features introduced in 2.2.7 and 2.2.8.
Fixed invalid CraftEngine item IDs causing menu item creation errors.
Fixed PlaceholderAPI and packet placeholder errors when players are offline or cannot be resolved.
Fixed data cache settings not properly syncing between servers.
Fixed file syncing not working properly.
Fixed merge issues.
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:mzraaPLu:iQanfpLM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mzraaPLu:iQanfpLM"
}

