StaffCore — Next-Gen Moderation Suite | Heuristics • HUD • T

StaffCore v1.3.0 Update A major milestone update bringing full modernization, modern Paper/Java 21 compatibility, visual staff enhancements, and advanced moderation tools. What's New & Improved in v1.3.0: 1. Modern Server Engine & Java 21 Support: · Fully upgraded and tested for Paper 1.21.x, Paper 26.x (Build 92+) and Java 21 LTS. · Migrated legacy action bars to native Paper Adventure API for smoother HUD rendering. · New intelligent startup verification banner displaying native version compatibility: Code (Text): ---------------------------------------- StaffCore | Modern Moderation Suite Version: 1.3.0 Author: Dafealru Paper API: 26.2.build.92-stable Supported Version: Yes (Native 1.21.x / 26.x) ---------------------------------------- 2. Complete IP Moderation Suite: · /sctempbanip <player|ip> <duration> <reason> - Temporarily ban players and their IP addresses. · /scbanip <player|ip> <reason> - Permanently ban players and their IP addresses. · /scunbanip <player|ip> - Instantly revoke an IP ban. · Full permission integration (staffcore.punish.banip, staffcore.punish.tempbanip, staffcore.punish.unbanip) and Tab auto-completion. 3. Staff Mode Glowing Aura & Visual Effects: · Activating Staff Mode (/staff) now applies an illuminated Glowing Outline aura around the staff member's character model combined with orbital spiral particle effects. · Automatically cleans up and restores standard player visibility upon disabling staff mode. 4. New Hotbar Moderation Tools: · Spectator Mode Tool (Ender Eye): Right-click to switch on the fly between Spectator mode (noclip/phase through walls) and standard Staff Flight Mode. · Night Vision Tool (Golden Carrot): Right-click to toggle clear infinite Night Vision on and off. 5. Enhanced Freeze & Anti-Bypass System: · Added powder snow freeze tick effects, snow particle ambiance, and acoustic feedback. · Comprehensive anti-bypass listeners: blocks vehicle mounting/dismounting, elytra gliding, riptide tridents, projectile shooting, item dropping, and item consumption while frozen. 6. New Subcommands & Language Defaults: · Added /staff version (aliases: /staff ver, /staff about) to check plugin version, author credits, and engine status in real-time. · Default language configuration set to Spanish (es) with full multi-language options (en, fr, pt). Author: Dafealru JAR File: StaffCore-1.3.0.jar

StaffCore 1.2.0-b2 Stability, Anti-Abuse Hardening, Freeze/Vanish Rework, and Internal Reliability Upgrade​ Summary This update is focused on production stability, abuse prevention, cleaner moderation flow, and safer data persistence. Most changes were made to reduce edge-case failures in real servers and make behavior more predictable for both staff and players. What changed, why, and impact · Migrated to api-version 1.21 and Java 21 build - Why: Keep compatibility aligned with modern Paper runtime and tooling. - Impact: Better long-term compatibility, cleaner modern build path, fewer runtime mismatches in current server stacks. · Anti-abuse protections hardened for staff mode/vanish - Why: Prevent misuse while moderating (combat, interaction, block modify, item pickup), all configurable. - Impact: Lower abuse surface, safer staff operations, more controlled moderation sessions. · Freeze persistence and state flow improved - Why: Fix reconnect/state edge cases and keep freeze lifecycle consistent. - Impact: More reliable freeze behavior across disconnect/reconnect, fewer broken states. · Freeze chat and visual templates upgraded - Why: Improve communication clarity during active moderation. - Impact: Players get clearer instructions, staff sees cleaner structured information. · Fixed interaction lock after unfreeze - Why: Some players remained partially blocked after freeze removal. - Impact: Normal gameplay interaction is correctly restored after unfreeze. · Fixed freeze damage/attraction anomalies - Why: Prevent abuse and inconsistent entity/physics behavior while frozen. - Impact: Freeze sessions are cleaner and harder to exploit. · Stricter multi-language pipeline - Why: Avoid mixed-language output and keep language persistence stable. - Impact: More consistent translation output and better user-facing localization quality. · /staff help expanded and clarified - Why: Command discoverability and onboarding needed improvement. - Impact: Faster staff onboarding, fewer command errors, better in-game guidance. · Command autocomplete improved - Why: Improve usability for staff/sanctions/reports/xray command flows. - Impact: Faster execution, fewer syntax mistakes, smoother moderation rhythm. · Wiki and help texts updated - Why: Keep docs synchronized with real plugin behavior. - Impact: Lower setup confusion and fewer misconfigurations. · Internal listener refactor - Why: Reduce monolithic responsibilities and improve maintainability. - Impact: Cleaner architecture, easier future fixes/features, lower regression risk. · Async/batch persistence + crash-safe IO base - Why: Reduce sync write pressure and improve data safety on unexpected shutdown. - Impact: Better runtime performance profile and safer persistence model (temp + replace + recovery + optional backup). · /staff health diagnostic upgrade - Why: Improve observability for server owners and debugging workflows. - Impact: Faster troubleshooting and clearer technical status visibility. · Vanish/TAB desync fix - Why: Eliminate hard desynchronization issues reported in vanish visibility. - Impact: More stable visibility behavior between world view and tab list. · Final vanish behavior normalized (less aggressive) - Why: Previous strict mode could over-apply visibility and create side effects. - Impact: More predictable production behavior; avoids breaking TAB and general player visibility. Operational notes · This is still beta, but significantly more stable than previous builds. · Recommended after update: full server restart (not only reload) for clean runtime state. · If you use custom lang/config files, re-check new keys before going live. If you report an issue, include: · Server version · Plugin version · Reproduction steps · Full console log/error Thanks to everyone testing StaffCore and sending reports. Your feedback is what improves every version and helps us fix real server edge cases faster. I’m always paying attention to your reports and suggestions, and I’ll keep polishing the plugin update by update. ​