Tags
Creators
Details
2.2.0
Compatibility
Changes
โจ Dynamic Configuration Reload & Improved Stability
This release focuses on making Blocketing more robust, easier to configure, and more reliable for server admins.
Highlights
-
Dynamic Configuration Reload
- Added
/blocketing reloadcommand to reload the config and restart the Discord bot without restarting your server. - Instantly apply changes to bot token, channel, guild, OP role, and webhook in-game.
- Added
-
Improved Error Handling & Logging
- Discord bot startup now validates configuration and provides clear error messages if setup is incomplete or invalid.
- All logging now uses SLF4J for consistent and clear output.
- Added warnings if the bot is not initialized when sending messages.
-
Quality of Life Improvements & Bugfixes
- Fixed avatar URL in player join notifications.
- Updated project metadata and removed unused code for a cleaner codebase.
Thank you for using Blocketing!
If you have questions or issues, open an issue on 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:WQAfq7OC:kLA7Pqr0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WQAfq7OC:kLA7Pqr0"
}

