Tags
Creators
Details
1.2.0
Compatibility
Changes
- Loot, stats and economy transfer
Servers can now carry a player's full inventory, armor, offhand, held cursor item and ender chest across a transfer, using Minecraft's own cookie system, no external database needed. Experience/level, health and hunger, active potion effects, gamemode and Vault economy balance can each be toggled on independently under loot_transfer in the config. Real vanilla statistics can also be kept in sync between servers, always keeping the higher value instead of overwriting it. Every payload is signed with a shared network_secret (set the same value on every server in your network) and tied to the exact player it was created for, so it can't be forged, misapplied or replayed. If a transfer fails, the player's items stay safe in a local backup that staff can restore with /auricnetwork recoverloot <player>.
- Transfer reliability
Players can no longer start a new transfer while one is already in progress, closing a case where two could overlap. Items held on the cursor are no longer lost mid-transfer. Players riding a horse, boat or minecart are now safely dismounted before being sent to another server. The console now warns on startup if accepts-transfers isn't set to true in server.properties, since transfers to that server are silently rejected otherwise.
- Security
The op_command action, available for menu buttons and hotbar items, no longer grants players real operator status to run its command. It now uses a temporary, scoped permission instead.
- Other
Added a check-updates option to disable the startup update check entirely. Minor visual polish to match the rest of the Auric suite.
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:VJh21Kfz:M3OXp7TS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VJh21Kfz:M3OXp7TS"
}

