Creators
Details
1.1.4
Compatibility
Changes
Fixed
-
All
/fsubcommands broken when TeamsAPI is absent:FactionCommandExecutorandFactionTabCompleterheld directimportstatements for TeamsAPI classes. On Paper's isolated plugin classloader this causedNoClassDefFoundErrorat class-load time when TeamsAPI was not installed, preventing the executor from being registered and making every/f <subcommand>(including/f info,/f map, etc.) fail with "Invalid command!".Introduced
TeamsCommandBridge(no TeamsAPI imports, loaded unconditionally) andTeamsCommandBridgeImpl(imports TeamsAPI, instantiated only via reflection when TeamsAPI is confirmed present). Mirrors the existingTeamsApiRegistrarisolation pattern. With TeamsAPI absent the bridge isnulland all subcommands route through the localCommandRegistryas intended.
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:trDfzeaq:ihooJiJj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:trDfzeaq:ihooJiJj"
}

