How To Set Up Scoreboard In Minecraft

A screenshot of a scoreboard on the right side of the screen.

The scoreboard organization is a complex gameplay mechanic utilized through commands. Mainly intended for mapmakers and server operators, scoreboards are used to track, set, and list the scores of entities in a myriad of different ways.

one Objectives
- ane.one Criteria
  - ane.1.1 Java Edition
    - ane.i.ane.1 Single criteria
    - 1.one.i.ii Compound criteria
  - 1.1.2 Bedrock Edition
ii Display slots
3 Tags
four Teams
5 Command reference
- 5.1 Objectives commands
- five.2 Players commands
- 5.3 Tags commands
- 5.4 Teams commands
half-dozen NBT format
vii History
8 Issues
9 References

Objectives [ ]

Objectives each have three main variables: A name, a criterion, and a display name. Objectives rail a number of points for entities, and are stored and displayed equally integers with a full score range of -2,147,483,648 to two,147,483,647.

An objective'due south name is used internally for referencing in commands, target arguments, and the file format. In Java Edition, the immune character fix for it includes all lowercase and capital letter letters, numbers, underscore, catamenia, minus and plus. In Boulder Edition, it can comprise any character.

An objective's display name is a raw JSON text and is displayed publicly in various situations. It does not have to be unique.

An objective'south criterion determines its behavior—primarily what to track. Lists of valid criteria are provided below.

An entity'southward score in any objective can be changed via commands unless it'south read-only (see #Criteria). It can exist increased by, decreased by, or set to a given amount with commands.

A score holder is a actor's name or an entity'southward UUID that has scores in an objective. Thespian name doesn't demand to be a real 1. Scores of not-role player entities tin exist changed merely by commands, and non by game system. Unlike players, when a not player entity dies, its scores are deleted.

Commands can bank check entity scores by using target selector with the scores argument (syntaxed @due east[scores={<name>=<min>..<max>}]. This argument uses <proper name> to specify the internal proper noun of the tested-for objective.

For case, in Java Edition, inputting /execute if entity @a[scores={deaths=1..}] into a command cake triggers a comparator or conditional command block if any player has died at to the lowest degree once, bold "deaths" is an objective of the "deathCount" benchmark.

Criteria [ ]

Java Edition [ ]

Single criteria [ ]

These criteria'southward names consist of a single alphabetical string.

Criterion name	Description	Tin can be modified
dummy	Score is just inverse by commands, and not by game events such equally death. This is useful for event flags, state mappings, currencies,...	Yes
trigger	Score is only inverse by commands, and not by game events such as death. The `/trigger` command tin be used by a player to set or increment/decrement their own score in an objective with this criterion. The `/trigger` command fails if the objective has not been "enabled" for the player using it, and the objective is disabled for the player after using the `/trigger` control on it. Note that the `/trigger` command tin be used by ordinary players fifty-fifty if Cheats are off and they are not an Operator. This is useful for player input via `/tellraw` interfaces.	Yep
deathCount	Score increments automatically for a thespian when they die.	Yeah
playerKillCount	Score increments automatically for a player when they impale another player.	Yes
totalKillCount	Score increments automatically for a player when they impale another player or a mob.	Yes
health	Ranges from 0 to 20 on a normal role player; represents the amount of half-hearts the player has. May appear as 0 for players earlier their health has changed for the first fourth dimension. Extra hearts and absorption hearts also count to the health score, significant that with Attributes/Modifiers or the Wellness Boost or Absorption status effects, wellness can far surpass 20.	No
xp	Matches the total amount of experience the player has collected since their concluding death (or in other words, their score).	No
level	Matches the current experience level of the player.	No
food	Ranges from 0 to 20; represents the amount of hunger points the player has. May appear as 0 for players earlier their foodLevel has inverse for the first time.	No
air	Ranges from 0 to 300; represents the amount of air the thespian has left from swimming under water, matches the air nbt tag of the role player.	No
armor	Ranges from 0 to 20; represents the corporeality of armor points the player has. May announced as 0 for players before their armor has changed for the kickoff time.	No

Compound criteria [ ]

Compound criteria's names are divided into parts, delimited with periods (.). For instance, minecraft.killed_by:minecraft.zombie is a valid compound criterion, under which player scores would increase whenever they're killed by zombie.

All objectives based on compound criteria is writable and can be modified with commands.

All statistics can exist used every bit a compound criterion whose name is its namespaced ID. Player statistics are stored separately from the scoreboard, and every bit they update, scores in these objectives are updated in parallel.

In addition, there are some other compound criteria:

Criteria base name Description Number of sub-criteria

teamkill.

Sub-criteria include team colors. Player scores increment when a player kills a member of the given colored team.

These criteria follow the complete format teamkill.<squad>, where <team> is a colour from the listing:

Accustomed ID Names
"blackness", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "grayness", "dark_gray", "blue", "green", "aqua", "ruddy", "light_purple", "yellowish", "white"

killedByTeam.

Sub-criteria include team colors. Player scores increment when a thespian has been killed by a member of the given colored squad.

These criteria follow the complete format killedByTeam.<squad>, where <squad> is a colour from the listing:

Accepted ID Names
"black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "cherry", "light_purple", "yellow", "white"

Bedrock Edition [ ]

Currently, dummy is the only criterion supported. As such, score can only be changed by commands.

Display slots [ ]

An objective with 2 points to the player is displayed in the "listing" slot, while an objective with the display name "Quest Points" with 0 points to the thespian is displayed in the "sidebar" slot.

Via the /scoreboard objectives setdisplay command (run into command reference), players' scores in specific objectives can exist displayed in certain 'slots' in-game. Each 'display slot' can prove i objective at a fourth dimension, and multiple 'brandish slots' may be used for the same or unlike objectives.

Slot	Description
listing	Displays a yellow number or some hearts (`/scoreboard objectives modify <objective> rendertype (hearts\|integer)`) without a heading on the tab menu, where online players are shown.‌^{[ Java Edition merely ]} Displays a white number without a heading on the Pause Bill of fare, where online players are shown.‌^{[ Bedrock Edition just ]} Visible even in singleplayer.
sidebar	Shows on the right manus side of the screen. Shows up to 15 entities with the highest score of that objective with a heading labeled with the objective'south <DisplayName>. Note that players are shown even if offline, and untracked players are not shown. In addition, fake players with names starting with a # practise not testify up in the sidebar under any circumstances.
sidebar.team.<color> ‌^{[ Java Edition only ]}	There are 16 squad-specific sidebar brandish slots. These operate the aforementioned as the standard sidebar slot, but only display to players who are on teams which use the specified color (for instance, "sidebar.team.green" displays to players on "greenish" teams). Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "aureate", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", "white".
belowName	Shows the <Score> followed by the objective'due south <DisplayName> below the player's nametag above their caput. This is hidden beyond ~10 blocks and when the player is sneaking. Non visible in singleplayer.

Tags [ ]

Tags are a simple listing of single-word strings stored straight in the Tags data tag of an entity. Equally with objectives, tags are case-sensitive.

Target selectors tin be used to check whether an entity has a tag with the "tag" argument.

Teams [ ]

"team" redirects here. For the command, encounter Commands/team.

A team'due south all variables are: a name, a display name, a member proper name prefix, a member proper name suffix, a boolean allow friendly burn option, and a listing of players who are on the team.

A team'south Proper name is used internally for reference in commands, target arguments, and the file format. It is a single, case-sensitive word.

A team'due south DisplayName is a JSON text component of one or more case-sensitive word, and is displayed publicly in diverse situations.

A team's Member Proper name Prefix & Member Proper name Suffix are inserted before and after the names of players on the squad, respectively. Prefixes and suffixes are used in the chat, the active players listing, the sidebar, and above team members' heads. These can be edited with respective commands.

The AllowFriendlyFire option controls whether or non members of a team are able to impairment each other. This defaults to truthful, leaving PvP mechanics unchanged—ergo, players can harm their teammates. When set to simulated, however, players on the same squad are prevented from directly damaging each other with melee attacks, bows, and Splash Potions of Harming. Note that players on the same team may nevertheless inflict negative status effects on each other with potions, even if <AllowFriendlyFire> is faux. Some non-role player entities in a squad are also afflicted by this.

It is important to note that each individual team fellow member can only be on one team; teams cannot share entities.

Commands can be used to cheque whether team members exist by using target option with the "squad" argument. (The '!' character may be placed before a name to bank check for entities not on a team.) For example, inputting /execute if entity @a[squad=ruby-red] into a command block provides comparator output if any role player exists on the red team. Conversely, /execute if entity @a[team=!blood-red] provides output when there are no players on the ruddy team. /execute if entity @a[team=!] allows output when any player is on at to the lowest degree 1 team, and /execute if entity @a[team=] allows output when no players are on whatsoever teams.

Control reference [ ]

For more details, see Commands/scoreboard.

Objectives commands [ ]

Commands	Clarification
scoreboard objectives list	List all existing objectives with their display names and criteria.
scoreboard objectives add together <objective> <criteria> [<displayName>]‌^{[ Coffee Edition just ]} scoreboard objectives add together <objective: string> dummy [displayName: string]‌^{[ Bedrock Edition just ]}	Create a new objective with the given internal objective name, specified benchmark, and the optional brandish name. In Bedrock Edition, "dummy" is the simply benchmark currently supported. `<displayName>` defaults to `<objective>` when unspecified. See above section for more on these arguments.
scoreboard objectives remove <objective>‌^{[ Java Edition but ]} scoreboard objectives remove <objective: string>‌^{[ Bedrock Edition but ]}	Delete all references to the named objective in the scoreboard system. Data is deleted from the objectives list and score holders' scores, and if it was on a display list it is no longer displayed.
scoreboard objectives setdisplay <slot > [<objective ]‌^{[ Coffee Edition only ]} scoreboard objectives setdisplay <listing\|sidebar> [objective: cord] [ascending\|descending]‌^{[ Boulder Edition only ]} scoreboard objectives setdisplay belowname [objective: string]‌^{[ Boulder Edition simply ]}	Display score info for the objective in the given slot. Valid slots are listed and described in Display Slots. In Bedrock Edition, if slot is `list` or `sidebar`, at that place is an additional optional argument `ascending\|descending` to specify the sort order. Note that the objective parameter is optional; if no objective is provided, this display slot is cleared (returned to its default state).
scoreboard objectives alter <objective> displayname <displayName> ‌^{[ Java Edition only ]}	Change the display name of the scoreboard in display slots.
scoreboard objectives modify <objective> rendertype (hearts\|integer) ‌^{[ Java Edition only ]}	Change the brandish format of the player list.

Players commands [ ]

Commands	Clarification
scoreboard players list [<target>]‌^{[ Java Edition simply ]} scoreboard players list [playername: target]‌^{[ Bedrock Edition only ]}	Lists all score holders which are tracked in some way by the scoreboard system. The optional `<target>` or `playername: target` parameter is used to list the scores of item score holders.
scoreboard players get <target> <objective> ‌^{[ Java Edition simply ]}	Return the scoreboard value.
scoreboard players set <targets> <objective> <score>‌^{[ Java Edition only ]} scoreboard players prepare <player: targets> <objective: string> <count: int>‌^{[ Boulder Edition but ]}	Set the targets' scores of the given objective, overwriting any previous score.
scoreboard players add <targets> <objective> <score>‌^{[ Java Edition merely ]} scoreboard players add <role player: targets> <objective: cord> <count: int>‌^{[ Bedrock Edition only ]}	Increments the targets' scores in that objective by the given corporeality.
scoreboard players remove <targets> <objective> <score>‌^{[ Java Edition only ]} scoreboard players remove <player: targets> <objective: cord> <count: int>‌^{[ Bedrock Edition only ]}	Decrements the targets' scores in that objective by the given amount.
scoreboard players random <player: target> <objective: cord> <min: int> <max: int> ‌^{[ Boulder Edition only ]}	Sets the targets' scores in that objective to a random number between min and max, both inclusive.
scoreboard players reset <targets> [<objective>]‌^{[ Coffee Edition only ]} scoreboard players reset <role player: target> [objective: string]‌^{[ Bedrock Edition merely ]}	Deletes score or all scores for the target. If `<objective>` is specified, and then just that objective is cleared. Otherwise, this applies to all objectives. Note that this does not only set the score(s) to 0: it removes the targets from the scoreboard altogether (or for the given objective).
scoreboard players test <player: target> <objective: cord> <min: wildcard int> [<max: wildcard int>] ‌^{[ Bedrock Edition merely ]}	Tests if targets' scores are within `min: wildcard int` and `max: wildcard int` (Defaults to 2,147,483,647). `min: wildcard int` can be replaced with asterisk () to correspond -2,147,483,648, and `max: wildcard int` tin can exist replaced with asterisk () to represent two,147,483,647.
scoreboard players enable <targets> <objective> ‌^{[ Java Edition merely ]}	Enables the target player(s) to use the `/trigger` command on the specified objective. This command accepts non-actor entities, but just players are able to really utilize the `/trigger` command. Until this has been done, players that endeavor to `/trigger` that objective fail. Using the `/trigger` control disables information technology again. Note that if the target(s) did not previously have a score for the specified objective, this command will set their score to 0.
scoreboard players performance <targets> <targetObjective> <operation> <source> <sourceObjective>‌^{[ Java Edition merely ]} scoreboard players operation <histrion: target> <targetObjective: string> <functioning: operator> <selector: target> <objective: string>‌^{[ Boulder Edition only ]}	Applies an arithmetic performance altering the targets' score(due south) in the target objective, using sources' scores in the source objective every bit input. <operation> may exist: "+=" Improver: Add source's score to that of target "-=" Subtraction: Subtract source's score from that of target "*=" Multiplication: Set target'south score to the product of target'due south and source'southward scores "/=" (Integer) Sectionalization: Divide target's score by source's score, and use the result (rounded downward) to set the target score. "%=" Modulus: Divide target's score by source'south score, and utilize the residual to set the target score "=" Assign: Set target's score to that of source "<" Min: Set target's score to source's score but if source has the lesser score. ">" Max: Set target's score to source'due south score only if source has the greater score. "><" Swaps target's and source'due south scores In all cases except "><", source's score in the objective remains unchanged. In all cases except "><", source's score remains unchanged. If target or source isn't tracked by the specified objective, it will be set to 0. If more than than one score holder is specified as sources, performs the performance once with each source's score. If more than than one target score holder is specified, performs the performance for each target 1 by one.

Tags commands [ ]

Teams commands [ ]

NBT format [ ]

The file scoreboard.dat in the 'information' binder of a Minecraft world stores the scoreboard information for that world as a GZip'd NBT file:

The root tag.
- data: The scoreboard data.
  - Objectives: A list of compound tags representing objectives.
    - An objective.
      - CriteriaName: The benchmark of this objective.
      - DisplayName: The brandish proper name of this objective in JSON. If none was specified during the objective'southward cosmos, this is gear up to {"text":"Value of Name"}.
      - Name: The internal name of this objective.
      - RenderType: The way the score is displayed. Can exist "integer" or "hearts", but defaults to "integer".
  - PlayerScores: A list of chemical compound tags representing scores tracked by the scoreboard system.
    - A tracked player/objective pair with a score.
      - Score: The score this actor has in this objective.
      - Name: The name of the player who has this score in this objective.
      - Objective: The internal name of the objective which this player has this score in.
      - Locked: i or 0 (true/false) - simulated if this objective is "enabled". Simply meaningful for objectives with the criteria "trigger", where this must exist false before a thespian can use the /trigger control on it.
  - Teams: A list of compound tags representing teams.
    - A Team.
      - AllowFriendlyFire: 1 or 0 (true/false) - true if players on this squad tin harm each other.
      - SeeFriendlyInvisibles: 1 or 0 (truthful/false) - true if players on this squad can see invisible teammates.
      - NameTagVisibility: The value of the nametagVisibility option of this team.
      - DeathMessageVisibility: The value of the deathMessageVisibility option of this team. Valid options are: never, hideForOtherTeams, hideForOwnTeam, always
      - CollisionRule: The value of the collisionrule selection of this team. Valid options are: always, pushOwnTeam, never, pushOtherTeams
      - DisplayName: The display proper noun of this team in JSON. If none was specified during the team's creation, this is set to {"text":"Value of Name"}.
      - Name: The internal name of this team.
      - MemberNamePrefix: The prefix prepended to names of players on this team. In JSON format.
      - MemberNameSuffix: The suffix appended to names of players on this team. In JSON format
      - TeamColor: The text-based colour ("black", "dark_blue", etc.) given to the team. Does not exist if no colour is set.
      - Players: A list of names of players on this squad.
        
        The name of a player on this squad.
  - DisplaySlots: A set of slots which are displaying specific objectives. If a slot is empty, its tag is not present.
    - slot_n : The internal name of the objective displayed (see below).

Display slots
No.	Type	Name
0	Player list	list
1	On the sidebar	sidebar
2	Below the thespian's username	belowName
3	Team color	sidebar.squad.black
four		sidebar.team.dark_blue
5		sidebar.team.dark_green
6		sidebar.team.dark_aqua
vii		sidebar.squad.dark_red
8		sidebar.team.dark_purple
9		sidebar.team.gold
10		sidebar.squad.grayness
11		sidebar.team.dark_gray
12		sidebar.team.blue
13		sidebar.team.green
xiv		sidebar.team.aqua
15		sidebar.team.cherry-red
sixteen		sidebar.squad.light_purple
17		sidebar.team.yellow
18		sidebar.team.white

History [ ]

Java Edition
1.5	13w04a	Added scoreboard.
1.5	13w05a	Added team-based functionality.
one.seven.2	13w36a	Added statistic-based objective criteria.
1.8	14w02a	Entities other than players tin can at present be part of teams and have objective scores.
	14w06a	Added the `trigger` and team kill-based objective criteria.
		Added `/scoreboard players enable`.
		"*" can be used in a player proper name statement to represent all players tracked past the scoreboard.
		Added the "objective" argument to `/scoreboard players reset`.
		Statistic objective criteria at present utilise named IDs instead of numerical IDs.
		Added the `achievement.overpowered` objective criterion.
	14w07a	Added `/scoreboard players operation` and `/scoreboard players test`.
		Scores for faux players that have a proper name first with "#" won't announced in the sidebar.
		Added squad-specific sidebar display slots.
		Added the `nametagVisibility` squad pick.
	14w10a	Added the `deathMessageVisibility` team option.
		Added a `dataTag` argument to `/scoreboard players set`, `/scoreboard players add together`, and `/scoreboard players remove`.
		Added the `stat.crouchOneCm`, `stat.sprintOneCm`, and `stat.timeSinceDeath` objective criteria.
	14w25a	Added `=`, `<`, and `>` to `/scoreboard players operation`.
	14w29a	Player/entity names in the sidebar are now secondarily sorted by alphabetical society.
	14w30a	Added the `stat.talkedToVillager` and `stat.tradedWithVillager` objective criteria.
	?	Added `><` to `/scoreboard players operation`.
1.8.2		Added the `stat.cauldronFilled`, `stat.cauldronUsed`, `stat.armorCleaned`, `stat.bannerCleaned`, `stat.brewingstandInteraction`, `stat.beaconInteraction`, `stat.dropperInspected`, `stat.hopperInspected`, `stat.dispenserInspected`, `stat.noteblockPlayed`, `stat.noteblockTuned`, `stat.flowerPotted`, `stat.trappedChestTriggered`, `stat.enderchestOpened`, `stat.itemEnchanted`, `stat.recordPlayed`, `stat.furnaceInteraction`, `stat.craftingTableInteraction`, `stat.chestOpened` objective criteria.
i.9	15w32a	Added the `stat.sneakTime` objective criteria.
	15w32b	Added `/scoreboard players tag`.
	15w32b	Added the `xp`, `food`, and `air` objective types.
	15w33a	Added the `stat.pickup` and `stat.drop` objective criteria.
	15w33a	Added the `armor`, `level` objective types.
	15w36a	Added `collisionRule`.
	15w49a	Added the `stat.aviateOneCm` objective criteria.
ane.13	pre7	Added `/scoreboard objectives modify`.
	pre8	Added `/scoreboard objectives alter <objectiveName> rendertype hearts` , which makes wellness bars display every bit hearts, similar this: .
		Added `/scoreboard objectives modify <objectiveName> rendertype integer` , which makes health confined display every bit yellow numbers.
		Objective names are now text components, not raw strings.
one.thirteen.1	18w31a	Changed the scoreboard operator `%=` from using `%` to `Math.floorMod`.
i.18	21w37a	Removed xvi-character length limits for scoreboards, score holders and team names.
Bedrock Edition
1.seven.0	beta one.7.0.two	Added basic scoreboard mechanics.
1.seven.0	beta one.7.0.two	Added dummy scoreboards.

Issues [ ]

Issues relating to "Scoreboard" are maintained on the bug tracker. Report issues there.

References [ ]

Versions

Demo
- Locations
PC Gamer Demo (Beta 1.3)

Development

Version history	Pre-Classic Classic Early Archetype Creative Multiplayer Test Survival Exam Late Archetype Creative Indev Infdev Alpha Beta Full Release Development versions

Removed features
- Blocks
- Items
Unused features
Sectional features
Mentioned features
- Sky dimension
Planned versions

Technical

Known bugs
- Minecraft Launcher
Hardware requirements
al_version
Block entity
Commands
- Functions
Crashes
Information values
- Classic
- Indev
- Pre-flattening
Data version
Debug screen
Formatting codes
Central codes
Minecraft Launcher
Protocol version
Resource location
Screenshot
Seed
Statistics
Tick
Spawn clamper
Coordinates

.minecraft	client.jar client.json launcher_profiles.json options.txt

Development resource	Anvil file format Chunk format Command storage format Generated structures format Level format Loot tables Map item format Model NBT format Obfuscation map Role player format raids.dat format Raw JSON text format Region file format Construction block file format Schematic file format Scoreboard format Server list format sounds.json Subtitles villages.dat format
Legacy development resources	Classic level format Classic server protocol Indev level format Alpha level format server_level.dat

Multiplayer

Server
Minecraft Realms
Server list
server.backdrop
Server requirements

Game customization

Skins
Capes
Resource packs
Data packs