1.0.0+mod
Compatibility
Changes
Initial Beta Version
Installing the pack/mod to the server will hide all player nameplates
- Modifies the name_tag_distance attribute of all players via a one time initial tick advancement
- to clarify: the pack does not contain looping/ticking logic. only fires logic once per player the first tick that they are targetable by the server (i.e. first join / reconnect with pack enabled) under specified advancement criteria, making the logic/load similar to most any vanilla advancement
- Includes native toggle to reenable or subsequently disable nameplate visibility
- /function no_player_nametags:config/show_player_nametags
- /function no_player_nametags:config/hide_player_nametags
created this pack due to the addition of the name_tag_distance attribute in MC26.2 allowing for an implementation that does not utilize the team command, a command that commonly causes prohibitive logic conflicts with MANY other packs/mods
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:RB2JgwDW:CpoPavco"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RB2JgwDW:CpoPavco"
}

