Tags
Creators
Details
1.7.3
Compatibility
Changes
๐ DuckyAntiKomar - Changelog v1.7.3
๐ Changes & Removals
๐ซ Disabled KomarB & KomarC checks
Due to weak detection and the need for a full rewrite, these checks have been temporarily disabled. They will return in a future update with improved accuracy.
๐ New Features
๐ Update Checker
The plugin now automatically checks for new updates and notifies administrators. Can be disabled in config.yml.
โ Config & Messages Update
๐ Changes in config.yml & messages.yml
Some options have been renamed and modified. You must regenerate the files (config.yml & messages.yml) to apply the latest changes!
๐ก Recommended Actions After Updating
โ Delete config.yml & messages.yml to regenerate new versions with the latest settings.
๐ Thanks for using DuckyAntiKomar!
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:VJAIqQnP:ou9wsh9x"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VJAIqQnP:ou9wsh9x"
}

