We all knew it had to happen at some point. As of right now, TAB has 40 Bukkit modules for different MC versions, lots of which are not being used by anyone anymore. Starting with 1.20.5, paper decided to make a harder fork from spigot, removing CraftBukkit relocation, requiring 2 implementations for each version - 1 for Spigot and 1 for Paper. All of this causes the plugin to take forever to compile and officially supporting versions that weren't tested for years isn't ideal either.

Eventually, I have decided to start dropping support for older MC versions on Bukkit. When and which versions is still not fully planned, but you can check the estimations below.

Players with unsupported MC versions will remain supported (either on a proxy or through ViaVersion), but plugin will no longer start on those Bukkit versions.

When MC version 26.1 comes out, TAB 6.0.0 will be released, dropping support for non-latest minor versions of

This page explains how the layout feature in TAB works and what are the problems preventing me from adding support for less than 4 columns.

Currently, TAB takes advantage of the 80 player tablist limit and therefore sends 80 fake players. They are sorted by UUID (<1.19.3), name (1.19.3 - 1.21.1) or listOrder (1.21.2+). The real players are pushed out of the tablist and not visible. This gives the plugin full control over what players see in the tablist without having to rely on other functions like teams to sort players.

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.

Main reasons for removing this feature include, but are not limited to:

• The feature was suffering from server-sided bugs, client-sided bugs, new limitations, as well as random issues, which I was not able to fix despite trying for years. Synchronization issue with the players (moving ahead / behind the player), players randomly not having their armor stands visibl

Last update: December 31st, 2022

• About
• Who is behind it
  • History with TAB
  • Their attitude towards me
  • Bug report feedback
• API
  • Lack of functions
• Non-deterministic API

This paste goes through my 5 year experience of developing the plugin, which started in 2016. It explains how it all started, what I went through, how I got to this point and why I don't want to do this anymore. It contains behind-the-scenes information and experience which end users have no idea about and most of them don't even care about.

I will not go through my whole minecraft history, I will start at the point where I decided to make my own plugins for my server. After I decided to close my last server, which was in 2016, I was left with plugin development knowledge, which I wanted to use in some way.

Back then bot attacks were a popular thing where I lived and no public plugins offered satisfying protection. I went through all available anti-bot plugins and took the best out of them. Then I decided to upload it as a paid plugin to spigot. One of the requirements is to have 3 free plugins. For that reason, I made 3 random small plugins (one of them literally had 7 lin