FAQ
On this page11 sections
- Which servers and versions does it run on?
- Does it work on Folia?
- Do players need a resource pack or a mod?
- What do Bedrock players see?
- Does it work with TAB?
- Will an update change my nametags?
- How much bandwidth does it use?
- Can different viewers see different text?
- Where are player customisations stored?
- Does the plugin send any data?
- The console shows a licence notice
Something does not look right? See troubleshooting.
Which servers and versions does it run on?
Paper, Purpur and Folia on Minecraft 1.21.11 or newer, with PacketEvents (opens in a new tab) 2.14+. Java 21 (Minecraft 26.x needs Java 25). Spigot and CraftBukkit are not supported: the plugin uses Paper's dialogs and Brigadier commands.
Does it work on Folia?
Yes. Packet work runs on each player's network thread; the plugin never touches the world off its region thread.
Do players need a resource pack or a mod?
No. Badges, icons and faces are drawn with textures the game already has or downloads from Mojang. Players on 1.21.9+ see everything; older clients (through ViaVersion) see text versions of badges and icons, and menus need 1.21.6+ (older clients use the commands).
What do Bedrock players see?
The vanilla nametag: Geyser cannot draw display entities, so with Floodgate installed Bedrock
viewers keep vanilla nametags (compatibility.bedrock-viewers: vanilla). displays treats them
like Java players.
Does it work with TAB?
Yes, with nothing to configure: vanilla nametags are hidden by rewriting team packets per viewer, so TAB's prefixes and tab-list sorting keep working. Badges can be shown in TAB too; see integrations.
Will an update change my nametags?
No. Your templates, badges and animations are never touched; new config.yml options are added
with their defaults. See updating.
How much bandwidth does it use?
Measured with 100 players packed together (each sees the 60 nearest nametags): static nametags 0.6 KiB/s per player, looping motions 5–7 KiB/s, the richest bundled design on everyone 17 KiB/s, a rainbow text effect on everyone 31 KiB/s, all within the default 32 KiB/s budget; server tick around 5 ms. See performance tuning.
Can different viewers see different text?
No; relational (per-viewer) placeholders are not supported. Every viewer sees the same nametag.
Where are player customisations stored?
Only players with a customisation (a badge choice, a forced template, /nametag self off...) are
stored: one file per player in data/players/, or a MySQL/MariaDB table with storage.type: mysql
(networks).
Does the plugin send any data?
- Usage statistics: every 30 minutes (the first two minutes after startup) an anonymous report
is sent to
nametags.minestar.me. It contains exactly: a random server id (made up on the first start and kept indata/server-id), the plugin version, the server software and its version, the Minecraft and Java versions, the number of players online, the storage type, which of PlaceholderAPI, LuckPerms, TAB, MiniPlaceholders and Floodgate are installed, and how many templates and badges you added yourself, the message language (only if it is a bundled one), how many templates and badges are loaded and which features they use (from a fixed list of words such as "badges" or "motions"). Never player names or UUIDs, IP addresses, ports, the MOTD or any text from your files. It helps decide which versions and integrations to support, and the totals are public at https://nametags.minestar.me/stats (opens in a new tab). Turn it off withusage-statistics: falseinconfig.yml. Privacy policy: https://nametags.minestar.me/privacy (opens in a new tab) - Licence check: while the server runs, the plugin regularly tells
nametags.minestar.mewhich store download it is: the BuiltByBit buyer id, resource id, download id and download time that BuiltByBit wrote into your copy, the random server id and the plugin version. It is how copies shared against the licence are found, so it is not anonymous, and it is separate from the usage statistics and their setting. A connection problem never stops the plugin, and nothing is ever switched off while the server runs. If you setlicense-keyinconfig.yml, that key is sent too. See the console shows a licence notice. - bStats: anonymous usage statistics (server count, server software, storage type, language,
template count bucket, which integrations are used), like most plugins. Turn it off for every plugin in
plugins/bStats/config.yml. - Update check: a plain download of a small version file every six hours, without any data
about your server. Turn it off with
update-checker: falseinconfig.yml. - MineSkin: only when an admin runs
/nametag badges generate: the 8×8 badge images are uploaded to turn them into skins.
Nothing else leaves your server. Player data stays in data/ or your own database.
The console shows a licence notice
Every copy tells nametags.minestar.me which BuiltByBit download it is, and gets one of three
answers back. The plugin acts on the answer it had when the server started, never in the middle of a
session and never because the website could not be reached.
- ok: the normal case; you never see anything.
- warning ("the licence check has flagged this copy"): the same download is running on unusually many servers or networks, so it looks shared. This is automatic and the plugin keeps working exactly the same. If you bought the plugin and run a large network, tell us and we mark your licence as legitimate; the notice is gone after the next restart.
- revoked ("nametags stay off"): set by hand, only after a refund or a breach of the licence. The plugin loads but shows no nametags; nothing else on the server is affected. If this is a mistake, contact us: once it is restored the console says so, and a restart turns the nametags back on.
To contact us, use the support Discord (https://discord.gg/eXNJWeTgP5 (opens in a new tab)) or the BuiltByBit resource
page (discussion or private message) and include the
"Download" and "Licence check" lines of /nametag debug report (or, if the licence is revoked
and the command is not available, the lines the console printed at startup).
A copy that did not come from BuiltByBit (a tester, a gift, a purchase made elsewhere) gets a
key from the author: put it in license-key in config.yml and restart.