Tags
Creators
Details
1.1.0
Compatibility
Changes
-
A rank-based welcome system was added upon joining: title, subtitle, chat message, action bar, sound, fireworks, and a non-damaging lightning bolt, triggered by the player's highest numerical rank.
-
A configurable quick access bar system was added: it grants players custom items upon joining with click actions (transfer, command, open menu, sound, message, etc.) and protection against dropping, moving, picking up, or swapping them.
-
The rotating announcement system was replaced with named announcements: each announcement has a unique ID and is sent on demand with
/auricnetwork announce <id>, with autocomplete and individual permission per announcement. -
Maintenance mode was added: servers on the list reject incoming transfers and display a message instead of silently failing.
-
The command
/auricnetwork statuswas added, which lists all servers on the network with their real-time status and a maintenance tag when applicable. -
- The main
/auricnetworkcommand has been expanded to accept all subcommands (server,spawn,lobby,party,status,announce) with dynamic autocompletion based on player permissions. The individual commands (/server,/spawn,/lobby,/party) continue to function as before.
- The main
-
Each permission in
auricnetwork.command.*has been restructured, dividing them as granularly as possible (each/partyand/spawnsubcommand now has its own individual node) so that a function can be removed without affecting the others. -
The permission to transfer other players (
server-others) has been separated from the permission to transfer oneself to avoid hierarchical confusion. -
The queue priority permission (
auricnetwork.queue.<number>) now accepts any number instead of a fixed range. -
Redundant server lists were removed from the announcements, boss bar, action bar, and quick access bar, as they were simply duplicating what
current_server_namealready defines. -
Minor performance improvements
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:Pnw0sgGu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VJh21Kfz:Pnw0sgGu"
}

