2.0.0
Compatibility
Changes
Rewrote backend
3 years ago when i initially wrote this plugin, I had no sense of what good code was whatsoever
This overhaul is to remedy that, here are some things that are new:
- no more data.yml Minecraft maps are stored via their 'id' (which is the number you see when you hover over the map item). Prior to this update, a data.yml file was created to store each id managed by the plugin and the file path to its corresponding image. This was just straight up bad... for one you couldn't move the server to another part on the computer without manually updating the file paths.. secondly, it's just dumb, you can easily store the id in the file name Thank you to SlyCedix for pointing this out to me
- optimized image storage Maps in Minecraft are always rendered at a resolution of 128x128, hence making it pointless to store any image of higher res to that. Hopefully this change can reduce the storage requirement by a good amount
Many things have changed on the backend and hopefully it should lead to a more optimized experience overall (at least a little bit)
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:m5SeVW9J"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PGfwpFcp:m5SeVW9J"
}

