Skip to main content
Scoreboard is the central manager object in VelaBoard. Every player you track, every team you configure, and every sidebar you display belongs to a Scoreboard instance. Rather than creating sidebars and teams in isolation, you work through a scoreboard so that all of these pieces stay coordinated in a single context.

The scoreboard lifecycle

You never instantiate Scoreboard directly. Instead, obtain one from ScoreboardHandler:
Once you have a scoreboard, register players with addPlayer(Player). VelaBoard needs a player to be registered before it can display sidebars or assign them to teams through this scoreboard. When a player leaves or you no longer need to track them, call removePlayer(Player) to clean up.

Players

Use getPlayers() to inspect who is currently registered. It returns a Collection<UUID> of all registered player IDs.

Teams

Teams group players and entities under shared visual properties like colors, prefixes, and collision rules. The Scoreboard manages the full team lifecycle. See Team Management in VelaBoard for full team configuration details. A scoreboard can manage both per-player sidebars (PlayerSidebar) and shared sidebars visible to multiple players (SharedSidebar) at the same time. See Sidebar Types: Player vs Shared for full sidebar configuration details.
A single Scoreboard instance can manage multiple teams and sidebars simultaneously. You do not need separate scoreboard instances for different groups of players or different sidebar types.

Example

The following example creates a scoreboard, registers a player, creates a player sidebar, and checks whether the player has an active sidebar: