Tags
Creators
Details
2.0.2
Compatibility
Required content
Changes
šØ Atlas Sprite Icons (Minecraft 1.21.9+) The biggest feature addition: inline item and block icons rendered directly in chat, titles, action bars, boss bars, and all other text contexts using Minecraft's new object text component. New syntax for players in chat:
[#item] ā shows the atlas sprite icon of your held item + its name [#item:3] ā same for predefined item slot 3 [##item] ā shows only the icon (no name) of your held item [##item:3] ā icon only for predefined slot 3 [#diamond] ā shows any named sprite inline (block names, item names)
Custom placeholder icon syntax:
[spawn] ā text only, even if icon: is set in placeholders.yml [#spawn] ā shows the configured icon + text [##spawn] ā shows only the configured icon
Permission nodes added:
chatmod.chatitem.icon ā use [#item] / [#item:N] chatmod.chatitem.icon_only ā use [##item] / [##item:N] chatmod.chaticon ā use [#SpriteName] in chat
š New sprites.yml config A new configuration file that maps short alias names to full atlas sprite paths. Lets admins define grass: "block/grass_block_side" so players can type [#grass] instead of the full path. Ships with aliases for common blocks, items, and the three special entity sprites available in the blocks atlas. Reference link included: https://www.gamergeeks.net/apps/minecraft/list-of-atlas-sprites
š¢ Broadcasts ā Full placeholder support All [] placeholder syntaxes now work in every broadcast type including /cm bcnow, predefined broadcasts, and the cycling legacy broadcaster ā across CHAT, ACTION_BAR, TITLE, and BOSSBAR display types.
[spawn], [discord] and all custom placeholders now expand in broadcast messages [item:N] (predefined slot items) now render correctly in broadcasts even without a player context [#item] and [##item] in /cm bcnow and scheduled broadcasts now resolve to the held item of the player who issued the command
Optional dependencies
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:UeyZY1Lc:XnjIf2j2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UeyZY1Lc:XnjIf2j2"
}

