Tags
Creators
Details
1.1.0
Compatibility
Required content
Changes
AuraCraft 1.1.0
Minecraft 26.1.2 · Fabric Loader 0.19.1+ · Fabric API 0.145.4+26.1.2
This update is a full rework of the mod's core systems. If you played an earlier version, things will feel familiar but tighter and more intentional.
Your auras are no longer gone forever
Lost an aura to a PvP fight? Withdrew one by accident? AuraCraft now remembers. Use an Aura Plus and it will restore the last aura you lost — automatically, no picker needed. Use enough Aura Plus items and you can work your way back to exactly where you were.
The picker is always open
You can now open the Aura Picker (Y) at any time, even if you have no points to spend. Browse your options, read descriptions, plan your next pick — the screen no longer locks you out. The Choose button simply stays grayed out until you have a point ready.
Withdraw now works in bulk
/aura withdraw accepts an amount now. Need to convert three auras into Aura Plus items at once? One command.
Aura Reset has a safety gate
The Aura Reset item will no longer activate if you've never picked an aura. This prevents accidentally burning a Reset before you've even made any choices.
Item stack sizes changed
| Item | Before | Now |
|---|---|---|
| Aura Plus | 16 | 1 |
| Aura Reset | 16 | 8 |
Aura Plus is now a single-use item by design — each one represents one lost aura or one new point.
Balance settings moved in-game
max_auras, drop_plus_on_kill, and the Heart of the Sea recipe toggle are now GameRules. Set them with /gamerule without touching any files.
New command: /aura restart
Admins now have a hard reset option that returns a player to a clean slate — 1 point, no auras, no history. Useful for fresh starts or fixing edge cases.
Both server and client must be on 1.1.0. Older clients will be disconnected on join with a message explaining the mismatch.
Optional dependencies
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:rOgBIenD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1LTZnmB3:rOgBIenD"
}

