Tags
Creators
Details
2.2.0
Compatibility
Required content
Changes
What's New
- Built-in update management. ModernTags can check for updates at startup and optionally download them automatically. Use
/moderntags updateto check and download manually, even when startup checks or automatic downloads are disabled. Downloads are placed in the server's update folder and installed when the server restarts. - Invisible player tags in spectator mode. Viewers in spectator mode (GM3) can now see invisible players' tags with the modern renderer, just like vanilla names. This brings the modern renderer in line with Minecraft and the legacy renderer. Invisible players' tags remain hidden from ordinary viewers.
- Standard bStats metrics. Added basic usage statistics. To opt out, set
enabled: falsein the sharedplugins/bStats/config.yml; there is no separate ModernTags setting.
New Configuration Options
updates:
check: true
auto-download: false
Startup checks are enabled by default. Set auto-download: true to download updates during startup checks; a server restart is still required to install them. The manual update command remains available in either mode, but is hidden from tab completion when automatic downloads are enabled.
Permission change: moderntags.admin replaces moderntags.reload and grants access to both configuration reloads and update downloads. Operators have it by default. If you granted the old permission manually, replace it with the new one.
Bug Fixes
- No default name flash during reloads or death. Fixed the vanilla player name briefly appearing while the modern tag was being removed or recreated.
- Spectators can see other spectators' tags. Fixed spectator tags being hidden from spectator viewers; they remain hidden from ordinary viewers.
- Legacy formatting survives invisibility. Fixed prefixes and suffixes being missing after a reload while the player was invisible, including when invisibility later ended.
- Hidden legacy tags stay hidden during updates. Shared text and formatting updates no longer reveal a tag to viewers from whom it was hidden.
Dependencies
- Updated MyLib to
7d2ccd9fd9for update management. - Added bStats
3.2.1.
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:3nZAj3kp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sxLqaqZP:3nZAj3kp"
}

