Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
ModernTags 2.0 — Major Update
⚠️ The configuration has been completely reworked and is not compatible with the previous version. Delete your old config and set up the plugin from scratch using the updated documentation.
This is the biggest update to ModernTags since its initial release. Version 2.0 introduces support for all client versions, a flexible condition system, and significantly improved compatibility with other plugins.
What's new
Support for clients below 1.19.4
A second renderer based on Scoreboard Teams has been added. The plugin automatically picks the right rendering method for each individual viewer — Text Display for 1.19.4+ clients, Scoreboard Teams for older ones. Tags are now visible to every player on the server regardless of their client version.
TAB compatibility
ModernTags 2.0 manages Scoreboard Teams internally, so you no longer need to disable TAB's nametag display to avoid conflicts.
Tags in separate files
Tags are now defined in individual files referenced from config.yml. Each file can contain both a modern and a legacy section for the respective renderers.
Condition system
The old permission-based tag selection (moderntags.tag.<name>) has been replaced by owner-conditions and viewer-conditions — flexible expressions that give you full control over which tag group is applied. Example: hasPermission('moderntags.tag.vip').
Viewer context in placeholders
The placeholder syntax has changed from <placeholder:key> to {owner:key} and {viewer:key}. This allows you to display different tag content depending on who is looking at the player.
Sneak dimming
On 1.19.4+ clients, tags now fade when the owner is crouching, matching vanilla Minecraft behavior.
Permission changes
moderntags.tag.<name> (auto-generated) and moderntags.see.other have been removed. Tag selection logic is now fully handled by the condition system.
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:FOLkjMDa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sxLqaqZP:FOLkjMDa"
}

