Tags
Creators
Details
1.4.0
Compatibility
Changes
Find second accounts of banned players - without storing addresses - and the proxy checks for BungeeCord networks too.
Added
- Alt detection (opt-in,
moderation.alts.enabled): every login stores a keyed hash of the address - never the address itself; IPv6 counts by its /64 network - and accounts that share one show up as possible alts:/admin alts <player>, the Possible Alts button on a profile, and a staff hint when a player joins who shares an address with a banned account (on every server of a network). Optionally refuse such players (moderation.alts.refuse-banned-alts, off by default;universaladmin.bypass.alt-checkexempts players). Addresses are forgotten aftermoderation.alts.retention(90 days);/admin alts <player> forgetdeletes a player's on request; viewing and forgetting are audited. New permissionsuniversaladmin.moderation.alts,.alts.forgetanduniversaladmin.bypass.alt-check. See docs/user/modules/moderation.md and ADR 0020. - UniversalAdmin BungeeCord: the proxy plugin for BungeeCord networks -
bans, network maintenance, the network whitelist and the server-list text,
the same
config.ymlas the Velocity plugin,/uabungee. On GitHub and as the-bungeeversion on Modrinth (ADR 0021).
Changed
- The proxy checks live in one place (
proxy/common) for both proxy plugins; UniversalAdmin Velocity behaves as before.
Upgrading
- Replace the jars and restart; a new table is created automatically. Alt
detection stays off until you switch it on. On a BungeeCord proxy, add
universaladmin-bungee-<version>.jarand fill in itsconfig.ymllike the Velocity plugin's.
What's Changed
- UniversalAdmin 1.4.0 by @nicki41 in https://github.com/nicki41/UniversalAdmin/pull/6
Full Changelog: https://github.com/nicki41/UniversalAdmin/compare/v1.3.0...v1.4.0
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:wGP5uSse:p3KEj3HK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wGP5uSse:p3KEj3HK"
}

