Tags
Creators
Details
2.5
Compatibility
Changes
CraftersStaff v2.5 — The Core Rewrite Update
đź“‹ Overview
CraftersStaff v2.5 is the most significant release in the plugin's history. This is not just a feature update—it is a complete architectural rewrite from the ground up, designed for enterprise-grade performance, stability, and aesthetics. Every internal system (database management, networking, memory handling, security, and internationalization) has been meticulously redesigned to meet premium modern standards.
✨ Added & Improved
- Modern Architecture: Completely transitioned to a modern Dependency Injection system. This drastically reduces memory leaks and initialization bugs during long server uptimes.
- High-Performance Database Layer: All database operations have been migrated to an asynchronous connection pool. Reads and writes (player data, notes, reports) now execute with zero impact on server TPS, regardless of player count.
- Universal Proxy Compatibility: The proxy messaging layer now dynamically detects your environment, flawlessly supporting both legacy networks (BungeeCord) and modern, strict validation networks (Velocity).
- Aesthetic Revolution: Introduced a hybrid color parsing engine that fully supports modern Hex formats (
<#hex>,<gradient>) alongside legacy ampersand codes and PlaceholderAPI variables. All menus have been fully redesigned with a minimalist, premium look. - Standardized Placeholders: Migrated all internal message variables to the professional PlaceholderAPI standard (e.g.,
%craftersstaff_target%), replacing outdated bracket variables across all configurations. - Zero-Lag Mining Alerts: The X-Ray detection system was rewritten from scratch to cache configurations and filter events optimally. It now adds zero measurable overhead, even in high-volume mining scenarios.
- Discord Integrations: Added full support for Discord webhook alerts for Reports and TPS monitoring.
- Configurable Freeze Alerts: Server administrators now have full control over the interval and maximum count of periodic freeze reminders.
- Public Developer API: Added a robust public API allowing third-party developers to hook into state changes (Staff Mode, Vanish, Freeze) cleanly.
🛡️ Fixed & Secured
- Unforgeable Staff Items: Staff item validation was upgraded to use persistent data tags (NBT) instead of simple name matching. Players can no longer forge staff items using an anvil to bypass restrictions.
- Multiverse Safe-Transit: Implemented a delayed world-transition safety check. Staff mode inventories, flight, and vanish states are now perfectly preserved when teleporting across worlds, preventing conflicts with inventory management plugins.
- GUI Security Exploits: Resolved a critical bug where players could bypass event cancellations and steal items from the Staff Menus.
- API Compatibility: Fixed a major API version mismatch that caused crashes on newer server versions, ensuring flawless execution on Paper 1.19 through 1.21+.
- Bulletproof Memory Cleanup: The memory management routine now aggressively purges all player state maps exactly at disconnect, guaranteeing zero memory accumulation over time.
- Menu Pagination & Visuals: Fixed broken pagination logic in the Notes and Reports managers. Additionally, resolved an issue where advanced color tags (
<gray>) failed to render properly on status labels. - Player Head Rendering: Fixed an issue where player heads in the GUI would not be clickable or load correctly if the player was offline.
- Hardcoded Strings Eliminated: A full codebase audit was performed to eliminate all hardcoded player-facing messages. Every single message is now 100% configurable via your language files.
🗑️ Removed
- Legacy Web System: The embedded HTTP web server and remote execution endpoints have been permanently removed. This significantly reduces plugin weight, startup time, and potential attack surfaces, making CraftersStaff a fully native, self-contained Minecraft plugin.
- Monolithic Command Structures: Outdated, heavily-coupled command architectures were removed in favor of modular, isolated command executors loaded dynamically.
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:ZDXDvD9l"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UAUjFHnX:ZDXDvD9l"
}

