Tags
Creators
Details
v24.1-DAISY_b2
Compatibility
Changes
・It's the end of 4th generation era. Sad to hear that, but now there is only just version number... Now plugin will support only 1.14+ versions and Java 14+. ・Fixed Token Encryption system. Make sure you've enabled 'TokenReplacement' feature and replaced your token. Improved encryption system, now it's more secure. ・Added multi-role feature! Now you can form list in RoleID(for example) and provide many roles - bot will add/remove them. ・Fixed typo in EPHEMERAL_MESSAGES. You need(if this feature was enabled) to replace EMPHERIAL_MESSAGES to EPHEMERAL_MESSAGES ・Fixed error: "Unknown message" when CONFIRM_MENU is enabled ・Fixed bug when server will stuck with plugin shutdown ・Added 1.20.4 support ・Fixed Linking. Now it should work with FLOODGATE_BEDROCK feature.
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:AzVOgtDW:7jwlb6b9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AzVOgtDW:7jwlb6b9"
}

