Tags
Creators
Details
All versions
9.4.0
Release
CraftersStaff 9.4.08 months ago 22
Uploaded by
Compatibility
Minecraft: Java Edition
1.21
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platform
Spigot
Changes
🚀 Version 9.4.0 - The Customization Update
🛠️ Fully Configurable GUIs (YAML Menus)
- Dynamic Menus: All core interfaces (
staff_list,staff_detail,reports,notes) are now driven by YAML configuration. - Full Customization: Menu size, items, materials, names, and lores can be modified without restarting or recompiling.
- Flexible Layouts: Staff list GUI now supports configurable inventory sizes directly from the menu files.
💎 Staff Mode Quality of Life
- Navigation: Added a dedicated back button in the Staff Detail menu, fully defined in YAML.
- Safety First: Per-slot actions in Staff Detail are now explicit and safer, preventing self-action errors on decorative items.
- Inventory Protection: Strengthened protection inside Staff menus to prevent moving or taking GUI items.
🛡️ Staff Tools & Anti-Spam
- Hardened Protection: Staff mode tools can no longer be moved between slots or swapped while active.
- Drop Prevention: Dropping a staff tool is blocked and no longer triggers the tool’s action.
- Clean Chat: Removed "cannot move/drop item" spam, keeping only essential feedback for the staff.
📂 Reports & Navigation Fixes
- Consistent GUI: Fixed fast page-switching issues in the reports menu caused by decorative items.
- Reliable Arrows: Navigation arrows now behave consistently and change pages only when intended.
📈 TPS Alerts & Stability
- Translation Sync: Corrected TPS alert message keys to use
alerts.tps.alertacross all supported languages. - Anti-Spam Logic: TPS alerts now strictly respect
check-intervalandalert-staffsettings. - Modern Support: Improved overall robustness of the TPS monitoring task on the latest Paper/Spigot versions.
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:NtLNzkFF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UAUjFHnX:NtLNzkFF"
}

