⚖️ REVEX 0.2.0 — Enforcement Core Update

REVEX 0.2.0 is a core enforcement update focused on control, stability, and better moderation flow for PRAXIC-powered servers. This release makes REVEX safer to configure, easier to manage in-game, and more flexible when handling repeated violations. PRAXIC detects. REVEX escalates.

✨ Highlights

• 🧭 New escalation modes: global and per-check
• 🛡️ Safer config loading with validation and automatic repair
• 🔍 New /revex inspect command for quick moderation checks
• ♻️ New /revex reset command for clearing escalation history
• 🕊️ New /revex pardon command for full player forgiveness
• 🔁 New /revex reload all command for deeper live reloads
• 🆔 New /revex banuuid command for UUID-based offline bans
• 🧩 New internal punishment action parser
• 📘 Updated README and clearer setup documentation
• 🔧 Updated PRAXIC compatibility metadata

🧭 Smarter Escalation Control

REVEX now supports configurable escalation behavior. Server owners can keep the classic global mode, where every punishable violation moves a player forward on one shared ladder. Or switch to per-check mode, where each PRAXIC check tracks its own escalation state separately.

Global mode

SpeedCheck → warn
FlyCheck → tempban 15m

Per-check mode

SpeedCheck → warn FlyCheck → warn SpeedCheck → tempban 15m This gives servers more precise control over how punishment progression works across different types of violations.

🛡️ Safer Configuration

REVEX 0.2.0 validates its config on load and repairs unsafe values when possible. This helps prevent broken configs from silently damaging enforcement behavior. Improved protection against:

• Empty escalation ladders
• Invalid punishment actions
• Invalid tempban durations
• Null values from manual JSON edits
• Invalid escalation reset times
• Invalid escalation mode values REVEX is now more forgiving when configs are edited by hand, while still keeping enforcement predictable.

🧩 Cleaner Punishment Parsing

Punishment ladder actions are now handled through a dedicated internal parser. Supported actions:

• warn
• tempban <duration>
• ban This makes punishment behavior stricter, safer, and easier to expand in future updates.

🧰 New Admin Commands

🔍 /revex inspect <player>

Quickly inspect a player's REVEX state from in-game. Shows useful moderation data such as:

• Ban status
• Ban reason
• Remaining ban time
• Current escalation step
• Last known violation time
• Per-check escalation state when enabled

♻️ /revex reset <player>

Resets a player's escalation history. Useful for false positives, testing, staff decisions, or giving a player a clean slate.

🕊️ /revex pardon <player>

Fully pardons a player. This removes their REVEX ban and resets escalation data in one action.

🔁 /revex reload all

Reloads more than just the main config. This command refreshes:

• Config
• Ban storage
• Escalation storage Useful for live server management without a full restart.

🆔 /revex banuuid <uuid> <name> <duration> [reason]

Adds UUID-based manual bans. This is useful when a player is offline and cannot be targeted through the normal online-player ban command.

🧱 Better Status Output

/revex status now gives a clearer overview of the current REVEX setup. It now displays:

• Whether REVEX is enabled
• Current escalation mode
• Default punishment ladder
• Number of per-check ladders
• Escalation reset time
• Staff alert status
• Discord notification status as planned functionality

🧹 Fixed & Improved

• Fixed inconsistent PRAXIC version references
• Fixed unsafe behavior with empty escalation ladders
• Fixed config edge cases caused by null values
• Improved punishment action validation
• Improved command feedback for server staff
• Improved reload behavior
• Improved long-term structure for future punishment features

📌 Notes

Discord webhook fields are still present in the config, but notification delivery is planned for a future update. REVEX currently stores bans in its own storage file instead of the vanilla Minecraft ban list.

🚀 Final Word

REVEX 0.2.0 is not just a version bump. It is a stronger enforcement foundation for PRAXIC-powered servers: safer configs, clearer commands, smarter escalation, better visibility, and a cleaner path toward future notification and ban backend updates.