Logo
MINECRAFTBIBLE
Items
Items

All game items

Blocks
Blocks

Building blocks

Mobs
Mobs

Creatures & monsters

Biomes
Biomes

World biomes

Structures
Structures

Generated structures

Recipes
Recipes

Crafting guides

Advancements
Advancements

Achievements

Loot Tables
Loot Tables

Drop rates

Tags
Tags

Item groupings

All Versions
View all data →
Capes
Cape ArchiveNEW

Browse rare Minecon capes, OptiFine capes, and custom capes from players worldwide

Browse

Player Database
Player DatabasePopular

Search any player

Skin Browser
Skin Browser

Browse & download skins

Cape Gallery
Cape GalleryNEW

Minecon & OptiFine capes

Seed Vault
Seed Vault

Curated seeds

Learn

Guides
GuidesNew

Tutorials & tips

Blog
Blog

News & updates

Community

Community Hub
Community HubHub

Posts, discussions & more

All Versions
View community →
Seed Analyzer
Seed Analyzer

World seed analysis

Loot Explorer
Loot Explorer

Drop rates

Crafting Calculator
Crafting Calculator

Material planning

Enchant Calculator
Enchant Calculator

Probability math

Redstone Lab
Redstone Lab

Signal timing

Trading Profit
Trading Profit

Villager ROI

All Versions
View all tools →
Mods
Mods

Browse all mods

Plugins
Plugins

Server plugins

Resource Packs
Resource Packs

Textures & sounds

Shaders
Shaders

Visual enhancements

Datapacks
Datapacks

World logic

Scanner
Mod Intelligence

Scan & analyze any mod

All Versions
View all mods →
Loading...
IntroductionIntroductionVersion HistoryVersion HistoryGuidesGuidesBlog & NewsBlog & News
ItemsItemsBlocksBlocksMobsMobsRecipesRecipesBiomesBiomesStructuresStructuresAdvancementsAdvancementsLoot TablesLoot TablesTagsTags
ModsModsPluginsPluginsResource PacksResource PacksShadersShadersDatapacksDatapacks

MinecraftBible

The Ultimate Wiki

Logo
MINECRAFTBIBLE

The ultimate Minecraft reference. Every item, block, mob, and recipe documented with precision.

Community

  • Player Database
  • Skin Browser
  • Cape Gallery
  • Community Hub
  • Seed Vault

Database

  • Items
  • Blocks
  • Mobs
  • Recipes
  • Biomes
  • Structures

Tools

  • Seed Analyzer
  • Mod Intelligence
  • Crafting Calculator
  • Enchant Calculator

Mods & Packs

  • Mods
  • Plugins
  • Resource Packs
  • Shaders
  • Datapacks

© 2026 MinecraftBible. Not affiliated with Mojang or Microsoft.

PrivacyTermsContact
CustomNameTags
ModMIT

CustomNameTags

This mod provides you with a way to customize your player's name tags completely server-side with no need for any client mods.

12.2K
Downloads
46
Followers
4 months ago
Updated
📦
28
Versions
managementsocialutilityfabric
Download Latestv1.2.0+1.21.11View on Modrinth

📖About CustomNameTags

CustomNameTags

This mod provides you with a way to customize your player's
name tags completely server-side with no need for any client mods.

nametags.png

Commands

You are able to do some basic actions from within the game with the /nametag
command, this requires permission level 2 or if you are using a permissions mod
you can have the permission "customnametags.command.nametag".

/nametag create <identifier> <text>

This creates a nametag with a given identifier and text, this supports the
placeholder api.

/nametag delete <identifier>

This deletes a given nametag with identifier.

/nametag reload

This reloads the config file.

Configuration

This mod allows a high level of customization, from the text being
displayed, whether it is being displayed and who it can be displayed to.

All of this is configured using a json located in config/CustomNameTags/config.json.
The above image used the following configuration:

{
  "nametags": [
    {
      "id": "example:admin_name",
      "update_interval": -1,
      "literal": "[Admin] <rainbow>%player:displayname_visual%<rainbow> ",
      "observee_predicate": {
        "type": "operator",
        "operator": 4
      }
    },
    {
      "id": "example:name",
      "update_interval": -1,
      "literal": "[Player] %player:displayname_visual%",
      "observee_predicate": {
        "type": "negate",
        "value": {
          "type": "operator",
          "operator": 4
        }
      }
    },
    {
      "id": "example:held_item",
      "update_interval": 1,
      "literal": "Holding: <green>%player:equipment_slot mainhand%</green>",
      "observee_predicate": {
        "type": "negate",
        "value": {
          "type": "entity",
          "value": {
            "equipment": {
              "mainhand": {
                "items": [
                  "minecraft:air"
                ]
              }
            }
          }
        }
      }
    },
    {
      "id": "example:data",
      "update_interval": 1,
      "literal": "%player:health%♥ %player:hunger%🍖 %player:statistic minecraft:killed minecraft:player%⚔ %player:statistic minecraft:deaths%\uD83D\uDC80"
    }
  ]
}

Creating a Nametag

In the config json, there will be an array which contains all the nametags
that will be displayed for your players. Each nametag is its own object.

Let's have a look at what makes up a nametag:

"id"

This is the identifier unique to your nametag, and follows this convention:
"namespace:name".

"update_interval"

This is the interval at which the nametag will be updated, in ticks.
Set to -1 if your nametag doesn't need to be updated.

"literal"

This is the text that will be displayed on your nametag. This supports
the placeholder api,
which means you can add contextual data.

For example "%player:displayname" which will insert the display name of the current player.
For all the details reference the placeholder api.

"visible_radius", "hidden_radius"

These two settings specify a range where the nametag will be visible to other players.

Set these to a negative value to disable them.

For example, if you only wanted players in range from a 5.3 to 10.7 block radius to see each others nametags,
you can set:

{
  // ...
  "hidden_radius": 5.3,
  "visible_radius": 10.7,
  // ...
}

"observee_predicate"

This is optional and doesn't need to be defined, but if defined will allow
you to decide which players will have this given nametag.

For example, in the example, above only operators are given the "example:admin_name"
nametag and only non-operators are given the "example:name" nametag.

This uses the predicate api;
you can view the documentation for more details about what predicates you
can define.

"observer_predicate"

This is optional and doesn't need to be defined, but if defined will determine
whether an observing player will be able to see this nametag.

This uses the predicate api;
you can view the documentation for more details about what predicates you
can define.

Caveats

There are some limitations of CustomNameTags, while for almost all the cases
the nametags will behave as expected, there are inconsistencies with the
custom nametags.

  • When players press F1 to hide their HUD player custom nametags will remain visible.
  • If the player is part of a team, their normal nametag will render.
    • This can be solved by hiding all nametags for the given team:
    • /team modify <team> nametagVisibility never

👥 Team & Contributors

senseiwells
senseiwellsOwner

⚙️ Compatibility

Environment
🖥️ Server-side
Loaders
fabric
Minecraft Versions
1.21.11

🔗 Links

Modrinth Page