Tags
Creators
Details
All versions
1.3.1
Release
PremiumUUID 1.3.16 days ago 30
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Paper
Purpur
Changes
PremiumUUID v1.3.1
Security & Fixes
- Unauthorized Pardon (security): Any player, even without op, could type
/pardon <player>and the plugin would lift that player's bans on every known identity. Identities are now only pardoned when the sender is allowed to use/pardon, or when the command itself lifted a ban. Updating is recommended for every server. - IP & Third-Party Bans Respected: The plugin no longer lets in players kicked as banned when the ban did not come from the vanilla profile ban list. IP bans (
/ban-ip) and bans from other plugins are now always kept. - Whitelist Op Bypass: Ops who are not in
whitelist.jsonare no longer kicked by the plugin, matching vanilla behaviour. - Kick Messages Preserved: Players rejected for another reason, such as a full server, no longer see "You are not whitelisted".
- Login Resilience: Unusual nicknames or a malformed response from the Mojang API could throw errors during login. The player now joins with the offline UUID instead.
- Mojang API Timeouts & Rate Limits:
timeout-msnow limits the whole lookup, and the plugin backs off after a rate limit (HTTP 429) or a failed lookup instead of querying Mojang again on every reconnect. - Reload Feedback:
/premiumuuid reloadnow warns that a change tocache.fileonly takes effect after a restart.
Under the Hood
- Lighter Disk I/O: The UUID cache is only written when it changed, and command-triggered writes no longer block the main thread.
- Thread-Safe Config: Configuration values are swapped atomically on reload, so async logins never read a half-updated config.
- E2E Version Matrix: The Mineflayer E2E suite now runs against seven Paper versions on every commit, including a new test that a non-op
/pardonis ignored. - Extended Test Coverage: Unit tests went from 8 to 33, covering the pardon authorization, ban/whitelist handling, Mojang API client, cache and config reload.
- Docs: Documented that ban, whitelist and pardon handling stays active when
premium-uuid-enabledisfalse, so earlier premium identities cannot be used to evade bans.
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:fmzKdjSa:Nq54TbHJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fmzKdjSa:Nq54TbHJ"
}

