4.9
Compatibility
Changes
Item frames, very cool
You can now specify in the command whether or not you want to receive Item Frames (or Glow Item Frames) along with your maps.
This can be disabled in the config (for specifically Item Frames or Glow Item Frames) and access can also be limited through permissions (also on a per Frame type basis.)
These are the useless things I do when I get too much time to myself..
Permission Nodes:
imagemaprenderer.map
description: allows player to run the /map command default: true
imagemaprenderer.itemFrames
description: allows player to receive Item Frames when they render map(s) default: true
imagemaprenderer.glowItemFrames
description: allows player to receive Glow Item Frames when they render map(s) default: true
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:emXrVHua"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PGfwpFcp:emXrVHua"
}

