6.4b
Compatibility
Changes
Fixed custom command aliases from commands-toggle.yml not executing their target commands correctly. Aliases such as /hub, /lobby, /main, /goto and /warpto now properly forward to their original commands. Fixed CommandsAPI compatibility where aliases could return Unknown command even though the target command worked. Improved command-toggle alias registration and collision handling. Removed invalid/conflicting alias mappings and corrected several outdated command names. Improved command-toggle startup/reload handling to avoid false “unavailable command” warnings.
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:KiX5RGZ1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mW41qQ0T:KiX5RGZ1"
}

