☰

Scoreboard Overflow

The scoreboard system is overloaded, often by a plugin or datapack creating far too many objectives, teams, or entries. This bloats world data and can cause lag or errors.

O que significa este erro?
Scoreboards track objectives, teams, and per-entity scores. When something creates an enormous number of these (frequently fake players or stray entries from a plugin), the scoreboard data balloons, hurting performance and sometimes throwing errors. 
Scoreboard too large
Causas mais comuns
  • A plugin/datapack spawning huge numbers of fake-player scores.
  • Teams or objectives created and never cleaned up.
  • A runaway loop adding scoreboard entries each tick.
  • Accumulated entries over a long-lived world.
  • Manual scoreboard misuse in command blocks.
Como diagnosticar
  1. List objectives and teams to gauge the count.
  2. Identify the plugin/datapack managing the scoreboard.
  3. Check scoreboard.dat size in the world's data folder.
  4. Look for command blocks adding entries on a clock.
Correções recomendadas
  • Remove stale objectives/teams
    Delete unused objectives and teams with the scoreboard commands.
  • Fix the source
    Update or reconfigure the plugin/datapack so it cleans up after itself.
  • Prune fake-player entries
    Reset or remove the bulk of unused score entries.
  • Stop runaway loops
    Disable any command-block clock piling on new entries every tick.
Analisar meu log
Perguntas frequentes

A bloated scoreboard means large data to save/load and process, which adds overhead.

Score holders that are not real players, often used by datapacks, easy to over-create.

In the world's data/scoreboard.dat file.