NBT & data editing · Java · Intermediate

How to Edit Objectives, Teams, and Player Scores in scoreboard.dat

Uninstalling complex datapacks often leaves your world cluttered with hundreds of obsolete scoreboard objectives and orphaned player scores. By manually editing the scoreboard.dat file offline, you can instantly clean up your world data, modify player statistics, or tweak team settings without typing tedious in-game commands. Because the NBT Editor runs entirely inside your browser, your world files are processed locally on your device and never upload to a server.

Open the NBT EditorOpen and edit any NBT file: level.dat, player data, structures, schematics, Bedrock files.

What you need

  • A Minecraft Java Edition world folder or .zip archive
  • The NBT Editor tool on our site
  • A complete backup of your world before making any changes

Step by step

  1. 1Back Up and Close Your World

    Before touching any world data, make a complete copy of your world folder and store it somewhere safe. Ensure that you have completely exited the world in singleplayer, or stopped the server if it is a multiplayer world. Minecraft overwrites data files upon saving and exiting, which will immediately erase your external edits if the game is still running.

    Tip: You can compress your world folder into a .zip file to serve as both a safe backup and an easy way to load it into our browser tool.

  2. 2Load scoreboard.dat in the NBT Editor

    Open the NBT Editor on our site and click to open your world folder or .zip archive. Navigate through the file tree to locate the 'data' subfolder, then select 'scoreboard.dat' to parse its structure. Once loaded, expand the root compound tag and then expand the 'data' compound tag to view the main scoreboard lists.

    Tip: If your world does not have a scoreboard.dat file yet, it simply means no objectives or teams have ever been created in that save.

  3. 3Clean Up Broken Objectives

    Expand the 'Objectives' list tag to see every tracking objective currently registered in the world. Each entry is an anonymous compound tag containing tags like 'Name' (the internal ID), 'CriteriaName' (what triggers it, such as 'dummy' or 'minecraft.killed:minecraft.zombie'), and 'DisplayName' (a JSON text string). To remove a leftover objective from an old datapack, select its parent compound tag inside the 'Objectives' list and delete it.

    Tip: Write down the exact 'Name' string of any objective you delete so you can also clean up its associated player scores in the next step.

  4. 4Modify or Prune Player Scores

    Collapse the objectives and expand the 'PlayerScores' list tag. Each compound tag here represents a single score entry, linking a player or entity UUID ('Name') to a specific tracker ('Objective') with an integer value ('Score'). To adjust a player's score, simply double-click the 'Score' tag and type a new integer; to finish cleaning up a deleted datapack, delete any compound entries whose 'Objective' tag matches the ones you removed earlier.

    Tip: Many datapacks store global variables on fake players with names starting with a hash symbol (like '#global' or '#temp'), which you can safely delete if the datapack is gone.

  5. 5Adjust Team Settings and Members

    Expand the 'Teams' list tag to inspect all configured teams and their rules. Inside each team's compound tag, you can edit properties like 'TeamColor', 'FriendlyFire' (0 for false, 1 for true), and 'CollisionRule' (such as 'never' or 'always'). You can also expand the 'Players' list inside a team to manually add or remove player usernames or entity UUIDs from that roster.

  6. 6Check Display Slots and Save

    Finally, expand the 'DisplaySlots' compound tag, which controls what objectives currently appear on the 'sidebar', 'list' (tab menu), or 'belowName' areas. If you deleted an objective in Step 3 that was actively being displayed here, delete its corresponding display slot tag so the game does not reference a missing tracker. Click the Save button in the NBT Editor to download your modified scoreboard.dat, and replace the original file inside your world's 'data' folder.

How it works

In Minecraft Java Edition, the scoreboard system is stored globally rather than per-dimension, residing in the 'data/scoreboard.dat' file as a GZip-compressed Named Binary Tag (NBT) structure. Unlike player inventories which are tied to individual UUID files, the scoreboard acts as a centralized relational database for the entire world. The root tag always wraps a single 'data' compound, which separates the logic into four distinct areas: 'Objectives', 'PlayerScores', 'Teams', and 'DisplaySlots'.

Because 'Objectives' (the definitions) and 'PlayerScores' (the actual values) are stored in separate NBT lists, they are only linked by the string name of the objective. When a datapack creates thousands of scores for entities and you later delete the datapack files, the scores remain permanently in 'scoreboard.dat' unless explicitly removed. If you delete an objective definition via NBT without deleting its corresponding entries in 'PlayerScores', those scores become orphaned data. While Minecraft will usually ignore or silently purge orphaned scores upon loading, cleaning up both lists ensures your file size stays minimal and prevents unexpected conflicts if a new datapack uses the same objective names.

Common mistakes

  • Editing scoreboard.dat while the world is currently open in Minecraft, which results in the game overwriting your manual changes the moment it auto-saves.
  • Deleting an objective from the 'Objectives' list while leaving it assigned in 'DisplaySlots', which can cause empty or glitchy scoreboard sidebars until reassigned.
  • Typing plain text into 'DisplayName', 'MemberNamePrefix', or 'MemberNameSuffix' tags instead of valid JSON text formatting (for example, it must be formatted like '{"text":"My Title"}' in modern versions).
  • Modifying the 'Locked' tag on a non-trigger objective expecting it to freeze a player's score; the 'Locked' byte tag only functions mechanically for objectives using the 'trigger' criteria.

FAQ

Why do I see long strings of random letters and numbers in the PlayerScores list instead of usernames?

While actual players are usually tracked by their username in the scoreboard, non-player entities (like armor stands or markers used by datapacks) are tracked by their 36-character hexadecimal UUID.

What happens if I just delete the entire scoreboard.dat file?

Minecraft will cleanly generate a brand new, empty scoreboard.dat file the next time you load the world. This is a safe way to completely factory-reset all teams, objectives, and scores at once, though it will break any active datapacks that rely on existing scoreboard setups.

Can I change an objective's CriteriaName after it has been created?

Yes. Unlike in-game commands which require you to delete and recreate an objective to change its criteria, editing the 'CriteriaName' string in the NBT Editor allows you to change what an objective tracks while preserving all existing player scores for it.

By opening data/scoreboard.dat in our browser-based NBT Editor, you can easily purge leftover datapack objectives, edit player scores, and customize team rules offline without uploading your world files.

More nbt & data editing guides

NBT & data editingHow to Edit Chest Contents, Sign Text, and Command Blocks Inside Chunk NBTEvery placed container, sign, and command block in a Minecraft Java Edition world stores its detailed state inside the region files as a block entity. When you need to clear a lag-inducing chest, edit a sign without breaking it, or disable a soft-locking repeating command block, you can modify these properties directly in the chunk data. This guide explains how to locate and edit placed block entities using our browser-based NBT Editor.JavaAdvanced5 steps
NBT & data editingHow to Open and Edit Any Minecraft NBT or .dat File in Your BrowserMinecraft stores almost all of its world rules, player inventories, and entity details inside Named Binary Tag (NBT) files, which normally look like unreadable gibberish in a standard text editor. With the browser-based NBT Editor on world.9minecraft.net, you can decode, navigate, and modify any .dat or .nbt file directly on your device. Because the tool runs locally in your browser, your save files are processed instantly and never upload to an external server.Java & BedrockBeginner5 steps
NBT & data editingHow to Inspect and Modify Structure Block .nbt FilesMinecraft Structure Blocks save custom builds as standalone .nbt files, allowing you to transfer creations between worlds or use them in custom data packs. Instead of rebuilding a structure in-game just to swap out one building material or remove accidentally captured mobs, you can directly edit the saved structure data. Our browser-based NBT Editor lets you inspect and modify these files locally on your device without uploading anything to a server.JavaIntermediate5 steps
NBT & data editingHow to Edit Villager Trades, XP, and Gossip Data via Entity NBTCustomizing villager trades, experience levels, and player reputation directly in your Minecraft Java Edition world allows you to build tailored shops or fix broken trading halls without using in-game command blocks. Since Minecraft 1.17 separated entity storage from terrain chunks, villager data lives inside dedicated entity region files that can be modified with precision. Using the browser-based NBT Editor on world.9minecraft.net, you can inspect and rewrite a villager's Offers, Recipes, and Gossips tags locally on your machine without ever uploading your world files.JavaAdvanced6 steps
NBT & data editingMinecraft NBT Data Types Explained: Byte, Short, Int, Long, Compound, and ArraysModifying Minecraft world files requires a clear understanding of the Named Binary Tag (NBT) format, as entering a value outside a tag's strict mathematical boundaries will immediately break your save. This guide breaks down all thirteen binary data types across both Java and Bedrock Editions so you can edit values safely without causing data overflow or chunk resets. You will learn how to inspect and modify these exact tag types directly inside your browser using our local NBT Editor.Java & BedrockIntermediate5 steps