Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Creators
Details
Changelog
🛡️ WeGuardian v2.3 – Changelog
🐛 Bug Fixes
- Fixed
/unbanipunbanning the incorrect IP when a banned player’s account was previously used by another person - Fixed
/unmuteipresolving and removing the wrong IP address - Fixed
{player}and{staff}placeholders not working in ban, kick, and mute screens - Fixed MiniMessage formatting not being parsed correctly when combined with legacy (
&) and color codes
✨ New Features
-
Added
{player}placeholder support to all punishment screen messages (ban, kick, mute) -
Added
{staff}placeholder support to all punishment screen messages (ban, kick, mute) -
Added full MiniMessage support alongside legacy color codes
- Supports tags like
<red>,<bold>,<gradient:red:blue>
- Supports tags like
-
Added hex color support in MiniMessage format
- Example:
<#FF5555>
- Example:
📢 Broadcast System
-
Added broadcast messages for all punishment types, fully configurable via
config.yml -
Supported broadcasts:
- Ban / Unban
- Mute / Unmute
- Kick
- IP Ban / IP Unban
- IP Mute / IP Unmute
-
All broadcast messages support placeholders:
{player},{staff},{reason},{duration},{expires},{ip}
⚡ Improvements
- Chat mute listener priority changed to
HIGHESTwithignoreCancelled = false→ Ensures mutes are enforced over all other plugins - Plugin now loads on STARTUP for earlier and safer initialization
- IP punishments now store and resolve the original punished IP from the punishment record instead of the player’s current IP
📁 Config Updates
- Updated
messages.ban.screento include{player}and{staff}placeholders - Updated
messages.kick.screento include{staff}placeholder - Updated
messages.mute.blockedto include{staff}placeholder - Updated
messages.mute.appliedto include{staff}placeholder - Added broadcast sections for all punishment and IP punishment types



