Tags
Creators
Details
2.1.0
Compatibility
Required content
Changes
What's New
- Relational placeholders. Nametags can now show different information depending on who is looking at the player. Use
{rel:...}with a relational PlaceholderAPI expansion. For example, an expansion that provides ally/enemy relationships can display a different status to each viewer. - Tags respond to condition changes. When a player's permissions or other tag conditions change, ModernTags can automatically switch to the correct tag. Players no longer need to teleport or rejoin just to see the change.
- Tags can be hidden when nothing matches. A fallback tag is no longer required: if no configured conditions match, no custom tag is displayed.
- Dynamic text colors and styles. The updated GikyMessage library now lets you change a tagβs text color or style using placeholder values, for example:
[text](color:{placeholder})or[text](style:{placeholder}). Formatting can change automatically as the placeholder value updates.
New Configuration Option
conditions-recheck-rate: 20 controls how often tag conditions are checked (in plugin ticks). The default is 20; set it to -1 to disable periodic checks. Conditions will still be evaluated when a tag is initially rendered or refreshed by an event.
Bug Fixes
- Static tags update properly. Placeholders now refresh even when a tag has only one animation frame.
- All affected players receive updates. Fixed cases where only some players using the same tag configuration were updated.
- More consistent visibility. Fixed tags appearing incorrectly when a player is invisible, crouching, or no longer supposed to have a visible tag.
- Correct text opacity. Opacity is now applied properly when animation frames change.
- More flexible conditions. Spaces before
&&and||no longer cause condition parsing errors. - More reliable rendering. Improved handling of concurrent tag updates and errors during processing.
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:sxLqaqZP:CXp5xiX9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sxLqaqZP:CXp5xiX9"
}

