Tags
Creators
Details
1.32.0
Compatibility
Changes
[CHORE] Update AstraLibs to 3.49.0\n[CHORE] Bump version to 1.32.0\n[FEAT] Parse texts with AutoComponentSerializer
Item names come from anvils, so they are escaped before they reach a message: otherwise a seller could send the buyer a clickable command.\n[FEAT] Switch texts to AutoComponentSerializer (#145)
-
[CHORE] Update AstraLibs to 3.49.0
-
[CHORE] Bump version to 1.32.0
-
[FEAT] Parse texts with AutoComponentSerializer
Item names come from anvils, so they are escaped before they reach a message: otherwise a seller could send the buyer a clickable command.
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:JodGTmt1:RKXjMyPg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JodGTmt1:RKXjMyPg"
}

