6.4
Compatibility
Changes
This update brings several improvements to the Alias module, including dynamic tab completion and some internal cleanup.
✨ Dynamic Player Tab Completion custom-tabs can now dynamically suggest currently online players using:
custom-tabs:
- "[players]" [players] is resolved live whenever tab completion is requested, so players who join or leave are reflected instantly without needing /oereload.
You can also mix dynamic players with normal static suggestions:
custom-tabs:
- "[players],console" And regular static tabs continue working exactly as before:
custom-tabs:
- "give,take" Compatibility [playerName] can also be used inside custom-tabs as a compatibility alias for [players].
custom-tabs:
- "[playerName]" This does not change the existing behavior of [playerName] inside alias commands.
️ Other Improvements Player suggestions are now sorted case-insensitively Duplicate suggestions are automatically removed Prefix filtering still works normally Zero online players are handled safely Player suggestions are no longer cached at config load PlaceholderAPI handling in the Alias module now uses the direct API instead of reflection Improved exception handling Failures while extracting the default aliases.yml are now properly logged instead of silently ignored Added documentation and examples to aliases.yml Example:
[code=YAML]playerinfo: enabled: true run-as: PLAYER commands:
- "msg $1 Hello!" add-tabs: true custom-tabs:
- "[players]" The alias system remains fully backwards compatible with existing static custom-tabs configurations.[/code]
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:mW41qQ0T:WYC2ZwMo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mW41qQ0T:WYC2ZwMo"
}

