Tags
Creators
Details
1.9.0
Compatibility
Changes
Hello!
Your existing configuration will be migrated automatically. It is recommended to back up your configuration before updating.
This update adds tag categories, per-tag GUI customisation, MiniMessage formatting and several menu improvements. Read below for more information.
Additions:
-
Added tag categories.
- Assign tags to categories using the new
categoryoption. - Categories can have their own item, name, lore, display order and GUI title.
- Added the reserved
allcategory for viewing every available tag. - Tags without a category are automatically placed in the
generalcategory. - The category selection page is only shown when a player has permission to view tags in more than one category. Otherwise, it is skipped and the available category opens directly.
- Assign tags to categories using the new
-
Added the
%deluxetags_category_amount%placeholder, which displays the number of tags available to the player in the current category. -
Added per-tag GUI items.
- Each tag can now define its own
displayname,description,itemanddata. - Tag descriptions can now contain multiple lore lines.
- Each tag can now define its own
-
Added MiniMessage support.
- Enable it using
use_minimessage: true. - Supports modern formatting such as gradients and other MiniMessage tags.
- Enable it using
-
Added modern item model options for GUI items:
item_modelmodel_datamodel_data_component
-
Added the configurable
gui.category_back_itembutton. -
PLAYER_HEADitems used for the current-tag display now show the player’s skin.
Changes:
- The update checker now uses Modrinth.
- Refreshed and reorganised the default configuration.
- Existing
gui.tag_select_itemsettings are automatically migrated to the new per-tag format. - Existing tags without a category are automatically assigned to
general. - Fixed various smaller bugs.
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:wtpLgugo:xuwIvpOR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wtpLgugo:xuwIvpOR"
}

