Tags
Creators
Details
All versions
1.0.3
Release
AuraCraft 1.0.35 months ago 44
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Changes
1.0.3 Patch
- Fixed
ClientHelloPayloadnever being registered server-side, which could silently drop packets or disconnect clients. - Moved
enabledEffectIdsfromSyncEffectPayloadtoUiStatePayloadso the full enabled-effect list is sent once on join rather than on every sync call. - Bumped client/server handshake protocol to version 3 to reflect the changed packet formats.
- Fixed grammar in PvP death messages: "killed lost" → "killed and lost", "a Aura Plus" → "an Aura Plus".
- Fixed
resetForRepickhardcoding the key name[Y]in its message; the server now sends a generic translatable string and lets the existing prompt payload show the player's actual bound key. - Simplified the redundant
instanceofpattern inapplyEffectById/removeEffectByIdto a null check followed by a single unchecked cast. - Config screen is now fully read-only when connected to a dedicated server: Save button is disabled, fields are non-editable, and a notice is displayed. Effect toggle buttons also respect this state.
- Config screen server-side sync is now submitted via
server.execute(), fixing a client-thread race condition in singleplayer. - Converted all remaining hardcoded
Component.literalplayer-facing messages toComponent.translatableentries. - Added missing lang keys:
ui_disabled,effect_reset,repick_item_used,max_tokens_reached,extra_token_gained,withdrawn_effect_restored,pvp_lost_token. - Replaced private constants + getter boilerplate (
getChosenEffectKey()etc.) withpublic static finalfields inEffectSmpMod. - Replaced manual last-element iteration over
LinkedHashSetwithstream().reduce((a, b) -> b)inwithdrawLatestSelectedEffectandremoveLastSelectedEffects. - Removed
refreshEnabledEffectsFromConfig()from the client mod; the enabled-effect list is now kept in sync exclusively viaUiStatePayload.
Optional dependencies
Unavailable version
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:1LTZnmB3:oUX1sKmT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1LTZnmB3:oUX1sKmT"
}

