Tags
Creators
Details
9.8.4
Compatibility
Changes
🚀 Version 9.8.4 - The Infrastructure Revolution
This is the most significant update in CraftersStaff history, transforming the plugin into a high-performance, hybrid network solution.
🛡️ Smart Configuration & Persistence
- Non-Destructive Config Merge: Automatic merging for
config.yml,commands.yml, menus, and all language files. - Comment Preservation: New options are appended to the end of your files. Your custom values, ordering, and YAML comments remain untouched.
- Smart Language Updates: All 7 supported languages receive new keys without overwriting your manual translations.
- Internal Cleanup: Refactored
ConfigManagerfor a cleaner codebase and zero internal warnings.
🌐 Hybrid Spigot/Velocity Core
- Single JAR Solution: One
CraftersStaff.jarfor both Spigot/Paper backends and Velocity proxies. - Auto-Detection: Lightweight environment detection using safe class-loading (prevents
ClassNotFoundException). - Unified Messaging: Introduced the
craftersstaff:mainchannel for seamless communication between servers and the proxy. - Shared MySQL Backend: Real-time synchronization of staff lists, notes, and punishments across your entire network.
🛠️ Dynamic Commands System
- YAML-Driven Commands: All definitions moved from
plugin.ymltocommands.yml. - Runtime Registration: Commands are injected via Bukkit's
CommandMapusing your custom names and aliases. - Flexible Renaming: Disable or rename any command without recompiling. (Note: Name changes require a full server restart for stability).
🚨 Network-Aware Moderation
- Global Staff Chat: When using Velocity, staff chat is broadcasted across all connected servers in the network.
- Contextual Alerts: Added a
server-nameoption. X-Ray and TPS alerts now identify the specific server (e.g.,[Survival-1]) when running behind a proxy. - Proxy Forwarding: The Velocity layer ensures that alerts reach every online staff member, regardless of which server they are currently moderating.
Created with ❤️ by xUnknowns Official Documentation | Support & Donations
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:KIb9MSpG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UAUjFHnX:KIb9MSpG"
}

