Links
Tags
Creators
Details
1.1
Compatibility
Changes
Security and Architecture Overhaul
-
Enhanced Encapsulation: In CorePlugin.java, managers (PlayerManager, BotManager) are now better protected. Public getters have been removed to prevent other plugins from accessing internal data.
-
Dependency Injection: Listeners and commands now directly receive the managers they need via their constructor, resulting in cleaner code and easier maintenance.
Discord Intent Optimization
- Security Minimalism: The bot now only uses the Server Members Intent. The "Message Content" and "Presence" Intents have been disabled for greater privacy and efficiency.
New Discord Features
-
Automatic Whitelist Removal: If a member loses their role on Discord, their Minecraft whitelist is automatically revoked.
-
Slash Commands: Complete management via Slash Commands (no need to read private messages).
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:wWb2IMHo:BwhNIOXb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wWb2IMHo:BwhNIOXb"
}
