Tags
Creators
Details
4.0.0-beta.1
Compatibility
Changes
YVtils Discord v4.0.0-beta.1
⚠️ Beta Notice
This is a beta release. Please back up your configuration files — or even your entire server — before upgrading. While the built-in migration system aims to preserve existing configs, data loss is still possible.
📦 Changelog
🔄 Core Changes
-
JDA Library Update
- Upgraded from
5.6.1to6.0.0-rc.2
- Upgraded from
-
Monolith to Modular Migration
- Migrated from a standalone plugin to the new YVtils Collection system
-
Embeds ➜ Components v2
- Reworked all Discord UI elements using Discord's new Components v2 API
🛠 Optimizations & Improvements
-
Persistent Stats Channels
- Stats channels now persist through server restarts to avoid rate limit issues
-
Console Sync Enhancements
- Cleaner message formatting and more efficient syncing logic
-
File Format Upgrades
- Internal saves (e.g.
discord/save.yml) are now stored as JSON
- Internal saves (e.g.
-
Config Cleanup
- Optimized overall configuration structure
-
Improved Internal Logic
- Cleaner codebase, faster background processes
-
Minecraft Permissions Update
- Discord-linked permissions are now automatically set as default
✨ New Features
-
Expanded Sync Options
- 🔁 Player Deaths
- 🏆 Player Advancements
- 🔌 Minecraft Server Join / Leave events
-
Bot-Friendly Configuration
- New toggles allow bots to trigger sync actions (e.g. executing server commands)
-
Component Emoji Support
- Application emojis are now used for icons inside Components
-
Multi-Select Enhancements
- Added support for multi-selection in the "force remove" menu
For support and discussion, visit our Discord Server or contribute via GitHub.
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:2VysTIcY:TnfJOip3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2VysTIcY:TnfJOip3"
}

