Guides
- 📚 Setup
- 📄 Config File
Documentation
- 🖥️ Commands
- 👥 Server Groups
- 🎨 Formatting
- 📛 Nametags
- 📊 Sorting
- ✍️ Placeholders
- 🔗 Relational Placeholders
- 🔀 Conditional Placeholders
- ✨ Animations
- 🖼️ Custom Logos
- 🔗 Server Links
- 📦 API
Velocitab can sort players in the TAB list by a number of "sorting elements." Sorting is enabled by default, and can be disabled with the sort_players
option in the config.yml
file.
Note:This feature requires sending Update Teams packets.send_scoreboard_packets
must be enabled in theconfig.yml
file for this to work. More details...
To modify what players are sorted by, modify the sorting_placeholders
list in the config.yml
file. This option accepts an ordered list; the first element in the list is what players will be sorted by first, with subsequent elements being used to break ties. The default sorting strategy is to sort first by %role_weight%
followed by %username%
.
# Ordered list of elements by which players should be sorted. (Correct values are both internal placeholders and (if enabled) PAPI placeholders)
sort_players_by:
- %role_weight%
- %username%
The following sorting elements are supported:
Sorting element | Description |
---|---|
Internal Placeholders | Check docs here |
PAPI Placeholders | Check docs here |
In Minecraft, the TAB list is sorted by the client; the server does not handle the actual display order of names in the list. Players are sorted first by the name of their scoreboard team, then by their name. This is why having a proxy TAB plugin sort players is a surprisingly complex feature request!
To get the client to correctly sort the TAB list, Velocitab sends fake scoreboard "Update Teams" packets to everyone in order to trick the client into thinking players on the server are members of a fake scoreboard team. The name of the fake team for sorting is based on a number of "sorting elements," which can be customized.
Velocitab has a few optimizations in place to reduce the number of packets sent; if you update frequently sorting element placeholders, do note this will lead to more packets being sent between clients and the proxy as the teams will need to be updated more regularly. This can lead to an observable increase in network traffic—listing fewer sorting elements in the sort_players_by
section will reduce the number of packets sent.
There are a few compatibility caveats to bear in mind with sorting players in the TAB list:
In these cases, you may need to disable the use of scoreboard packets through the send_scoreboard_packets
option detailed earlier.