Tags
Creators
Details
All versions
1.8
Release
CraftersStaff - 1.87 months ago 58
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
Paper
Purpur
Spigot
Changes
CraftersStaff v1.8 — Persistent Vanish & UX Improvements
✨ New Features
- Added
/unfreezecommand to unfreeze players directly. - Persistent Vanish System — Vanish state now persists when disabling Staff Mode.
- New
vanish.persist-on-staff-disableoption (default:true). - New
vanish.auto-enable-on-staff-disableoption (default:false).
- New
- Proxy Bridge Plugin — New
CraftersStaff-Proxyfor Velocity, BungeeCord and Waterfall.- New
proxy-config.ymlwith storage modes (LOCAL/MYSQL), sync settings and debug mode. - Staff state (staff mode, vanish, freeze) now persists on server switch.
- Network-wide freeze notifications with server name:
[Freeze] [ServerName] Player has been frozen by Staff. - Separate local and network freeze notification messages (
staff-notify-freeze-network,staff-notify-unfreeze-network).
- New
- Ban-on-quit system — Frozen players who disconnect are automatically banned via a configurable console command.
- Self-action prevention —
/freeze,/unfreeze,/reportand/notecan no longer be used on yourself. - Freeze state validation — Freezing an already frozen player shows an
already frozenmessage. Unfreezing an unfrozen player shows anot frozenmessage. - New
freeze.still-frozenmessage shown to players attempting to rejoin while still frozen.
🔧 Changes
- Improved Player List Menu — Click on any player head to instantly open the quick actions menu. Removed complex
Shift+Clickcombinations for better UX. - Simplified freeze chat —
/freeze <player> [message]now sends messages directly to the frozen player. - Discord link is now embedded directly in the freeze message via
lang/messages.ymlinstead of a separate config variable. - Removed
discord-messageconfiguration variables from the freeze system for a cleaner setup. - Freeze notifications now properly distinguish between staff and frozen player messages:
- Staff see:
[Freeze] > Player has been frozen by Staff - Frozen player sees:
[Freeze] > You have been frozen by Staff
- Staff see:
- Improved freeze chat format:
[Freeze] Staff > message. - Enhanced freeze command help:
/freeze <player> [message]. - Better permission handling in the player actions menu.
- Code optimization in
ConfigManagerwith default fallback values. - Version updated to
1.8across all components.
🐛 Fixed
- Fixed all freeze messages no longer including the plugin prefix for cleaner notifications.
- Fixed
freeze.discord-messagereference causingMessage not founderror. - Fixed freeze chat format now using single
>instead of double>>. - Fixed
UnsupportedOperationExceptionon player join — now uses properStaffManagermethods. - Fixed variable
{staff}in unfreeze message not displaying correctly. - Fixed duplicate messages in frozen player chat — messages no longer echo back to sender.
- Fixed
/craftersstaff helpcommand showingMessage not founderrors. - Fixed help messages updated with all available commands including
/reportand/stafflog. - Fixed Velocity proxy
NullPointerException— updatedvelocity-plugin.jsonwith correct version and main class. - Fixed
Message not found: freeze.still-frozenerror. - Fixed freeze ban-on-quit command now executes from console on next tick for reliability.
- Fixed freeze state not being properly cleaned up on player quit.
- Fixed Velocity proxy
InvalidPluginException— removedvelocity-plugin.jsonfrom backend JAR. - Fixed Velocity proxy
IllegalArgumentException: plugin main instance automatically registered.
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:zkveGgql"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UAUjFHnX:zkveGgql"
}

