On this page
- Choose the display areas you need
- 1. TAB
- What it handles well
- Who it suits and what to check
- 2. SimpleScore
- What it handles well
- Who it suits and what to check
- 3. LuckTAB
- What it handles well
- Who it suits and what to check
- 4. DonutScoreboard
- What it handles well
- Who it suits and what to check
- Test a readable sidebar before adding animations
- Check sidebar toggles before telling players what to type
Key takeaways
5- TAB covers tab lists, nametags, sidebars and bossbars; its sidebar starts disabled.
- SimpleScore focuses on sidebars, with permission, world and region-based selection.
- LuckTAB requires LuckPerms and coordinates several displays around its groups.
- DonutScoreboard focuses on a styled sidebar with animations and network-synced player preferences.
- Build a small plain-text board, test its selection rules, then add placeholders and animations.
For a lobby or survival server, choosing a display plugin starts with deciding what players need to see: a tab list, rank nametags, a sidebar, or several of these together. This comparison explains where TAB, SimpleScore, LuckTAB and DonutScoreboard fit, then gives you a practical way to test your shortlist.
Choose the display areas you need
These four plugins overlap, but they do not cover identical jobs. TAB and LuckTAB cover several display areas, while SimpleScore and DonutScoreboard focus on the sidebar. Our team recommends choosing by the areas you want to control before comparing animations or colours.
| Plugin | Main coverage | Requirements or integrations to check | Licence |
|---|---|---|---|
| TAB | Tab list, nametags, header and footer, sidebar and bossbars | PlaceholderAPI for wiki examples that use its placeholders; separate proxy installation guidance | Apache-2.0 |
| SimpleScore | Animated sidebar scoreboards | Java 8 or above; optional PlaceholderAPI and WorldGuard | MIT |
| LuckTAB | Tab list, nametags, chat formatting and sidebar | LuckPerms required; Java 21 and Paper or Spigot 1.21+ stated as requirements | GPL-3.0 |
| DonutScoreboard | Configurable sidebar with animations and conditional boards | Optional PlaceholderAPI and Vault | All Rights Reserved |
1. TAB
TAB combines player-list formatting, nametags, header and footer text, sidebar scoreboards, bossbars and per-world player lists.
What it handles well
TAB suits an owner who wants several displays managed through one project. Its wiki covers sorting, animations, conditional placeholders and multi-server features, alongside the individual display systems. You can use the parts you need; its wiki says disabled features use no CPU.
For a sidebar, TAB supports a title, lines and display conditions. Conditions are checked in order, with the first matching scoreboard selected. That gives you a documented route to different boards for different situations, rather than squeezing every message onto one sidebar.
Who it suits and what to check
Shortlist TAB when tab formatting and nametags matter as much as the sidebar. Its Modrinth listing covers many server and proxy platforms, with version labels spanning older Minecraft releases through 26.3. Match the individual release to your platform rather than treating that broad range as a promise for every build.
The sidebar is disabled by default. In config.yml, set enabled: true inside the scoreboard section before testing it. TAB's support policy also distinguishes previous purchasers, who receive unrestricted direct support, from other users, who are directed to community support.
2. SimpleScore
SimpleScore concentrates on animated sidebar scoreboards, with RGB colours, conditions and several ways to choose which board a player sees.
What it handles well
SimpleScore offers permission-based, world-based and WorldGuard region-based scoreboard selection. That makes it worth considering when the sidebar should change between areas or player groups. Its listing describes flicker-free animations and a translatable message system.
PlaceholderAPI and WorldGuard are optional integrations. You can choose whether those integrations belong in your design rather than assuming every sidebar needs region rules or external placeholders. RGB colour support is listed for Minecraft 1.16 and later.
Who it suits and what to check
Shortlist SimpleScore when your immediate job is a sidebar and you do not need this plugin to manage tab headers or nametags. Those features are not listed on its project page, so assess it as a scoreboard tool.
Its Modrinth page lists Bukkit, Folia, Paper, Purpur and Spigot, with Minecraft versions from 1.8 through 26.2 and a stated Java minimum of 8. It uses the MIT licence.
3. LuckTAB
LuckTAB uses LuckPerms groups to drive tab list formatting, nametags, chat formatting and a sidebar through one configuration file.
What it handles well
LuckTAB is worth considering when rank presentation is the centre of your display design. Its documented features include legacy colour codes, hex colours and animated gradients, plus headers and footers that vary by world or permission.
It also provides a player sidebar toggle and recognises Bedrock players through Geyser and Floodgate. For an owner planning coordinated rank displays, this brings several related presentation jobs into the same configuration.
Who it suits and what to check
Shortlist LuckTAB when you already want LuckPerms to supply your group structure. LuckPerms is required, rather than an optional enhancement. If your groups are still being planned, work through setting up rank groups, inheritance and prefixes before designing each rank's appearance.
The stated requirements include Paper or Spigot 1.21+ and Java 21. Its Modrinth listing includes 1.21.x and versions through 26.3, and identifies the licence as GPL-3.0. ProtocolLib is optional for static tab rows, so include that dependency in your checks if those rows are part of your plan.
4. DonutScoreboard
DonutScoreboard offers a configurable sidebar styled after the DonutSMP server, with editable lines, animations and permission-based board selection.
What it handles well
Its display options include MiniMessage and hex colours, with animations defined in animations.yml. The project describes updates that happen when content changes, alongside player preferences that can be synchronised across a network.
It also includes a keyall countdown feature. Shortlist that feature only if your server needs it; an animation or countdown should earn its place by helping players understand what is happening.
Who it suits and what to check
DonutScoreboard suits owners who specifically want that style of sidebar and its associated controls. Treat it as a sidebar choice rather than assuming it replaces a tab list or nametag plugin.
The Modrinth listing includes server platforms such as Paper, Purpur and Folia, and proxy platforms including Velocity and BungeeCord. It lists Minecraft 1.21.x and versions through 26.3. PlaceholderAPI and Vault are optional, and the licence is All Rights Reserved. Players can enable or disable their sidebar through the documented controls.
Test a readable sidebar before adding animations
Start with the information a player needs during ordinary play. For a hub, use the same priorities you establish when planning clear lobby navigation. A sidebar should support the next action, not compete with every other display.
- Write a small plain-text board first. Give it a clear title and a few useful lines. Check the wording before spending time on gradients or animation.
- Test the selection rules. For permission-based boards, check accounts in the groups you intend to support. For world-based boards, check each intended world.
- Add dynamic values one at a time. When a placeholder stays visible as raw text, use the PlaceholderAPI setup and troubleshooting guide before replacing the whole board configuration.
- Check the player's hide option. Decide whether your display should be optional and test the relevant toggle.
- Add animation last. Keep the finished display easy to read while players move, chat and play.
Check sidebar toggles before telling players what to type
The toggle command depends on your chosen plugin and configuration. Keep your help text consistent with the controls you actually enable.
- TAB: its scoreboard toggle command defaults to
/sb. Settings include remembering the player's choice and hiding the board by default. - LuckTAB: documents
/sidebaras its player sidebar toggle. - DonutScoreboard: documents
/sb enableand/sb disable.
For a full tab list and nametag project, start by testing TAB or LuckTAB. For a dedicated sidebar, start with SimpleScore or DonutScoreboard. Keep the decision tied to the displays, dependencies and controls your server needs.
Frequently asked questions
Should we use TAB or SimpleScore for a Paper server?
Choose TAB to test when you want tab list formatting, nametags and a sidebar within one project. Choose SimpleScore to test when the job is specifically an animated sidebar with permission, world or region-based selection. Match the release to your server version before choosing.
Which plugin can show LuckPerms ranks in the tab list?
LuckTAB explicitly uses LuckPerms groups for tab list and nametag formatting, alongside chat and sidebar displays. LuckPerms is a required dependency. Plan the group structure before configuring how each rank appears.
Why is TAB not showing a sidebar scoreboard?
TAB's scoreboard feature is disabled by default. Set enabled to true inside the scoreboard section of config.yml, then check the board's display condition. TAB checks scoreboard conditions in order and displays the first match.
How can players hide their scoreboard?
TAB's scoreboard toggle command defaults to /sb, while LuckTAB documents /sidebar. DonutScoreboard provides /sb enable and /sb disable. Check your chosen configuration before publishing the command in player help.
Does SimpleScore also change tab headers and nametags?
SimpleScore's listing describes sidebar scoreboard features rather than tab headers or nametags. TAB and LuckTAB explicitly cover those additional display areas. Choose according to the areas you need to control.
