Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated last week
All versions
1.0.5
Release
Hotfix v3last week 96
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.9–1.21.11
Platforms
Paper
Purpur
Changes
# AUTHENTICATION (new)
+ auth.mode: DIALOG — native pre-spawn UI, before the player enters the world
+ auth.mode: CHAT — /login and /register (fallback; forced when bedrock.mode=proxy)
+ auth.hideChatCommands: true — hides auth commands from chat and autocomplete
+ dialog: maxAttempts 3, sessionTtl 2h, welcomeTtl 15min, packTimeout 60s
+ no more vanilla "Waiting for server" screen: uses CLOSE, no countdown
# PREMIUM x CRACKED (new)
+ premium detected via Netty handshake (channel injection), no external plugin
+ premium joins straight in with the Mojang UUID; cracked keeps login/password
+ cracked account using a premium nick is blocked
+ session cache 7 days — no Mojang lookup on every login
+ configurable handshake timeout (auth.premium.timeoutMs, 3000ms)
+ hashed cookie
# UUID MIGRATION (new)
+ migrates on its own on the first boot, BEFORE the managers load
+ pairing (offline -> Mojang) detected by nick: auth.yml + usercache.json
+ rewrites the ymls and moves player data (inventory, EC, XP, position, advancements, stats)
+ verified backup before any mutation + MANIFEST with rollback
+ runs ONCE (done flag); after that only via /aurauuids
+ /aurauuids: scan | apply | status | purge | migrar
+ forced UUID->UUID migration for conflicts or moving data between accounts
+ gate: blocks premium login while old data is still unmigrated
# PERMISSIONS AND OTHERS
+ permission nodes in English, with the old (pt) ones kept as legacy aliases:
+ quicklogin/rapidologin, mobstick/graveto, claim/terreno, link/vincular, clan/cla
+ anti-dupe: Ender Chest, crates and shops
+ Clan Ender Chest: warns when it is already in use by another member
- pack prompt: "&ePack do servidor necessario para ver os glyphs oficiais."
+ pack prompt: "AuraEssentials"
- permission descriptions in Portuguese (became legacy aliases)
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:ewrf0pon:14IaAeT3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ewrf0pon:14IaAeT3"
}

