Skip to content

Instantly share code, notes, and snippets.

@NEZNAMY
Last active September 18, 2024 18:16
Show Gist options
  • Save NEZNAMY/f4cabf2fd9251a836b5eb877720dee5c to your computer and use it in GitHub Desktop.
Save NEZNAMY/f4cabf2fd9251a836b5eb877720dee5c to your computer and use it in GitHub Desktop.
The removal of unlimited nametag feature

About

Unlimited nametag feature hides original nametags and display armor stands instead. It was created back in MC 1.12, where we were actively suffering from 16 character limit in prefix and suffix. The very next version mojang removed the limit. Had they done it 1 version sooner, this feature may have never existed. It has unlocked a lot more than just that, and has become quite popular (about 20% of servers using TAB have it enabled). However, as time goes by, this feature is becoming more and more complicated to maintain, which made me decide to completely remove it. It was a good run, but I don't want to keep going.

Reasons for removal

Main reasons for removing this feature include:

  • Code is becoming more and more complicated, especially to support all MC versions.
  • There are tons of totally random bugs which I have no idea how to fix, as well as server bugs preventing it from working properly.
  • Mojang is (albeit extremely slowly) making this feature less and less useful with less and less limits in vanilla nametags.
  • People constantly keep asking the same questions over and over (top question being why they cannot see them with F5), making it by far the highest time investment into the feature (far more than coding itself)

What's next

  • As of TAB 4.1.6 (Released with MC 1.21), this feature will be marked for removal:
    • NO support will be provided
    • All wiki references will be deleted (besides the feature page itself, which will have a warning on top)
    • No bugs will be fixed anymore and all existing bug reports will be closed
  • A new branch called 5.0.0 was created, which has the feature removed. This branch will become the active one.
  • 4.x branch will no longer be actively maintained, only receiving support for new MC versions and critical bugfixes (in other features)
  • Github actions will only contain dev builds of 5.0.0 version, instead of 4.x
  • When MC 1.22 hits (expected date is June 2025), version 5.0.0 will be released, fully removing the feature
  • 4.x branch will only receive updates for new MC versions without any other changes and stay on github to compile for anyone who still wants the feature and doesn't care about anything else

What can you do?

Let's go through all ways you can deal with this:

  • Find alternative way to display information using existing features:
    • 16 character limit on <1.13 - Update to 1.13+
    • Belowname limits - Update to 1.20.3+
    • Multiple lines - You'll need to display everything you want in just 2 (almost) fully customizable lines instead. It's enough to display everything important (prefix, suffix and Belowname).
    • RGB Username - Beg mojang to add hex support to team color
    • Changing player name - There are nick plugins that offer this (actually changing player's name in game profile and sending modified packet), although I am not aware of any good one. This is a very complicated process with tons of side effects that need to be accounted for, so it will not be added into the plugin.
  • Stay on TAB 4.x. If you are stuck on MC versions older than their player base, you can also just keep your plugins outdated as well. The plugin works and currently doesn't have a single bug affecting Bukkit installation, so you won't be hurting at all. Even if one is found, it will be fixed. We still have a year to go afterall.
  • Look for alternative plugins willing to deal with this mess. You can check these 3rd party plugins out (not affiliated with me in any way, use at your own risk):

Feedback

While nothing you can say will change my mind, you can share your feedback below, such as questions or things I made unclear or forgot.

@NEZNAMY
Copy link
Author

NEZNAMY commented Jul 11, 2024

i am on 1.20.6, but the only way i know how to set a nametag is with player profiles, which have a 16 character limit

Yes, player names are still limited. You can change them with game profile, but prefix/suffix is still an available feature.

@MCdragonmasters
Copy link

MCdragonmasters commented Jul 11, 2024

i am on 1.20.6, but the only way i know how to set a nametag is with player profiles, which have a 16 character limit

Yes, player names are still limited. You can change them with game profile, but prefix/suffix is still an available feature.

but i have prefixes that have a gradient across the player's entire name which team prefixes cannot do

@NEZNAMY
Copy link
Author

NEZNAMY commented Jul 11, 2024

Unfortunately you'll lose this feature. You can stay on 4.x. You still don't have to worry about it for a year, at which point it is highly unlikely you will still be running the server considering average server lifespan. If you will still be around, you will still be able to compile it yourself.

@JULJERYT
Copy link

I have been using this feature for 3 years now. I will miss it.
jujer
(it means certified sigma)

@MCdragonmasters
Copy link

bruh what i have it enabled in config and have restarted the server multiple times
image

@NEZNAMY
Copy link
Author

NEZNAMY commented Jul 12, 2024

bruh what i have it enabled in config and have restarted the server multiple times image

You probably disabled its parent feature - scoreboard-teams. What does that have to do with future removal of this feature?

@tbm00
Copy link

tbm00 commented Jul 13, 2024

Unfortunately you'll lose this feature. You can stay on 4.x. You still don't have to worry about it for a year, at which point it is highly unlikely you will still be running the server considering average server lifespan. If you will still be around, you will still be able to compile it yourself.

I appreciate you giving the heads up to us server owners. However, just because a lot of servers end quickly, doesn't mean nice, long lasting servers don't use and appreciate this feature... It's very wack for you to vindicate the removal of this feature because the average server lifespan is short.. I understand and respect your other reasons, and appreciate your work. But that specifically is not valid.

I don't care about for any new features, so I will compile the old version myself when updating to 1.22. Thank you for providing that!

@NEZNAMY
Copy link
Author

NEZNAMY commented Jul 13, 2024

I didn't say I'm removing it because servers shut down quickly, I just see it as another way of dealing with it - users forgetting (old ones leaving and new ones never finding out).

@Sv3r
Copy link

Sv3r commented Jul 14, 2024

I was mainly using it to use custom colors in nametags, is it even possible without it? Seems like it just gets changed to the closest vanilla color there is.

@NEZNAMY
Copy link
Author

NEZNAMY commented Jul 14, 2024

I was mainly using it to use custom colors in nametags, is it even possible without it? Seems like it just gets changed to the closest vanilla color there is.

Yes, just legacy colors, it's also explained in the main message, as well as wiki.

@JericNisperos
Copy link

I don't think this won't affect the users too much. Since TAB still offers Belowname feature. I think one option you might want to consider is to expand the Belowname feature. Similar to how scoreboard was created, you can apply the same feature like adding a condition and shows a different belowname value. This may not provide multiple lines but this will definitely resolve the issue where you can display different information based on the condition, example, if you are on specific world.

@NEZNAMY
Copy link
Author

NEZNAMY commented Jul 24, 2024

I don't think this won't affect the users too much. Since TAB still offers Belowname feature. I think one option you might want to consider is to expand the Belowname feature. Similar to how scoreboard was created, you can apply the same feature like adding a condition and shows a different belowname value. This may not provide multiple lines but this will definitely resolve the issue where you can display different information based on the condition, example, if you are on specific world.

Conditional placeholders are supported in both text and number/fancy display.

@NEZNAMY
Copy link
Author

NEZNAMY commented Jul 29, 2024

How then can we display the player's hex color without this function?

The original message says you cannot. Mojang will need to add it.

@cloakfox
Copy link

Very sad to hear that this key feature is getting removed from TAB, I have been using it for years and is one of the only reasons I ever switched to TAB.

@Kanin
Copy link

Kanin commented Aug 24, 2024

No, I tried going premium, y'all have showed me a middle finger. I don't want to do that feature anymore, free nor paid.

Coming from one of the nearly 3 thousand people who bought this plugin (according to BBB purchases), this is upsetting to hear. What do you consider a middle finger?

@NEZNAMY
Copy link
Author

NEZNAMY commented Aug 24, 2024

No, I tried going premium, y'all have showed me a middle finger. I don't want to do that feature anymore, free nor paid.

Coming from one of the nearly 3 thousand people who bought this plugin (according to BBB purchases), this is upsetting to hear. What do you consider a middle finger?

  • Using sites like blackspigot to get the premium version without paying.
  • Pushing me into making the plugin opensource, so they can compile the premium version by themselves, then arguing I am obligates to provide support for premium features to people who didn't buy it, because they compiled it without buying.
  • Telling me they have no intention of buying the premium version, because the free one has everything they need, missing the point of premium version's existence in the first place.
  • Demanding support for premium features without verifying as buyers first, making random excuses like "I can't verify right now", "My friend bought it", "Just answer me pls".
  • Gaslighting me into helping them with premium features without buying it first, saying they won't buy something that's buggy. When I magically fixed the bug by editing their config, they obviously never bought it after (I even exposed some of these people in a different gist).
  • After moving over to free plugin with paid support model, people asked for refunds because they now no longer have any advantages as they believe they will not need support anymore (these people usually opened above 5 tickets in the past).
  • When free users asked for help, I refused and explained them, I got call bad words and was wished death. I had to argue with them for a long time and only if I was able to win thee argument some of them considered buying it. Imagine if you had a 1-hour argument with your boss every single day of your life explaining why you believe you should be paid for going to work. You'd probably leave immediately.
  • Free users are hiding support requests as bug reports, saying they won't pay for support, because it's not asking for help, but reporting a bug (never ever was it an actual bug). Check closed github issues. Almost every single one of them was closed as "plugin works as described" or "caused by another software".
  • Arguing with free users always took way longer than it would have taken to actually answer their trivial question answered everywhere over the wiki.
  • Random refunds after people get what they paid for.
  • Not to mention the endless problems with paypal banning spigot devs, complicated af taxes in my country and more.

I can't put years of experience into a few sentences, but I hope you are starting to understand what it's like being on the other side.

@Kanin
Copy link

Kanin commented Aug 25, 2024

No, I tried going premium, y'all have showed me a middle finger. I don't want to do that feature anymore, free nor paid.

Coming from one of the nearly 3 thousand people who bought this plugin (according to BBB purchases), this is upsetting to hear. What do you consider a middle finger?

  • Using sites like blackspigot to get the premium version without paying.
  • Pushing me into making the plugin opensource, so they can compile the premium version by themselves, then arguing I am obligates to provide support for premium features to people who didn't buy it, because they compiled it without buying.
  • Telling me they have no intention of buying the premium version, because the free one has everything they need, missing the point of premium version's existence in the first place.
  • Demanding support for premium features without verifying as buyers first, making random excuses like "I can't verify right now", "My friend bought it", "Just answer me pls".
  • Gaslighting me into helping them with premium features without buying it first, saying they won't buy something that's buggy. When I magically fixed the bug by editing their config, they obviously never bought it after (I even exposed some of these people in a different gist).
  • After moving over to free plugin with paid support model, people asked for refunds because they now no longer have any advantages as they believe they will not need support anymore (these people usually opened above 5 tickets in the past).
  • When free users asked for help, I refused and explained them, I got call bad words and was wished death. I had to argue with them for a long time and only if I was able to win thee argument some of them considered buying it. Imagine if you had a 1-hour argument with your boss every single day of your life explaining why you believe you should be paid for going to work. You'd probably leave immediately.
  • Free users are hiding support requests as bug reports, saying they won't pay for support, because it's not asking for help, but reporting a bug (never ever was it an actual bug). Check closed github issues. Almost every single one of them was closed as "plugin works as described" or "caused by another software".
  • Arguing with free users always took way longer than it would have taken to actually answer their trivial question answered everywhere over the wiki.
  • Random refunds after people get what they paid for.
  • Not to mention the endless problems with paypal banning spigot devs, complicated af taxes in my country and more.

I can't put years of experience into a few sentences, but I hope you are starting to understand what it's like being on the other side.

As a developer, I understand a large portion of the other side and I can assure you it happens to the majority of devs (not even just in the Minecraft sphere). I've grown to just ignore these users, as there's simply some people you cannot help. It's not your responsibility to provide exactly what they want, expect, or desire... paid or free. It's just upsetting that you let these bad actors affect the experience of those of us who did actually decide to buy your plugin and support you directly. However I do understand the refund/tax issues, that is a pain in the ass to deal with.

At the end of the day I support you and your plugin, it's been by far the best tab plugin for many, many years. I just wish you wouldn't specifically call out those of us who supported you in such a way, we aren't all the customer you described.

@NEZNAMY
Copy link
Author

NEZNAMY commented Aug 25, 2024

I was implicitly talking about free users here though. The user suggested making a paid version, suggesting people would buy it = they didn't buy it yet, therefore referring to free users as well.

@Yohhannn
Copy link

God damn. Been using this feature for the years now and it will be removed? I wouldn't mind buying it as a premium to keep that type of feature. <3

@NEZNAMY
Copy link
Author

NEZNAMY commented Aug 31, 2024

God damn. Been using this feature for the years now and it will be removed? I wouldn't mind buying it as a premium to keep that type of feature. <3

You had over 3 years to buy it while the plugin was for sale, you didn't (I assume based on the way you're talking). The plugin linked in the post as an alternative is (unfortunately) paid, so it pretty much matches your criteria.
Alternatively, stay on 4.x, it will still be updated to new MC versions and you can pay someone to fix issues in the feature, also matching your criteria.

@jared27906
Copy link

Why not use display entities for the unlimited nametags?, it looks like its gonna be easy to implement since you just make the display ride the player then offset it with the transform, plus you get alot of options and its pretty much performance friendly

@NEZNAMY
Copy link
Author

NEZNAMY commented Sep 7, 2024

Why not use display entities for the unlimited nametags?, it looks like its gonna be easy to implement since you just make the display ride the player then offset it with the transform, plus you get alot of options and its pretty much performance friendly

Riding means a bunch of other issues, especially with riding plugins. Display entities are 1.19.4+ only, this feature mostly makes sense for legacy servers only, so it cannot be done. It would not really solve much either.

@Matt-MX
Copy link

Matt-MX commented Sep 14, 2024

UnlimitedNameTags went premium for commercial usage so I created my own resource here.

@NEZNAMY
Copy link
Author

NEZNAMY commented Sep 14, 2024

UnlimitedNameTags went premium for commercial usage so I created my own resource here.

Your source code does not compile and you don't offer any download links either. I can't link your resource.

@Matt-MX
Copy link

Matt-MX commented Sep 17, 2024

UnlimitedNameTags went premium for commercial usage so I created my own resource here.

Your source code does not compile and you don't offer any download links either. I can't link your resource.

Should be all sorted now! Downloads are available on the Releases page and the build issues have been resolved.

@TomLewis
Copy link

UnlimitedNameTags went premium for commercial usage so I created my own resource here.

awesome, we now have 2 options! thanks!

@Avenred
Copy link

Avenred commented Sep 18, 2024

What's the character limit for usernames past version 1.13? Also, can you hex color the prefix and suffix that go before vanilla nametags, or are those limited to the default /team colors?

@NEZNAMY
Copy link
Author

NEZNAMY commented Sep 18, 2024

What's the character limit for usernames past version 1.13? Also, can you hex color the prefix and suffix that go before vanilla nametags, or are those limited to the default /team colors?

There is no limit on 1.13+. RGB is supported too (1.16+).

@Avenred
Copy link

Avenred commented Sep 18, 2024

Awesome! So is it just the username itself that cannot be changed beyond the default team colors?

@NEZNAMY
Copy link
Author

NEZNAMY commented Sep 18, 2024

Awesome! So is it just the username itself that cannot be changed beyond the default team colors?

Yes. See limitations for more info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment