1.4.0
Compatibility
Changes
- Adds a new type of configuration for prefixes, 'layout'
Layout (layout)
This is a list of strings. Each string will be a new line in the item's lore. If this is provided and is not empty, this will overwrite the default layout of the prefix item. Each item will have their own unique layout. Layout Placeholders:
<prefix_id>- The prefix's ID as listed in prefixes.yml.<prefix>- The prefix itself.<unlocked>- The Unlocked / Locked text. This defaults to[](Empty List).
Example
custom_layout:
display-name: "<green>Fancy Layouts!</green>"
description:
- "This section is effectively ignored with custom layouts."
prefix: "<white>[<green>LAYOUTS</green>]</white>"
layout:
- "<blue>Prefix ID:</blue> <prefix_id>"
- "It looks like this: <prefix>"
- "<gray> โ I snuck this in here, how weird!"
- "<yellow>Unlock State:<yellow> <unlocked>"
- "<blue>Line 1 Description"
- "Line 2 Description"
- "<red>Line 3 Description"
- " "
- "<green>Hi I wanted to skip another line."
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:1K3zR1bu:e297tLl5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1K3zR1bu:e297tLl5"
}

