Tags
Creators
Details
All versions
11.0.0
Release
CraftersStaff 11.0.07 months ago 37
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.5
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Bukkit
BungeeCord
Paper
Spigot
Velocity
Waterfall
Changes
CraftersStaff v11.0.0 — AdvancedBan, LiteBans & Diagnostics
🔌 AdvancedBan Integration Upgraded
- Added comprehensive debug logging to the hook: event type, punished player, issuer, reason and duration.
- Console messages now announce when the hook is registered and list detected event classes.
👁️ Sanctions Command Listener Improved
- Every console or in-game sanction command now produces a detailed log entry with target, reason and duration.
- Console-executed commands are now treated identically to player-executed ones.
- Granular debug output for ban/tempban, mute, kick, warn, unban, unmute and unwarn.
🛡️ Error Handling & Diagnostics Hardened
- Individual reflection failures are now logged, showing which getter (
getActor()vsgetStaff()) succeeded. - Unhandled exceptions inside event handlers are no longer silently swallowed — logged with full context.
🌐 Webhook Behaviour Refined
- Console-executed sanction commands now correctly trigger Discord embeds.
- Per-type toggles and proper URL handling (
webhook-urlwithlinkfallback). - JSON escaping and HTTP error body logging for easier debugging.
⚖️ LiteBans Integration Prepared
- Added the same detailed logging and event handling used for AdvancedBan.
- If LiteBans is present, the hook will activate and report punishments with full diagnostics.
These changes provide robust monitoring of moderation actions and give server operators full visibility when using AdvancedBan, LiteBans or similar sanction systems alongside CraftersStaff.
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:UAUjFHnX:yBHF6rMy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UAUjFHnX:yBHF6rMy"
}

