Tags
Creators
Details
1.0
Compatibility
Changes
This is the first stable release of WeGuardian, a lightweight and efficient security plugin for Minecraft servers.
WeGuardian is a comprehensive, professional-grade Minecraft punishment system plugin designed for modern Paper/Bukkit and Folia servers. It provides a complete suite of moderation tools with GUI-driven interfaces, advanced punishment templates, cross-server synchronization, and MySQL support.
โจ Key Features
๐ฏ Core Punishment System
- GUI-Driven Interface: Intuitive
/punish <player>command opens comprehensive punishment center - Complete Punishment Types: Ban, Tempban, Mute, Tempmute, Kick, Warn, Unban, Unmute, Notes
- IP-Based Punishments: IP bans, IP mutes with automatic player correlation
- Smart Templates: Advanced punishment escalation system with auto-progression
- Silent Punishments: Execute punishments without broadcasting with
-sflag - Advanced Validation: Duplicate punishment prevention and permission hierarchy checks
๐ Advanced Features
- Punishment Templates: Automated escalation system with configurable offense levels
- Advanced Commands:
/banlist,/mutelist,/alts,/blame,/warns,/unwarn - IP Correlation: Advanced alt account detection with shared IP analysis
- Punishment History: Complete audit trail with clickable punishment IDs
- Template Integration: Smart punishment progression based on player history
- Rich Formatting: Adventure API with hover tooltips and clickable elements
Installation:
- Download the
.jarfile from the Releases page. - Place it in your serverโs
pluginsfolder. - Restart the server to activate WeGuardian.
Compatibility:
- Works with Paper/Spigot/Folia 1.21 and above
- Requires Java 17+ or higher
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:tr7kHo9E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QsS6k1xF:tr7kHo9E"
}

