Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 3 weeks ago
All versions
2.0.0+1.19.2-forge
Beta
Item Descriptions 2.0.0+1.19.2last year 31
Compatibility
Minecraft: Java Edition
1.19.2–1.19.4
Platform
Forge
Supported environments
Client-side
Changes
Note: Due to issues with Architectury Loom, support for 2.0 versions on MinecraftForge will be limited.
Added
- Enchantment Descriptions have been added, allowing for enchantments to be described in a consistent style. This is automatically disabled when other mods with the same feature are present.
- Item Descriptions primarily uses its own keys, but will fall back to ones designed for Enchantment Descriptions if not present.
- Tooltips are now wrapped based off of pixel width, instead of number of characters. This should make their length more consistent. (@sisby-folk)
- Tags are now sorted based off mod namespaces, not just length. Modded tags are assumed to be the most specific, followed by vanilla tags, followed by common tags. This should fix some odd tagging behaviour with blocks like wool and items like swords and axes.
- Entity style translation keys now work for blocks and items as well, allowing for more specific key matching. This is primarily useful for matching against blocks and items with the same identifier. (
block.minecraft.oak_sign.descriptioninstead oflore.minecraft.oak_sign)
Changed
- Hinting is no longer shown when an item has no available key.
- Cleaned up large parts of internal logic.
Fixed
- New wrapping logic should prevent double wrapping in EMI.
- Missing tool tag descriptions on Fabric 1.19 and 1.20.
Removed
- Legacy string matching code.
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:UaizcMKP:uXm8WeFd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UaizcMKP:uXm8WeFd"
}

