Tags
Creators
Details
Licensed Apache-2.0
Published last month
Updated 2 days ago
All versions
1.2.1
Release
UniversalAdmin 1.2.13 days ago 8
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.1โ26.1.2
1.21.7โ1.21.11
Platforms
Paper
Purpur
Changes
Maintenance done right in a network: one server or all of them.
Added
- Network maintenance:
/admin maintenance network on [kick] [reason]closes every server of the network at once (and the proxy with UniversalAdmin Velocity), with its own reason, message and allow-list;off,status,list,allowanddenylikewise. The GUI page has a second row for it. New permissionuniversaladmin.server.maintenance.network. See docs/user/network.md and ADR 0017. - UniversalAdmin Velocity refuses logins during network maintenance
(bypass permission on the proxy or the network allow-list still get in)
and shows "Maintenance" in the server list (
maintenance-checkin its config.yml)./uavelocityshows both checks. - A server in network mode without LuckPerms says at startup that OP and permissions count per server, and how to share them (network.md).
Fixed
- Maintenance in network mode was shared by accident: every server used the same stored state, so putting one server into maintenance closed the others after their next restart. Each server now keeps its own.
/admin maintenance statusand the dashboard tile also show the network's maintenance.- Import summary and allow-list audit entries no longer say "1 punishments" or "1 players".
- UniversalAdmin Velocity names its author in the proxy log, and no longer uses the deprecated event order API.
- Javadoc of the extension API: no more links to classes that only exist in the plugin.
Upgrading
- Replace the jars (plugin on every server, and UniversalAdmin Velocity on
the proxy if you use it) and restart. A new table (
ua_maintenance) is created and the old maintenance state copied into it - every server keeps the maintenance it had. In a network, give every server anetwork.server-nameif you have not yet.
What's Changed
- UniversalAdmin 1.2.1 by @nicki41 in https://github.com/nicki41/UniversalAdmin/pull/4
Full Changelog: https://github.com/nicki41/UniversalAdmin/compare/v1.2.0...v1.2.1
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:rO2SxXd8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wGP5uSse:rO2SxXd8"
}

