Links
Tags
Creators
Details
2.3.0
Compatibility
Required content
Changes
Replace hardcoded error strings in ShellCommand with localized messages via LanguageManager. getBetterErrorMessage was refactored to inspect a lower-cased message and return appropriate localized keys (including network/io/unknown cases) and some messages now append the original exception text. Also updated config import/export and file save error handling to use localized "error.invalid_path" and "error.file_cannot_save" messages. Added corresponding localization keys to en.json and tr.json for: error.cannot_run_program, error.access_denied, error.permission_denied, error.file_not_found, error.invalid_path, error.file_cannot_save, error.command_not_found, error.network_error, error.io_error, and error.unknown.
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:d9Zeqv5x:iee0V6Dx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d9Zeqv5x:iee0V6Dx"
}

