Tags
Creators
Details
2.3
Compatibility
Changes
๐ก๏ธ 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
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:QsS6k1xF:aO8QrpHr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QsS6k1xF:aO8QrpHr"
}

