4.7
Compatibility
Changes
"Minor bug fixes" -every developer ever when changing the entire underlying framework
jkjk, actual bug fixes
-You now do not break everything when running the "map" command from a console
-When rendering an image onto a grid of more than 1 map, it will only send the confirmation message once (instead of per every map rendered)
Of course if you find any bugs and/or want something added, let me know and I'll try
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:PGfwpFcp:Gjyk48Jn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PGfwpFcp:Gjyk48Jn"
}

