Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated last month
All versions
1.2.2
Release
AirCore 1.2.26 months ago 47
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Folia
Paper
Changes
- Fix: Stop cancellation checks once teleport is complete.
- Changed: Now all placeholders %player% and %target% use display names instead of player names.
- Changed: /back to now save location before any teleport (world changes, TPA, /back itself, spawn teleports, etc.).
- Added: Added /nick command, including colors and formats (permissions are the same for chat).
- Added: Added new placeholder %aircore_player_displayname%
Remember to add these new lines in your config files!
- New in config.yml:
chat:
# Player nicknames
nickname:
prefix: "*" # Prefix shown before nickname in chat ("" for none)
max-length: 16
name-validation-regex: "^[a-zA-Z0-9_]+$"
- New in commands.yml:
commands:
nick:
aliases: [nickname]
usage: "/%label% [nick]"
usage-others: "/%label% [nick] [player]"
- New in lang/messages/en_US.yml:
utilities:
nick:
set: "%prefix% <green>Your nickname has been set to <yellow>%nick%</yellow>.</green>"
set-for: "%prefix% <green>You set <yellow>%player%</yellow>'s nickname to <yellow>%nick%</yellow>.</green>"
set-by: "%prefix% <green><yellow>%player%</yellow> set your nickname to <yellow>%nick%</yellow>.</green>"
reset: "%prefix% <green>Your nickname has been cleared.</green>"
reset-for: "%prefix% <green>You cleared the nickname for <yellow>%player%</yellow>.</green>"
reset-by: "%prefix% <red><yellow>%player%</yellow> cleared your nickname.</red>"
errors:
too-long: "%prefix% <red>That nickname is too long! (<yellow>%length%</yellow>/<yellow>%max%</yellow> characters).</red>"
invalid-name: "%prefix% <red>Invalid nickname.</red>"
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:8VonM7S3:Kq8RneAH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8VonM7S3:Kq8RneAH"
}

