Tags
Creators
Details
2.2
Compatibility
Changes
đ WeGuardian v2.2 â Database & Security Fixes
đ Fixes & Improvements
-
Fixed MySQL index creation issues (now fully compatible with MySQL & SQLite).
-
Punishment broadcast messages now correctly use
messages.prefixfromconfig.yml. -
Resolved a critical IP-ban bypass issue allowing alt accounts to join.
- Improved IP normalization (IPv4 & IPv6-mapped IPv4)
- Fixed IP ban cache logic so new bans apply instantly
âšī¸ Notes
- No database migration required
- No config or permission changes
- Safe drop-in update
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:n5uZdtQA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QsS6k1xF:n5uZdtQA"
}

