Links
Tags
Creators
Details
0.4+1.17.1
Compatibility
Changes
This release switches the translation to use the server-translation-api mod making it possible to translate server side instead of relying on a optional client side mod. All non-experimental functionality apart from the alias is now configurable using commands (including the defaults).
Set of changes:
- split
enablednode to set and query instead of enable and disable - remove all client side parts of the mod
- adds experimental event based backend, it can be switched to by setting
"advancedEventOptions": truein the config - add centre set query and reset commands
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:116VbfxT:3i21axue"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:116VbfxT:3i21axue"
}

