Скорборд

Команды 1#

/scoreboard info
/scoreboard set title default &6&l{server_name}
/scoreboard preview
/scoreboard reload

/scoreboard group vip title <gradient:FFD700-FF8C00>&lVIP
/scoreboard group vip line 2 &6Баланс: &f${balance} &6[VIP]
/scoreboard info
/scoreboard group vip reset

/scoreboard reload
/scoreboard board list
/scoreboard preview

/scoreboard toggle
/scoreboard toggle

/scoreboard reload
/scoreboard preview

Конфигурация#

scoreboard.json#

Права 2#

Подробное руководство#

Config file: config/neoessentials/scoreboard.json
Reload in-game: /scoreboard reload
Admin permission: neoessentials.scoreboard.admin · Toggle permission: neoessentials.scoreboard.toggle
Introduced: v1.0.6

Overview#

The sidebar scoreboard system renders the classic right-hand-side Minecraft scoreboard — title + up to 15 lines — fully server-side, config-driven, with animation, conditional boards, and per-group/per-player overrides.

Why This Isn't Just a Vanilla /scoreboard Objective#

Vanilla's scoreboard Objective/Team/Score state lives on the server's single shared ServerScoreboard and is broadcast identically to every connected player. That's fine for a tablist row (a player's own nametag looks the same to every viewer) but wrong for a sidebar: two players might be shown different boards (one in the Nether, one in the Overworld) or the same board with different values (each player's own balance).

NeoEssentials solves this by building the four scoreboard packets (ClientboundSetObjectivePacket, ClientboundSetPlayerTeamPacket, ClientboundSetScorePacket, ClientboundResetScorePacket) against a private, never-registered Scoreboard instance purely to serialize them, then sending them directly to one player's connection — the same technique already used for the tablist header/footer packet. No two players' boards can interfere with each other, and nothing is ever visible to a player other than the one the packet was sent to.

Configuration#

Full scoreboard.json structure#

{
  "_configVersion": 1,
  "scoreboard": {
    "enabled": true,
    "refreshInterval": 20,      // ticks between updates (20 = 1s)
    "joinDelayTicks": 40,       // wait this long after join before showing a board
    "toggleCommandEnabled": true,

    "boards": [
      {
        "name": "default",
        "priority": 0,
        "conditions": [],       // empty = always matches — MUST be last (fallback)
        "title": "<gradient:FFD700-FF8C00>&l{server_name}",
        "titleFrames": [],      // optional: animated title, same shape as tablist header
        "lines": [
          { "text": "&7&m                    " },
          { "text": "&eOnline: &f{online}&7/&f{max}" },
          { "text": "&eBalance: &f${balance}" },
          { "text": "&eGroup: &f{group}" },
          { "text": "&6Richest: &f{leaderboard_money:1:name}" }
        ]
      },
      {
        "name": "nether_board",
        "priority": 10,
        "conditions": [ "world:the_nether" ],
        "title": "&c&lNETHER",
        "lines": [ { "text": "&7Danger zone" } ]
      }
    ],

    "groups":  { },
    "players": { }
  }
}

Core Fields#

Board Fields#

A line's own condition (optional, single string) controls whether that specific line is shown — hidden lines are skipped entirely (remaining visible lines compact upward into sequential slots), not left as a blank gap.

Conditions Grammar#

This is deliberately a small comparison grammar, not a scripting engine — it covers permission gates, world checks, and placeholder-threshold checks, which covers the vast majority of real use cases without the security/maintenance surface of an embedded expression language.

A board's conditions list is implicit AND. There's no OR — approximate it with two boards at adjacent priorities if you need it.

Overrides#

Same priority order as Tablist: per-player > per-group > board default.

"groups": {
  "vip": {
    "titleOverride": "&6&lVIP SERVER",
    "lineOverrides": { "2": "&6Balance: &f${balance} &6[VIP]" }
  }
},
"players": {
  "<uuid>": {
    "titleOverride": "&dWelcome back!"
  }
}

lineOverrides keys are 0-based indexes into the resolved board's lines array. An override replaces the line's text but doesn't change its condition — a conditionally-hidden line stays hidden even with an override text set.

Placeholders#

Shorthand tokens (matching tablist's convention):

Plus {animation:NAME} (from animations.json, shared with the Tablist System), the full {neoessentials_*} registered placeholder set, and {leaderboard_<board>:<rank>:name|value} — see Leaderboard System.

Commands#

Runtime overrides via /scoreboard player//scoreboard group are not persisted — add them to scoreboard.json manually to survive /scoreboard reload.

Toggle Persistence#

/scoreboard toggle is backed by its own DataStore collection (scoreboard_toggles, one record per player, written immediately on change) — the same single-collection, write-immediately pattern used by PayToggleManager for /paytoggle. A player's preference defaults to on and survives server restarts.

Disabling Completely#

Three independent layers, from most to least aggressive:

1. modules.scoreboardEnabled: false in config.json (restart required) — the event handlers driving tick/join/quit never fire at all, so no scoreboard packet is ever sent. Same restart-required module-toggle pattern as every other subsystem.
2. /scoreboard disable (live, no restart) — immediately tears down the sidebar for every currently-online player: clears the display slot, resets every visible line's score, removes the per-line teams, and removes the objective itself (not just hides it).
3. scoreboard.json's "enabled": false + /scoreboard reload — same effect as #2.

Technical Notes#

• Fake score-holder entries. Each of the 15 possible line slots uses a fixed invisible string (§0–§e) as its score-holder name — these aren't real players, just unique client-side row identifiers. The actual line text lives entirely in that slot's team prefix.
• Anti-flicker. Packets are only sent when the player's resolved title/lines actually changed since the last send — same dirty-check philosophy as the Tablist System's team prefix caching.
• Score ordering. Vanilla's client sorts sidebar rows by descending score value; each slot is given a fixed score (15 − slotIndex) so line order stays stable regardless of content, with the number itself hidden via a blank NumberFormat.

Web Dashboard API#

/api/scoreboard (auth required for reads, auth-admin for writes):

Back to Wiki Home