How To Set A Scoreboard For Deaths 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 rails, set, and list the scores of entities in a myriad of different ways.

1 Objectives
- i.1 Criteria
  - one.1.one Coffee Edition
    - 1.1.1.1 Single criteria
    - ane.1.1.2 Compound criteria
  - 1.i.2 Bedrock Edition
2 Display slots
3 Tags
four Teams
5 Command reference
- 5.ane Objectives commands
- 5.ii Players commands
- five.3 Tags commands
- 5.4 Teams commands
6 NBT format
seven History
viii Issues
ix References

Objectives [ ]

Objectives each have 3 chief variables: A name, a criterion, and a display name. Objectives track a number of points for entities, and are stored and displayed as integers with a full score range of -ii,147,483,648 to 2,147,483,647.

An objective's proper name is used internally for referencing in commands, target arguments, and the file format. In Java Edition, the allowed grapheme set for information technology includes all lowercase and uppercase letters, numbers, underscore, period, minus and plus. In Boulder Edition, it can contain whatsoever character.

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

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

An entity's score in any objective can exist inverse via commands unless information technology's read-only (come across #Criteria). It tin exist increased past, decreased by, or set to a given amount with commands.

A score holder is a player'southward name or an entity'south UUID that has scores in an objective. Player name doesn't need to be a real ane. Scores of not-player entities tin be changed just by commands, and not past game system. Unlike players, when a non histrion entity dies, its scores are deleted.

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

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

Criteria [ ]

Java Edition [ ]

Single criteria [ ]

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

Benchmark proper name	Description	Can exist modified
dummy	Score is just changed by commands, and non past game events such every bit death. This is useful for effect flags, state mappings, currencies,...	Yes
trigger	Score is simply inverse by commands, and non by game events such as death. The `/trigger` command can be used by a player to set or increase/decrement their own score in an objective with this criterion. The `/trigger` control fails if the objective has not been "enabled" for the player using it, and the objective is disabled for the histrion later on using the `/trigger` control on information technology. Note that the `/trigger` control tin be used by ordinary players even 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 player when they die.	Aye
playerKillCount	Score increments automatically for a player when they kill another player.	Yes
totalKillCount	Score increments automatically for a player when they kill another player or a mob.	Yeah
health	Ranges from 0 to 20 on a normal player; represents the amount of half-hearts the thespian has. May appear as 0 for players before their health has changed for the kickoff time. Extra hearts and absorption hearts besides count to the health score, meaning that with Attributes/Modifiers or the Health Boost or Absorption status effects, health tin far surpass 20.	No
xp	Matches the total amount of experience the player has nerveless since their last death (or in other words, their score).	No
level	Matches the current experience level of the histrion.	No
nutrient	Ranges from 0 to 20; represents the amount of hunger points the player has. May appear equally 0 for players before their foodLevel has inverse for the first time.	No
air	Ranges from 0 to 300; represents the amount of air the player has left from swimming under water, matches the air nbt tag of the player.	No
armor	Ranges from 0 to 20; represents the amount of armor points the actor has. May appear as 0 for players before their armor has changed for the first time.	No

Compound criteria [ ]

Compound criteria's names are divided into parts, delimited with periods (.). For example, minecraft.killed_by:minecraft.zombie is a valid compound benchmark, nether which player scores would increment whenever they're killed past zombie.

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

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

In addition, there are some other compound criteria:

Criteria base of operations name Description Number of sub-criteria

teamkill.

Sub-criteria include team colors. Actor scores increment when a histrion kills a member of the given colored squad.

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

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"

killedByTeam.

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

These criteria follow the consummate format killedByTeam.<team>, where <team> is a colour from the list:

Accustomed ID Names
"black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "greyness", "dark_gray", "blue", "light-green", "aqua", "red", "light_purple", "yellow", "white"

sixteen

Bedrock Edition [ ]

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

Display slots [ ]

An objective with two points to the player is displayed in the "list" 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 control (run into command reference), players' scores in specific objectives can be displayed in certain 'slots' in-game. Each 'display slot' can show one objective at a time, and multiple 'display slots' may be used for the same or different objectives.

Slot	Description
list	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 only ]} Displays a white number without a heading on the Pause Menu, where online players are shown.‌^{[ Boulder Edition only ]} Visible even in singleplayer.
sidebar	Shows on the right paw side of the screen. Shows upward to 15 entities with the highest score of that objective with a heading labeled with the objective's <DisplayName>. Notation that players are shown even if offline, and untracked players are non shown. In add-on, fake players with names starting with a # exercise not show up in the sidebar under whatsoever circumstances.
sidebar.team.<color> ‌^{[ Java Edition only ]}	There are 16 squad-specific sidebar display slots. These operate the same as the standard sidebar slot, but simply display to players who are on teams which use the specified color (for example, "sidebar.team.green" displays to players on "green" teams). Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gilded", "grayness", "dark_gray", "bluish", "greenish", "aqua", "red", "light_purple", "xanthous", "white".
belowName	Shows the <Score> followed by the objective's <DisplayName> below the player'southward nametag above their caput. This is subconscious across ~10 blocks and when the player is sneaking. Not visible in singleplayer.

Tags [ ]

Tags are a simple list of unmarried-word strings stored directly in the Tags data tag of an entity. As with objectives, tags are case-sensitive.

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

Teams [ ]

"team" redirects here. For the command, run across Commands/squad.

A team's all variables are: a name, a brandish name, a member proper name prefix, a member name suffix, a boolean allow friendly fire option, and a list of players who are on the team.

A team'southward Name is used internally for reference in commands, target arguments, and the file format. It is a single, example-sensitive word.

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

A team's Member Name Prefix & Member Proper noun Suffix are inserted before and afterwards the names of players on the team, respectively. Prefixes and suffixes are used in the chat, the agile players list, the sidebar, and above team members' heads. These tin be edited with respective commands.

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

It is important to note that each private team fellow member can but be on i team; teams cannot share entities.

Commands tin can be used to check whether team members be by using target choice with the "team" argument. (The '!' graphic symbol may exist placed before a name to bank check for entities not on a team.) For case, inputting /execute if entity @a[team=crimson] into a command block provides comparator output if any player exists on the red team. Conversely, /execute if entity @a[team=!cherry-red] provides output when there are no players on the red team. /execute if entity @a[team=!] allows output when any player is on at least one team, and /execute if entity @a[team=] allows output when no players are on any teams.

Command reference [ ]

For more than details, see Commands/scoreboard.

Objectives commands [ ]

Commands	Description
scoreboard objectives listing	Listing all existing objectives with their brandish names and criteria.
scoreboard objectives add <objective> <criteria> [<displayName>]‌^{[ Java Edition only ]} scoreboard objectives add <objective: string> dummy [displayName: cord]‌^{[ Bedrock Edition only ]}	Create a new objective with the given internal objective name, specified benchmark, and the optional display proper noun. In Bedrock Edition, "dummy" is the only criterion currently supported. `<displayName>` defaults to `<objective>` when unspecified. Run into to a higher place department for more on these arguments.
scoreboard objectives remove <objective>‌^{[ Java Edition only ]} scoreboard objectives remove <objective: string>‌^{[ Bedrock Edition only ]}	Delete all references to the named objective in the scoreboard system. Information 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 just ]} scoreboard objectives setdisplay <list\|sidebar> [objective: string] [ascending\|descending]‌^{[ Bedrock Edition only ]} scoreboard objectives setdisplay belowname [objective: string]‌^{[ Bedrock Edition only ]}	Display score info for the objective in the given slot. Valid slots are listed and described in Brandish 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 brandish slot is cleared (returned to its default state).
scoreboard objectives change <objective> displayname <displayName> ‌^{[ Java Edition but ]}	Modify the display name of the scoreboard in display slots.
scoreboard objectives modify <objective> rendertype (hearts\|integer) ‌^{[ Coffee Edition only ]}	Alter the display format of the role player list.

Players commands [ ]

Commands	Description
scoreboard players list [<target>]‌^{[ Java Edition but ]} scoreboard players listing [playername: target]‌^{[ Boulder 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 particular score holders.
scoreboard players get <target> <objective> ‌^{[ Java Edition but ]}	Return the scoreboard value.
scoreboard players set <targets> <objective> <score>‌^{[ Coffee Edition simply ]} scoreboard players set <thespian: targets> <objective: string> <count: int>‌^{[ Bedrock Edition simply ]}	Ready the targets' scores of the given objective, overwriting whatever previous score.
scoreboard players add <targets> <objective> <score>‌^{[ Coffee Edition only ]} scoreboard players add together <thespian: targets> <objective: string> <count: int>‌^{[ Boulder Edition just ]}	Increments the targets' scores in that objective by the given amount.
scoreboard players remove <targets> <objective> <score>‌^{[ Java Edition only ]} scoreboard players remove <player: targets> <objective: string> <count: int>‌^{[ Boulder Edition only ]}	Decrements the targets' scores in that objective by the given corporeality.
scoreboard players random <histrion: target> <objective: string> <min: int> <max: int> ‌^{[ Bedrock Edition only ]}	Sets the targets' scores in that objective to a random number between min and max, both inclusive.
scoreboard players reset <targets> [<objective>]‌^{[ Java Edition only ]} scoreboard players reset <thespian: target> [objective: string]‌^{[ Boulder Edition but ]}	Deletes score or all scores for the target. If `<objective>` is specified, and then but that objective is cleared. Otherwise, this applies to all objectives. Notation that this does not merely 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: string> <min: wildcard int> [<max: wildcard int>] ‌^{[ Bedrock Edition just ]}	Tests if targets' scores are inside `min: wildcard int` and `max: wildcard int` (Defaults to 2,147,483,647). `min: wildcard int` tin be replaced with asterisk () to represent -2,147,483,648, and `max: wildcard int` tin can be replaced with asterisk () to stand for ii,147,483,647.
scoreboard players enable <targets> <objective> ‌^{[ Java Edition only ]}	Enables the target player(s) to use the `/trigger` command on the specified objective. This command accepts non-role player entities, only simply players are able to really use the `/trigger` command. Until this has been done, players that effort to `/trigger` that objective fail. Using the `/trigger` command disables information technology once again. Annotation that if the target(s) did non previously have a score for the specified objective, this command will set their score to 0.
scoreboard players operation <targets> <targetObjective> <operation> <source> <sourceObjective>‌^{[ Java Edition but ]} scoreboard players functioning <player: target> <targetObjective: string> <functioning: operator> <selector: target> <objective: string>‌^{[ Bedrock Edition only ]}	Applies an arithmetic operation altering the targets' score(south) in the target objective, using sources' scores in the source objective every bit input. <functioning> may exist: "+=" Add-on: Add source'due south score to that of target "-=" Subtraction: Decrease source's score from that of target "*=" Multiplication: Gear up target'south score to the production of target's and source'southward scores "/=" (Integer) Division: Divide target's score by source's score, and use the event (rounded downwards) to set the target score. "%=" Modulus: Split up target's score by source's score, and use the remainder to set the target score "=" Assign: Set target's score to that of source "<" Min: Ready target's score to source's score only if source has the bottom score. ">" Max: Set target's score to source's score just if source has the greater score. "><" Swaps target's and source's scores In all cases except "><", source'south score in the objective remains unchanged. In all cases except "><", source'south score remains unchanged. If target or source isn't tracked by the specified objective, it will be set to 0. If more than 1 score holder is specified as sources, performs the operation once with each source's score. If more 1 target score holder is specified, performs the functioning for each target i by 1.

Tags commands [ ]

Teams commands [ ]

NBT format [ ]

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

The root tag.
- data: The scoreboard data.
  - Objectives: A list of compound tags representing objectives.
    - An objective.
      - CriteriaName: The criterion of this objective.
      - DisplayName: The brandish name of this objective in JSON. If none was specified during the objective'southward creation, this is set up to {"text":"Value of Proper name"}.
      - Proper name: The internal name of this objective.
      - RenderType: The mode the score is displayed. Can be "integer" or "hearts", just defaults to "integer".
  - PlayerScores: A listing of compound tags representing scores tracked by the scoreboard system.
    - A tracked player/objective pair with a score.
      - Score: The score this player has in this objective.
      - Name: The proper name of the player who has this score in this objective.
      - Objective: The internal proper name of the objective which this thespian has this score in.
      - Locked: 1 or 0 (truthful/simulated) - false if this objective is "enabled". Merely meaningful for objectives with the criteria "trigger", where this must exist false before a player tin can use the /trigger command on it.
  - Teams: A list of compound tags representing teams.
    - A Team.
      - AllowFriendlyFire: ane or 0 (true/false) - true if players on this squad tin can damage each other.
      - SeeFriendlyInvisibles: 1 or 0 (true/faux) - truthful if players on this team can see invisible teammates.
      - NameTagVisibility: The value of the nametagVisibility option of this team.
      - DeathMessageVisibility: The value of the deathMessageVisibility option of this squad. Valid options are: never, hideForOtherTeams, hideForOwnTeam, always
      - CollisionRule: The value of the collisionrule option of this team. Valid options are: always, pushOwnTeam, never, pushOtherTeams
      - DisplayName: The display name of this squad in JSON. If none was specified during the team'due south cosmos, this is set to {"text":"Value of Proper 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 color is gear up.
      - Players: A list of names of players on this team.
        
        The name of a role player on this squad.
  - DisplaySlots: A gear up of slots which are displaying specific objectives. If a slot is empty, its tag is not present.
    - slot_0: The internal name of the objective displayed in the "list" slot.
    - slot_1: The internal name of the objective displayed in the "sidebar" slot.
    - slot_2: The internal proper name of the objective displayed in the "belowName" slot.
    - slot_3: The internal proper noun of the objective displayed in the "sidebar.team.black" slot.
    - slot_4: The internal proper name of the objective displayed in the "sidebar.team.dark_blue" slot.
    - slot_5: The internal proper noun of the objective displayed in the "sidebar.team.dark_green" slot.
    - slot_6: The internal proper noun of the objective displayed in the "sidebar.team.dark_aqua" slot.
    - slot_7: The internal name of the objective displayed in the "sidebar.team.dark_red" slot.
    - slot_8: The internal proper name of the objective displayed in the "sidebar.squad.dark_purple" slot.
    - slot_9: The internal name of the objective displayed in the "sidebar.team.gold" slot.
    - slot_10: The internal name of the objective displayed in the "sidebar.team.gray" slot.
    - slot_11: The internal name of the objective displayed in the "sidebar.team.dark_gray" slot.
    - slot_12: The internal name of the objective displayed in the "sidebar.team.bluish" slot.
    - slot_13: The internal proper name of the objective displayed in the "sidebar.team.green" slot.
    - slot_14: The internal name of the objective displayed in the "sidebar.squad.aqua" slot.
    - slot_15: The internal name of the objective displayed in the "sidebar.team.red" slot.
    - slot_16: The internal name of the objective displayed in the "sidebar.team.light_purple" slot.
    - slot_17: The internal name of the objective displayed in the "sidebar.team.yellow" slot.
    - slot_18: The internal name of the objective displayed in the "sidebar.team.white" slot.

History [ ]

Coffee Edition
ane.5	13w04a	Added scoreboard.
ane.5	13w05a	Added squad-based functionality.
one.7.2	13w36a	Added statistic-based objective criteria.
one.8	14w02a	Entities other than players tin can now exist 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 actor name argument to correspond all players tracked by the scoreboard.
		Added the "objective" argument to `/scoreboard players reset`.
		Statistic objective criteria now employ named IDs instead of numerical IDs.
		Added the `achievement.overpowered` objective criterion.
	14w07a	Added `/scoreboard players operation` and `/scoreboard players examination`.
		Scores for imitation players that have a name beginning with "#" won't appear in the sidebar.
		Added team-specific sidebar brandish slots.
		Added the `nametagVisibility` team choice.
	14w10a	Added the `deathMessageVisibility` team choice.
		Added a `dataTag` argument to `/scoreboard players fix`, `/scoreboard players add`, and `/scoreboard players remove`.
		Added the `stat.crouchOneCm`, `stat.sprintOneCm`, and `stat.timeSinceDeath` objective criteria.
	14w25a	Added `=`, `<`, and `>` to `/scoreboard players performance`.
	14w29a	Histrion/entity names in the sidebar are now secondarily sorted by alphabetical order.
	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.
ane.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.drib` objective criteria.
	15w33a	Added the `armor`, `level` objective types.
	15w36a	Added `collisionRule`.
	15w49a	Added the `stat.aviateOneCm` objective criteria.
1.13	pre7	Added `/scoreboard objectives modify`.
	pre8	Added `/scoreboard objectives modify <objectiveName> rendertype hearts` , which makes wellness confined display as hearts, like this: .
		Added `/scoreboard objectives modify <objectiveName> rendertype integer` , which makes wellness confined display as yellow numbers.
		Objective names are now text components, not raw strings.
i.xiii.1	18w31a	Changed the scoreboard operator `%=` from using `%` to `Math.floorMod`.
1.18	21w37a	Removed 16-graphic symbol length limits for scoreboards, score holders and team names.
Bedrock Edition
1.7.0	beta 1.vii.0.ii	Added basic scoreboard mechanics.
1.7.0	beta 1.vii.0.ii	Added dummy scoreboards.

Bug [ ]

Problems relating to "Scoreboard" are maintained on the bug tracker. Report issues in that location.

References [ ]

Versions

Demo
- Locations
PC Gamer Demo (Beta 1.3)

Evolution

Version history	Pre-Classic Classic Early on Archetype Creative Multiplayer Test Survival Examination Tardily Classic Creative Indev Infdev Alpha Beta Total Release Development versions

Removed features
- Blocks
- Items
Unused features
Exclusive features
Mentioned features
- Heaven dimension
Planned versions

Technical

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

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

Development resources	Anvil file format Clamper format Control storage format Generated structures format Level format Boodle tables Map detail format Model NBT format Obfuscation map Player format raids.dat format Raw JSON text format Region file format Structure 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