Scoreboard

The scoreboard system is a complex gameplay mechanic intended mostly for map makers. It is used via commands and command blocks.

Objectives

Objectives are a combination of name, display name, and criteria, and track an integer number of points for players. The full score range is -2,147,483,648 to 2,147,483,647, and does not support decimals.

An objective's name is used internally when referenced in commands, target arguments, and in the file format. It is case-sensitive and must be a single word.

Conversely, the display name can be multiple words, and is displayed publicly in various situations. It is also case-sensitive, and does not have to be unique.

An objective's criteria determines its behavior:

Criteria	Description	Can be Modified?
dummy	Score is only changed by commands, and not by game events such as death. This is useful for event flags, state mappings, and currencies.	Yes
trigger	Score is only changed by commands, and not by game events such as death. The /trigger command can be used by a player to set or increment/decrement their own score in an objective with this criteria. The /trigger command will fail if the objective has not been "enabled" for the player using it, and the objective will be disabled for the player after they use the /trigger command on it. Note that the /trigger command can 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.	Yes
deathCount	Score increments automatically for a player when they die.	Yes
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.	Yes
health	Ranges from 0 to 20 on a normal player; represents the amount of half-hearts the player has. May appear as 0 for players before their health has changed for the first time. Extra hearts and absorption hearts also count to the health score, meaning that with Attributes/Modifiers or the Health Boost or Absorption Status effects, health can far surpass 20.	No

In snapshot 13w36a, hundreds of new criteria were added. These criteria use the Statistics and Achievements systems to form compound criteria. Unlike the simple criteria above, compound criteria have multiple parts, separated by periods ("."). For example, "stat.entityKilledBy.Zombie" would be a compound criterion, which would increment for a player whenever a zombie kills them.

A list of known compound criteria follows:

Criteria Base	Description	Can be Modified?	Number of sub-criteria
achievement	Accepted sub-criteria are: "acquireIron", "bakeCake", "blazeRod", "bookcase", "breedCow", "buildBetterPickaxe", "buildFurnace", "buildHoe", "buildPickaxe", "buildSword", "buildWorkBench", "cookFish", "diamonds", "diamondsToYou", "enchantments", "exploreAllBiomes", "flyPig", "fullBeacon", "ghast", "killCow", "killEnemy", "killWither", "makeBread", "mineWood", "onARail", "openInventory", "overkill", "overpowered", "portal", "potion", "snipeSkeleton", "spawnWither", "theEnd", and "theEnd2". Value is dependent on how many times the player has gotten the achievement (e.g. if a player has picked up three blocks of wood, their score for an objective with the "achievement.mineWood" criterion will be 3).	Yes	34
stat	Base for criteria related to a player's statistics. Accepted sub-criteria are: "animalsBred", "boatOneCm", "climbOneCm", "damageDealt", "damageTaken", "deaths", "diveOneCm", "drop", "fallOneCm", "fishCaught", "flyOneCm", "horseOneCm", "jump", "junkFished", "leaveGame", "minecartOneCm", "mobKills", "pigOneCm", "playerKills", "playOneMinute", "swimOneCm", "treasureFished", and "walkOneCm". Score increments automatically for a player when they perform the action specified by the sub-criterion.	Yes	23
stat.craftItem	The sub-criteria are the ID number (such as "stat.craftItem.1") or ID name (such as "stat.craftItem.minecraft.stone" - note that the "minecraft." is required for ID names) of a block or item. Only IDs of craftable or smeltable blocks and items are accepted. The value increments when the block or item is removed from a furnace, crafting table, or the inventory's crafting field. Clicking to remove increments the value by one, but shift-clicking increments it by two. Accepted Numeric IDs 1, 5, 20, 22-25, 27-29, 33, 35, 41, 42, 44-48, 50, 53, 54, 57, 58, 61, 65-67, 69, 70, 72, 76-79, 80, 82, 84, 85, 89, 91, 95, 96, 98, 101-103, 107-109, 112-114, 116, 123, 126, 128, 130, 131, 133-136, 138, 139, 143, 145-148, 151, 152, 154-160, 163-165, 167, 170-173, 256-259, 261-286, 290-294, 296-317, 320-325, 328, 330, 331, 333, 336, 339-343, 345-347, 350, 351, 353-357, 359, 361, 362, 364, 366, 371, 374, 376-382, 385, 386, 388-390, 393, 395, 396, 398, 400, 404-408, and 420 Accepted ID Names acacia_stairs, activator_rail, anvil, arrow, baked_potato, beacon, bed, birch_stairs, blaze_powder, boat, book, bookshelf, bow, bowl, bread, brewing_stand, brick, brick_block, brick_stairs, bucket, cake, carpet, carrot_on_a_stick, cauldron, chainmail_boots, chainmail_chestplate, chainmail_helmet, chainmail_leggings, chest, chest_minecart, clay, clock, coal, coal_block, cobblestone_wall, comparator, compass, cooked_beef, cooked_chicken, cooked_fish, cooked_porkchop, cookie, crafting_table, dark_oak_stairs, daylight_detector, detector_rail, diamond, diamond_axe, diamond_block, diamond_boots, diamond_chestplate, diamond_helmet, diamond_hoe, diamond_leggings, diamond_pickaxe, diamond_shovel, diamond_sword, dispenser, dropper, dye, emerald, emerald_block, enchanting_table, ender_chest, ender_eye, fence, fence_gate, fermented_spider_eye, fire_charge, fishing_rod, flint_and_steel, flower_pot, furnace, furnace_minecart, glass, glass_bottle, glass_pane, glowstone, gold_block, gold_ingot, gold_nugget, golden_apple, golden_axe, golden_boots, golden_carrot, golden_chestplate, golden_helmet, golden_hoe, golden_leggings, golden_pickaxe, golden_rail, golden_shovel, golden_sword, hardened_clay, hay_block, heavy_weighted_pressure_plate, hopper, hopper_minecart, iron_axe, iron_bars, iron_block, iron_boots, iron_chestplate, iron_door, iron_helmet, iron_hoe, iron_ingot, iron_leggings, iron_pickaxe, iron_shovel, iron_sword, iron_trapdoor, item_frame, jukebox, jungle_stairs, ladder, lapis_block, lead, leather_boots, leather_chestplate, leather_helmet, leather_leggings, lever, light_weighted_pressure_plate, lit_pumpkin, magma_cream, map, melon_block, melon_seeds, minecart, mossy_cobblestone, mushroom_stew, nether_brick, nether_brick_fence, nether_brick_stairs, netherbrick, noteblock, oak_stairs, painting, paper, piston, planks, pumpkin_pie, pumpkin_seeds, quartz, quartz_block, quartz_stairs, rail, redstone, redstone_block, redstone_lamp, redstone_torch, repeater, sandstone, sandstone_stairs, shears, sign, slime, slime_ball, snow, snow_layer, speckled_melon, spruce_stairs, stained_glass, stained_glass_pane, stained_hardened_clay, stick, sticky_piston, stone, stone_axe, stone_brick_stairs, stone_button, stone_hoe, stone_pickaxe, stone_pressure_plate, stone_shovel, stone_slab, stone_stairs, stone_sword, stonebrick, sugar, tnt, tnt_minecart, torch, trapdoor, trapped_chest, tripwire_hook, wheat, wooden_axe, wooden_button, wooden_door, wooden_hoe, wooden_pickaxe, wooden_pressure_plate, wooden_shovel, wooden_slab, wooden_sword, wool, and writable_book Certain items, such as iron ingots, pickaxes, and cake, have achievement counterparts that increment in the same way.	Yes	199 (398)
stat.useItem	The sub-criteria are the ID number (such as "stat.useItem.1") or ID name (such as "stat.useItem.minecraft.stone") of a block or item. Most blocks and items are accepted, except various blocks which do not have an item form. Accepted Numeric IDs 1-25, 27-33, 35, 37-54, 56-58, 60-62, 65-67, 69, 70, 72, 73, 76-82, 84-91, 95-103, 106-114, 116, 119-123, 125-131, 133-139, 141-143, 145-148, 151-167, 170-175, 256-408, 417-422, and 2256-2267 Accepted ID Names acacia_stairs, activator_rail, anvil, apple, arrow, baked_potato, barrier, beacon, bed, bedrock, beef, birch_stairs, blaze_powder, blaze_rod, boat, bone, book, bookshelf, bow, bowl, bread, brewing_stand, brick, brick_block, brick_stairs, brown_mushroom, brown_mushroom_block, bucket, cactus, cake, carpet, carrot, carrot_on_a_stick, carrots, cauldron, chainmail_boots, chainmail_chestplate, chainmail_helmet, chainmail_leggings, chest, chest_minecart, chicken, clay, clay_ball, clock, coal, coal_block, coal_ore, cobblestone, cobblestone_wall, cocoa, command_block, command_block_minecart, comparator, compass, cooked_beef, cooked_chicken, cooked_fish, cooked_porkchop, cookie, crafting_table, dark_oak_stairs, daylight_detector, deadbush, detector_rail, diamond, diamond_axe, diamond_block, diamond_boots, diamond_chestplate, diamond_helmet, diamond_hoe, diamond_horse_armor, diamond_leggings, diamond_ore, diamond_pickaxe, diamond_shovel, diamond_sword, dirt, dispenser, double_plant, double_stone_slab, double_wooden_slab, dragon_egg, dropper, dye, egg, emerald, emerald_block, emerald_ore, enchanted_book, enchanting_table, end_portal, end_portal_frame, end_stone, ender_chest, ender_eye, ender_pearl, experience_bottle, farmland, feather, fence, fence_gate, fermented_spider_eye, filled_map, fire, fire_charge, firework_charge, fireworks, fish, fishing_rod, flint, flint_and_steel, flower_pot, flowing_lava, flowing_water, furnace, furnace_minecart, ghast_tear, glass, glass_bottle, glass_pane, glowstone, glowstone_dust, gold_block, gold_ingot, gold_nugget, gold_ore, golden_apple, golden_axe, golden_boots, golden_carrot, golden_chestplate, golden_helmet, golden_hoe, golden_horse_armor, golden_leggings, golden_pickaxe, golden_rail, golden_shovel, golden_sword, grass, gravel, gunpowder, hardened_clay, hay_block, heavy_weighted_pressure_plate, hopper, hopper_minecart, ice, iron_axe, iron_bars, iron_block, iron_boots, iron_chestplate, iron_door, iron_helmet, iron_hoe, iron_horse_armor, iron_ingot, iron_leggings, iron_ore, iron_pickaxe, iron_shovel, iron_sword, iron_trapdoor, item_frame, jukebox, jungle_stairs, ladder, lapis_block, lapis_ore, lava, lava_bucket, lead, leather, leather_boots, leather_chestplate, leather_helmet, leather_leggings, leaves, leaves2, lever, light_weighted_pressure_plate, lit_furnace, lit_pumpkin, log, log2, magma_cream, map, melon, melon_block, melon_seeds, milk_bucket, minecart, mob_spawner, monster_egg, mossy_cobblestone, mushroom_stew, mycelium, name_tag, nether_brick, nether_brick_fence, nether_brick_stairs, nether_star, nether_wart, netherbrick, netherrack, noteblock, oak_stairs, obsidian, packed_ice, painting, paper, piston, planks, poisonous_potato, porkchop, portal, potato, potatoes, potion, pumpkin, pumpkin_pie, pumpkin_seeds, quartz, quartz_block, quartz_ore, quartz_stairs, rail, record_11, record_13, record_blocks, record_cat, record_chirp, record_far, record_mall, record_mellohi, record_stal, record_strad, record_wait, record_ward, red_flower, red_mushroom, red_mushroom_block, redstone, redstone_block, redstone_lamp, redstone_ore, redstone_torch, reeds, repeater, rotten_flesh, saddle, sand, sandstone, sandstone_stairs, sapling, shears, sign, skull, slime, slime_ball, snow, snow_layer, snowball, soul_sand, spawn_egg, speckled_melon, spider_eye, sponge, spruce_stairs, stained_glass, stained_glass_pane, stained_hardened_clay, stick, sticky_piston, stone, stone_axe, stone_brick_stairs, stone_button, stone_hoe, stone_pickaxe, stone_pressure_plate, stone_shovel, stone_slab, stone_stairs, stone_sword, stonebrick, string, sugar, tallgrass, tnt, tnt_minecart, torch, trapdoor, trapped_chest, tripwire_hook, vine, water, water_bucket, waterlily, web, wheat, wheat_seeds, wooden_axe, wooden_button, wooden_door, wooden_hoe, wooden_pickaxe, wooden_pressure_plate, wooden_shovel, wooden_slab, wooden_sword, wool, writable_book, written_book, and yellow_flower The value increments when a player uses a block or item. "Use" is defined as when: A shovel, a pickaxe, an axe, flint and steel, shears, a hoe, or a sword consumes durability. This does not apply to anything else with durability: helmets, chestplates, leggings, boots, bows, fishing rods, or "carrot on a stick"s. A block would be placed; a block does not have to be placed or even have the possibility of being placed. Certain blocks have specific conditions to be placed but increment the value whether a block can and is placed, for instance, sugar cane requires water to be directly horizontally adjacent to the block on which it is being placed and needs to be placed on top of either sand, red sand, dirt, podzol, or a grass block but increments the value when the player right clicks (or whatever the "Use Item/Place Block" control is) on any block. A painting, spawn egg, any type of minecart, or item frame spawns an entity. This does not apply to when a boat or any projectile is spawned from an eye of ender, ender pearl, egg, snowball, bow, Bottle o' Enchanting, or any throwable potions. One of the two usable dyes are properly used. Either when cocoa beans place cocoa pods on jungle wood or bone meal is used to grow plants, such as crops or grass. A record is placed in a jukebox. Each record has a different stat. The value, however, does not increment when any milk, potions, or any "foodstuffs" is consumed; items are used to name, tame, feed, breed, saddle, or leash mobs; when a new item is created through use, like when an empty map becomes a map, when a bucket becomes a lava bucket, water bucket, or milk or vice versa, or when a bowl becomes mushroom stew; and all instances mentioned above. There are 357 items attainable in creative mode, without using commands and including blocks with similar IDs but different datavalues, that can use this stat and 195 that cannot.	Yes	318 (636)
stat.breakItem	The sub-criteria are the ID number (such as "stat.breakItem.256") or ID name (such as "stat.breakItem.minecraft.bow") of an item with durability. Accepted Numeric IDs 256-259, 261, 267-279, 283-286, 290-294, 298-317, 346, 359, and 398 Accepted ID Names bow, carrot_on_a_stick, chainmail_boots, chainmail_chestplate, chainmail_helmet, chainmail_leggings, diamond_axe, diamond_boots, diamond_chestplate, diamond_helmet, diamond_hoe, diamond_leggings, diamond_pickaxe, diamond_shovel, diamond_sword, fishing_rod, flint_and_steel, golden_axe, golden_boots, golden_chestplate, golden_helmet, golden_hoe, golden_leggings, golden_pickaxe, golden_shovel, golden_sword, iron_axe, iron_boots, iron_chestplate, iron_helmet, iron_hoe, iron_leggings, iron_pickaxe, iron_shovel, iron_sword, leather_boots, leather_chestplate, leather_helmet, leather_leggings, shears, stone_axe, stone_hoe, stone_pickaxe, stone_shovel, stone_sword, wooden_axe, wooden_hoe, wooden_pickaxe, wooden_shovel, and wooden_sword The value increments when the durability runs out. The durability runs out when the condition for losing durability for the item is met, and the durability becomes negative, which is the first use after the durability is zero.	Yes	50 (100)
stat.mineBlock	The sub-criteria are the ID number (such as "stat.mineBlock.1") or ID name (such as "stat.mineBlock.minecraft.stone") of a block. Most blocks are accepted, except for various indestructible or technical blocks. Accepted Numeric IDs 1-6, 12-25, 27-33, 35, 37-50, 53, 54, 56-58, 60-62, 65-67, 69, 70, 72, 73, 76-82, 84-91, 95, 97-103, 106-114, 116, 119-123, 125-131, 133-139, 143, 145-148, 151-165, and 170-175 Accepted ID Names acacia_stairs, activator_rail, anvil, beacon, birch_stairs, bookshelf, brick_block, brick_stairs, brown_mushroom, brown_mushroom_block, cactus, carpet, chest, clay, coal_block, coal_ore, cobblestone, cobblestone_wall, cocoa, command_block, crafting_table, dark_oak_stairs, daylight_detector, deadbush, detector_rail, diamond_block, diamond_ore, dirt, dispenser, double_plant, double_stone_slab, double_wooden_slab, dragon_egg, dropper, emerald_block, emerald_ore, enchanting_table, end_portal, end_portal_frame, end_stone, ender_chest, farmland, fence, fence_gate, furnace, glass, glass_pane, glowstone, gold_block, gold_ore, golden_rail, grass, gravel, hardened_clay, hay_block, heavy_weighted_pressure_plate, hopper, ice, iron_bars, iron_block, iron_ore, jukebox, jungle_stairs, ladder, lapis_block, lapis_ore, leaves, leaves2, lever, light_weighted_pressure_plate, lit_furnace, lit_pumpkin, log, log2, melon_block, monster_egg, mossy_cobblestone, mycelium, nether_brick, nether_brick_fence, nether_brick_stairs, netherrack, noteblock, oak_stairs, obsidian, packed_ice, piston, planks, portal, pumpkin, quartz_block, quartz_ore, quartz_stairs, rail, red_flower, red_mushroom, red_mushroom_block, redstone_block, redstone_lamp, redstone_ore, redstone_torch, sand, sandstone, sandstone_stairs, sapling, slime, snow, snow_layer, soul_sand, sponge, spruce_stairs, stained_glass, stained_glass_pane, stained_hardened_clay, sticky_piston, stone, stone_brick_stairs, stone_button, stone_pressure_plate, stone_slab, stone_stairs, stonebrick, tallgrass, tnt, torch, trapped_chest, tripwire_hook, vine, waterlily, web, wooden_button, wooden_pressure_plate, wooden_slab, wool, and yellow_flower This increments when a player mines a block. "Mine" is defined as when a player destroys a block in a way that an item could/would drop, unless the block does not drop items like glass, or another block would be created like ice. The value does not increase when in Creative mode and will still increase if doTileDrops is set to false.	Yes	135 (270)
stat.killEntity	The sub-criteria are the name of an entity. Valid names are: "Bat", "Blaze", "CaveSpider", "Chicken", "Cow", "Creeper", "Enderman", "EntityHorse", "Ghast", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "Sheep", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf", and "Zombie". Increments when a player has killed the specified mob.	Yes	24
stat.entityKilledBy	The sub-criteria are the name of an entity. Valid names are: "Bat", "Blaze", "CaveSpider", "Chicken", "Cow", "Creeper", "Enderman", "EntityHorse", "Ghast", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "Sheep", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf", and "Zombie". Increments when a player has been killed by the specified mob. Note that if the name of a passive mob is used the value will never increase, as those mobs are not capable of hurting the player.	Yes	24
teamkill	The sub-criteria are the color of a team. Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Increments when a player has killed a member of a team with the specified color.	Yes	16
killedByTeam	The sub-criteria are the color of a team. Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Increments when a player has been killed by a member of a team with the specified color.	Yes	16

A player's score in any objective may be changed via commands, unless it is read-only (currently, only objectives with the 'health' criterion are read-only). It may be increased or decreased by a specific amount, or set to a specific value. For objectives based upon stats or achievements, the objective can be changed via commands, however the actual stat or achievement doesn't change. The objective will continue to update with changes in stats or achievements.

Command blocks can also be used to check a player's score for any objective, with the arguments score_name and score_name_min. In these arguments, name is the internal name of the objective to test for. score_name passes players with at most the specified number of points, while score_name_min passes players with at least the specified number of points.

For example, "testfor @p[score_deaths=5,score_deaths_min=1]" in a Command Block will make a comparator provide output if a player has died at least once and has died no more than 5 times, assuming "deaths" is an objective of the "deathCount" criterion.

Display slots

Via the "scoreboard objectives setdisplay" command (see 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 without a heading on the tab menu, where online players are shown. Visible even in singleplayer.
sidebar	Shows on the right hand side of the screen. Shows players in a high score list with a heading labeled the objective's display name. Note that offline players may be shown, and untracked players will not be shown.
sidebar.team.<color>	There are 16 team-specific sidebar display slots. These operate the same as the standard sidebar slot, but only 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", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white".
belowName	Shows the score followed by the objective's display name below the player's nameplate above their head. Is hidden beyond ~10 blocks and when the player is sneaking. Not visible in singleplayer.

Teams

Teams are a combination of name, display name, prefix, suffix, friendly fire option, and a list of players who are on the team.

As with objectives, the name and display name of a team are case-sensitive, name is a single word used internally, and display name can be multiple words and does not need to be unique.

The prefix and suffix are inserted before and after the names of players on a team - without using external editors, the only possible prefixes are formatting codes for team colors, and the only possible suffix is the reset code (so characters after a player's name aren't formatted). Prefixes and suffixes will be added to the names of players in chat, the active players list, the sidebar, and above their heads.

The friendly fire option allows control of whether team members can harm each other. Its default mode, "true", makes no changes to PvP mechanics. When set to "false", however, it prevents players on the same team from causing damage to each other with melee attacks, bows, and Splash Potions of Harming. Note that players on the same team may still inflict negative status effects on each other with potions, even if friendly fire is false.

It is important to note that each individual player can only be on one team; teams cannot share players.

Command blocks can be used to check whether a player is on a team with the "team" argument; the "!" character may be placed before a name to check for players not on the team. For example, "testfor @p[team=red]" in a Command Block will provide comparator output if a player is on the "red" team. Similarly, "testfor @p[team=!red,team=!blue]" will provide output for players who are neither on "red" nor "blue". Also, if checking for a blank team, the game will actually check for all players without a team.

Command reference

Command	Description	Success Conditions
scoreboard <objectives|players|teams>	The base command of the scoreboard system.	N/A
scoreboard objectives list	Lists all existing objectives, with their display name and criteria.	The scoreboard must have at least one objective.
scoreboard objectives add <name> <criteria> [display name...]	Creates a new objective with the internal name name, specified criteria, and the optional display name. Without a specified display name, it will default to name. See above section for the meaning of these properties. All arguments are case-sensitive.	name must not be used by an existing objective, and must be at most 16 characters. criteria must be a valid criteria type. display name must be at most 32 characters.
scoreboard objectives remove <name>	Deletes all references to the objective with name in the scoreboard system. Data is deleted from the objectives list, player scores, and if it was on a display list, it will no longer be displayed.	name must be an existing objective.
scoreboard objectives setdisplay <slot> [objective]	Display Slots]. Note that the objective parameter is optional: if no objective is provided, this display slot is cleared (returned to its default state).	objective must exist, if it is specified. slot must also exist. Note that clearing an empty slot will still succeed.
scoreboard players list [playername]	Displays all players who are tracked, in some way, by the scoreboard system. The optional playername parameter can be used to display all scores of a particular player, and "*" (an asterisk) in place of playername will display all scores for all players tracked by the scoreboard system.	playername must have recorded scores, if specified. If no playername is specified, there must be at least one tracked player on the scoreboard.
scoreboard players set <player> <objective> <score>	Sets the player's score in objective to score, overwriting the previous score if it exists. "*" (an asterisk) may be used in place of player to represent every player tracked by the scoreboard.	objective must exist and cannot be read-only, and score must be between -2,147,483,648 and 2,147,483,647, inclusive. Note that player does not need to be online or even exist.
scoreboard players add <player> <objective> <count>	Increments the player's score in objective by count. "*" may be used to represent all players tracked by the scoreboard.	objective must exist and cannot be read-only, and count must be between 1 and 2,147,483,647, inclusive. Note that player does not need to be online or even exist.
scoreboard players remove <player> <objective> <count>	Decrements the player's score in objective by count. "*" may be used to represent all players tracked by the scoreboard.
scoreboard players reset <player> [objective]	Deletes score or all scores for player. If objective is specified, only that objective is cleared; otherwise this applies to all objectives. Note this does not merely set the score(s) to 0: it removes the player from the scoreboard altogether (or for the given objective). "*" may be used to represent all players tracked by the scoreboard.	Always succeeds, even on players who are not on the scoreboard.
scoreboard players enable <player> <trigger>	Enables player to use the /trigger command on the specified trigger objective. Until this has been done, player's attempts to /trigger that objective will fail. Once they have used the /trigger command on it, it will be disabled again. "*" may be used to represent all players tracked by the scoreboard.	trigger must be an objective of the criteria "trigger".
scoreboard players test <player> <objective> <min> [max]	Outputs whether or not player's score in objective is within the range min to max (inclusive). If not specified, max defaults to 2,147,483,647. "*" may be used to represent all players tracked by the scoreboard.	objective must exist, and player's score in it must exist and be at least min and no greater than max. Note that player does not need to be online or even exist.
scoreboard players operation <targetName> <targetObjective> <operation> <selector> <objective>	Applies an arithmetic operation altering targetName's score in targetObjective, using selector's score in objective as input. operation may be "+=" (Addition: add selector's score to targetName's), "-=" (Subtraction: subtract selector's score from targetName's), "*=" (Multiplication: set targetName's score to the product of targetName and selector's scores), "/=" (Integer Division: set targetName's score to itself divided by selector's score), and "%=" (Modular Division: set targetName's score to the remainder of the division between itself and selector's score). In all cases, selector's score in objective will remain unchanged. "*" may be used in place of either targetName or selector (but not both) to represent all players tracked by the scoreboard.	objective and targetObjective must exist, targetObjective cannot be read-only, and all requested targets/selectors must have scores in the specified objectives (if some do and some do not, the operation will succeed only for the combinations where both the target and the selector have a score). Note that player does not need to be online or even exist.
scoreboard teams list [teamname]	Lists all teams, with their display names and the amount of players in them. The optional teamname parameter can be used to display all players on a particular team.	If teamname is specified, it must exist and must have players. If no teamname is specified, there must be at least one registered team on the scoreboard.
scoreboard teams add <name> [display name...]	Creates a team with the given name and optional display name.	name must not be used by an existing team, and must be at most 16 characters. display name must be at most 32 characters.
scoreboard teams remove <name>	Deletes the named team from the scoreboard system.	name must be an existing team.
scoreboard teams empty <name>	Removes all players from the named team.	name must be an existing team, and the team must have at least one player.
scoreboard teams join <team> [players...]	Assigns the specified players to the specified team. If no player is specified, the player running the command joins the team. "*" may be used to represent all players tracked by the scoreboard.	team must exist. Note that the named players do not need to be online or even exist, and can even already be on the team.
scoreboard teams leave [players...]	Makes the specified players leave their teams. If no player is specified, the player running the command leaves their team. "*" may be used to represent all players tracked by the scoreboard.	Each player must be on a team - it is possible to get a partial success and partial failure, but a command block will report only the failure.
scoreboard teams option <team> <color|friendlyfire|seeFriendlyInvisibles|nametagVisibility> <value>	The base command for team-specific settings.	N/A
scoreboard teams option <team> color <value>	Will color the name of all players on this team in chat, above their head, on the Tab menu, and on the sidebar. Valid color values are "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Another valid value is "reset" (names show in default color and formatting).	team must exist, and value must be a valid value.
scoreboard teams option <team> friendlyfire <true|false>	The default setting, true, has no impact on PvP mechanics. When set to false, players on this team cannot harm each other with melee, bow, or Splash Potion of Harming attacks, but may still inflict negative status effects on each other.	team must exist, and the setting must be "true" or "false".
scoreboard teams option <team> seeFriendlyInvisibles <true|false>	When set to true, players on this team will see invisible teammates (and themselves) as semi-transparent instead of completely invisible.	team must exist, and the setting must be "true" or "false".
scoreboard teams option <team> nametagVisibility <never|hideForOtherTeams|hideForOwnTeam|always>	Controls the visibility of nametags for players on the given team, and defaults to "always". When set to "never", no nametags will show above any player. When set to "hideForOtherTeams", only the nametags of players on other teams will be hidden. When set to "hideForOwnTeam", only nametags of other players on one's own team will be hidden. When set to "always", all nametags will be visible.	team must exist, and the setting must be "never", "hideForOtherTeams", "hideForOwnTeam", or "always".

NBT format

The file scoreboard.dat in the 'data' folder of a Minecraft world stores the scoreboard data 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 criteria of this objective. Must be "dummy", "deathCount", "playerKillCount", "totalKillCount", or "health".
        •  DisplayName: The display name of this objective. If none was specified during the objective's creation, this will be identical to the Name tag below.
        •  Name: The internal name of this objective.
    •  PlayerScores: A list 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 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.
    •  Teams: A list of compound tags representing teams.
      • A Team.
        •  AllowFriendlyFire: 1 or 0 (true/false) - true if players on this team can harm each other.
        •  SeeFriendlyInvisibles: 1 or 0 (true/false) - true if players on this team can see invisible teammates.
        •  DisplayName: The display name of this team. If none was specified during the team's creation, this will be identical to the Name tag below.
        •  Name: The internal name of this team.
        •  Prefix: The prefix prepended to names of players on this team. Ordinarily, it is a Formatting Code.
        •  Suffix: The suffix appended to names of players on this team. Ordinarily, it the reset code, "§r", to prevent formatting from spilling over, but it may be blank if prefix is also blank.
        •  Players: A list of names of players on this team.
          • The name of a player on this team.
    •  DisplaySlots: A set of slots which are displaying specific objectives.
      •  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 name of the objective displayed in the "belowName" slot.

History

r
1.5 {{Extension DPL}}<ul><li>[[Lead|Lead]]<br/>{{About|the item used for leashing and leading mobs|the element|Element#Lead}} {{Item | image = Lead.png | stackable = Yes (64) | renewable = Yes }} '''Leads''' are [[tool]]s used to leash and lead passive and neutral [[animal]]s, [[golem]]s and some [[monster]]s. == Obtaining == === Chest loot === {{LootChestItem|lead}} === Crafting === {{Crafting |A1= String |B1= String |A2= String |B2= Slimeball |C3= String |Output= Lead,2 |type= Tool }} === Mob loot === [[Wandering Trader|Wandering trader]]s always spawn with 2 [[llama|trader llama]]s, each held with a lead. When a trader llama is detached, either by killing it or the wandering trader, dragging them far apart, or putting the llama in a [[boat]] or a [[minecart]], the lead drops at the llama's position. == Usage == === Crafting ingredient === {{crafting usage}} === Leashing mobs === [[File:SuspendedPigs.png|190px|thumb|One block tall mobs, such as pigs, suspend at 7 blocks above the ground.]] [[File:SuspendedCows.png|190px|thumb|Two block tall mobs, such as cows, also suspend at 7 blocks above the ground.]] {{control|Using}} a lead on a [[mob]] ties the lead to the mob, allowing it to be moved by the player. Multiple mobs can be held by leads at once, but each mob held requires its own lead. It is possible to leash the following mobs and other entities: {{columns-list|colwidth=20em| * {{EntityLink|Allay}} * {{EntityLink|Axolotl}} * {{EntityLink|Bee}} * {{EntityLink|Boat}}{{only|bedrock}} * {{EntityLink|Camel}} * {{EntityLink|Cat}} * {{EntityLink|Chicken}} * {{EntityLink|Chicken Jockey}} (only the mount) * {{EntityLink|Cow}} * {{EntityLink|Dolphin}} * {{EntityLink|Donkey}} * {{EntityLink|Fox}} * {{EntityLink|Frog}} * {{EntityLink|Glow Squid}} * {{EntityLink|Goat}} * {{EntityLink|Hoglin}} * {{EntityLink|Horse}} * {{EntityLink|Iron Golem}} * {{EntityLink|Llama}} * {{EntityLink|Mooshroom}} * {{EntityLink|Mule}} * {{EntityLink|Ocelot}} * {{EntityLink|Parrot}} * {{EntityLink|Pig}} * {{EntityLink|Polar Bear}} * {{EntityLink|Rabbit}} * {{EntityLink|Sheep}} * {{EntityLink|Skeleton Horse}} * {{EntityLink|Skeleton Horseman}} (only the mount) * {{EntityLink|Sniffer}} * {{EntityLink|Snow Golem}} * {{EntityLink|Squid}} * {{EntityLink|Strider}} * {{EntityLink|Trader Llama}} * {{EntityLink|Wolf}} * {{EntityLink|Zoglin}} * {{EntityLink|Zombie Horse}}}} Additionally, [[villager]]s, [[wandering trader]]s, and [[monster]]s other than the ones listed above, can be leashed using a map editor or [[NBT]] editor. With a mob on a lead held by the player, {{control|using}} the lead on any type of [[fence]] (or [[wall]]{{only|bedrock|short=1}}) attaches the lead to it with a visible knot, tying the mob to it. To attach it to a wall on Bedrock Edition, the player must hold a lead in the main hand.<ref>{{bug|MCPE-108078}}</ref> Multiple leads may be attached to one fence post. A mob tied to a fence tends to stay within 5 blocks of the fence post. A lead is broken by pressing the {{control|use item}} control on the mob again, hitting the knot, or removing the attached fence post. Leads also break when hit by projectiles. Whenever a lead is removed or broken, it drops as an [[item (entity)|item]] at the location of the mob. However, it does not drop when unleashed in Creative mode.{{only|java}}<ref>{{bug|MCPE-79639}}</ref> A lead does not break if the attached animal dies. A lead can stretch a maximum of 10 blocks. If the mob is able to move towards the player or fence post, it does so. If not, or if the mob is moving very quickly away from the player, the lead breaks. When the player or the knot is more than 7 blocks above the ground, the mob being leashed becomes suspended. Most mobs that can be leashed can still be leashed even if attacking the player leashing them, and any attached leads do not break. [[Wolf|Wolves]] cannot be leashed after becoming angry. Despite this, if they become angry while already leashed, the lead does not break, but it cannot be reattached when broken through other methods while the wolf is still angry. A lead attached to a hoglin breaks if it becomes a [[zoglin]]. A lead does not prevent mobs from despawning if they normally would despawn. When moving downwards and accelerating towards the ground, leashed mobs accumulate fall damage and take it if they hit the ground while still accelerating. When moving up or decelerating (such as when the lead is stretched to its limit), the fall distance is set to one block and the mob therefore does not take any fall damage if it touches the ground. If the player walks into and back out of a [[nether portal]] while holding a lead connected to a mob, the lead remains attached to the mob. However, if a mob attached to a lead walks into a nether portal, the lead breaks and drops as an item in the other dimension. A lead can be used to remove a mob from a boat without needing to break the boat, if the mob can normally be leashed. If a chunk unloads while containing a leashed mob (either by the player walking too far away, or traveling to another dimension via a portal), the lead breaks and drops as an item, leaving the mob free to wander around. == Sounds == {{Edition|Java}}: {{Sound table |sound=Lead Knot break1.ogg |sound2=Lead Knot break2.ogg |sound3=Lead Knot break3.ogg |subtitle=Leash Knot breaks |source=neutral |description=When a leash knot is destroyed |id=entity.leash_knot.break |translationkey=subtitles.entity.leashknot.break |volume=1.0 |pitch=1.0 |distance=16}} {{Sound table |sound=Lead Knot place1.ogg |sound2=Lead Knot place2.ogg |sound3=Lead Knot place3.ogg |subtitle=Leash Knot tied |source=neutral |description=When a leash knot is placed on a fence |id=entity.leash_knot.place |translationkey=subtitles.entity.leashknot.place |volume=1.0 |pitch=1.0 |distance=16 |foot=1}} {{Edition|Bedrock}}: {{Sound table |type=bedrock |sound=Lead Knot break1.ogg |sound2=Lead Knot break2.ogg |sound3=Lead Knot break3.ogg |source=neutral |description=When a leash knot is broken by {{ctrl|interacting}} with it |id=leashknot.break |volume=1.0 |pitch=1.0}} {{Sound table |sound=Lead Knot place1.ogg |sound2=Lead Knot place2.ogg |sound3=Lead Knot place3.ogg |source=neutral |description=When a leash knot is placed on a fence or wall |id=leashknot.place |volume=1.0 |pitch=1.0 |foot=1}} == Leash Knot == '''Leash knot''' is an entity created when the [[player]] right-clicks the fence while having a mob leashed. {{Entity| title = Leash Knot| image = Knot.png|imagesize= 100px|networkid='''[[JE]]''': 77}} === Data values === ==== ID ==== {{edition|java}}: {{ID table |edition=java |generatetranslationkeys=y |displayname=Leash Knot |spritetype=entity |nameid=leash_knot |foot=1}} {{edition|bedrock}}: {{ID table |edition=bedrock |shownumericids=y |notshowbeitemforms=y |generatetranslationkeys=y |displayname=Leash Knot |spritetype=entity |nameid=leash_knot |id=88 |foot=1}} ==== Entity data ==== Leash knots have entity data that define various properties of the entity. {{el|java}}: {{main|Entity format}} {{/ED}} {{el|bedrock}}: : See [[Bedrock Edition level format/Entity format]]. == Data values == === ID === {{edition|java}}: {{ID table |edition=java |showforms=y |generatetranslationkeys=y |displayname=Lead |spritetype=item |nameid=lead |form=item |foot=1}} {{edition|bedrock}}: {{ID table |edition=bedrock |shownumericids=y |showforms=y |notshowbeitemforms=y |generatetranslationkeys=y |displayname=Lead |spritetype=item |nameid=lead |id=547 |form=item |foot=1}} == Achievements == {{load achievements|So I Got That Going for Me}} == Advancements == {{load advancements|When the Squad Hops into Town}} == History == {{missing information|The history of a lot of mobs be leashed}} {{History|java}} {{History||1.6.1|snap=13w16a|[[File:Lead JE1 BE1.png|32px]] Added leads. |Leads do not currently have a tooltip and are called “leashes” in [http://www.mojang.com/2013/04/minecraft-snapshot-13w16a-and-new-launcher/ the change notes].}} {{History|||snap=13w16b|Leads have been given a tooltip.}} {{History|||snap=13w18a|Leads have been given a [[crafting]] recipe.}} {{History||1.9|snap=15w50a|Added a [[sound]] for leads: <code>entity.leashknot.place</code>.}} {{History||1.11|snap=16w32a|The [[entity]] ID of the knot has been changed from <code>LeashKnot</code> to <code>leash_knot</code>.}} {{History|||snap=16w39a|Leads can now be found in [[woodland mansion]] chests.}} {{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 420.}} {{History||1.14|snap=18w43a|[[File:Lead JE2 BE2.png|32px]] The texture of leads has been changed.}} {{History|||snap=19w05a|Added [[wandering trader]]s, which are naturally equipped with leads.}} {{History||1.15|snap=?|[[Bee]]s can now be leashed.}} {{History||1.16|snap=20w09a|[[Skeleton horse]]s and [[zombie horse]]s can now be leashed.<ref>{{bug|MC-166246}}</ref>}} {{History|||snap=?|[[Hoglin]]s can now be leashed.}} {{History||1.16.2|snap=20w27a|[[Zoglin]]s can now be leashed.}} {{History||1.17|snap=21w19a|[[Squid]]s and [[glow squid]]s can now be leashed.<ref>{{bug|MC-136647}}</ref>}} {{History|||snap=?|[[Axolotl]]s can now be leashed.}} {{History||1.19|snap=22w13a|Lead may now be found in [[ancient city]] [[chest]]s.}} {{History|||snap=?|[[Frog]]s can now be leashed.}} {{History||1.19.3|snap=22w42a|[[Camel]]s can now be leashed.|Mobs no longer accumulate fall damage when dangling on leads.<ref>{{bug|MC-14167||Mobs build up fall damage when dangling on a lead|Fixed}}</ref>}} {{History||1.20 (Experimental)|link=1.19.4|snap=?|[[Sniffer]]s can now be leashed.}} {{History||1.20|snap=23w12a|Lead can now be found in [[suspicious gravel]] and [[suspicious sand]] in [[trail ruins]].}} {{History|||snap=23w16a|Lead no longer generates in [[suspicious sand]] in [[trail ruins]].|Due to the split of the archaeological loot tables for the suspicious gravel within the [[trail ruins]]; lead now is in the common loot.}} {{History|pocket alpha}} {{History||v0.15.0|snap=build 1|[[File:Lead JE1 BE1.png|32px]] Added leads.}} {{History|pocket}} {{History||1.1.0|snap=alpha 1.1.0.0|Leads now have better "physics". |The [[entity]] ID of the knot has been changed from <code>leashknot</code> to <code>leash_knot</code>. |Leads can now be found inside [[woodland mansion]] [[chest]]s.}} {{History|bedrock}} {{History||1.4.0|snap=beta 1.2.14.2|Leads can now be found inside [[buried treasure]] [[chest]]s. |Leads can now be used on [[boat]]s.}} {{History||1.4.0|snap=beta 1.2.20.1|Leads can now be used to craft [[balloon]]s.}} {{History||1.10.0|snap=beta 1.10.0.3|[[File:Lead JE2 BE2.png|32px]] The texture of leads has been changed. |[[Wandering trader]]s now [[drops|drop]] leads after they are detached from trader [[llama]]s.}} {{History||1.14.0|snap=beta 1.14.0.1|Leads can now be used on [[polar bear]]s, [[ocelot]]s, [[parrot]]s, [[dolphin]]s and old [[villager]]s.}} {{History||1.19.0|snap=beta 1.19.0.20|Allays can now be leashed.}} {{History|console}} {{History||xbox=TU19|xbone=CU7|ps=1.12|wiiu=Patch 1|switch=1.0.1|[[File:Lead JE1 BE1.png|32px]] Added leads.}} {{History||xbox=TU43|xbone=CU33|ps=1.36|wiiu=Patch 13|[[Sound]]s have been added for leads.}} {{History|Ps4}} {{History||1.90|[[File:Lead JE2 BE2.png|32px]] The texture of leads has been changed.}} {{History|3ds}} {{History||0.1.0|[[File:Lead JE1 BE1.png|32px]] Added leads.}} {{History|foot}} == Issues == {{issue list|Lead|Leash}} == Trivia == [[File:Steve wearing Lead.png|100px]] [[File:Alex wearing Lead.png|100px]] * The lead is named as "leash" in the texture file. * If a [[player]] goes to sleep while holding a mob on a lead, the lead remains attached. * {{IN|Java}}, when using the {{cmd|item}} command to put a lead in a player's head slot, the item gets rotated and positioned in such a way that it looks like the player is wearing a monocle. == Gallery == <gallery> Multiple_Leash.png|Many animals can be tied to one fence post. HorseLeashedOnAFence.png|A [[horse]] wearing [[golden horse armor]] that is leashed to a fence post. ThreeTiedSheep.png|Three sheep tied to the same fence. More accurate lead mobs.png|A shot of all the mobs that could be tied with leads as of 1.6.1, except donkeys and mules. Yo Yo.png|With the use of the leash, it is possible to suspend animals in the air by tying the leash on high-up fence posts. YoYo.png|A [[donkey]] with the Grumm/Dinnerbone [[name tag]] [[easter egg]] tied to a fence with a lead to make a yo-yo. Flying_Sheep.png|Several [[sheep]] hanging in the air in [[Creative]] mode. Pocket Edition Lead.jpg|First image of a lead in ''Bedrock Edition''. </gallery> == References == {{Reflist}} == External Links == *[https://www.minecraft.net/en-us/article/taking-inventory-lead Taking Inventory: Lead] – Minecraft.net on April 8, 2022 {{items}} {{entities}} [[Category:Tools]] [[de:Leine]] [[es:Rienda]] [[fr:Laisse]] [[hu:Lasszó]] [[it:Guinzaglio]] [[ja:リード]] [[ko:끈]] [[nl:Leidtouw]] [[pl:Smycz]] [[pt:Laço]] [[ru:Поводок]] [[th:เชือกจูง]] [[zh:拴绳]] [[Category:Renewable resources]]</li><li>[[:Category:Plants|Category:Plants]]<br/>All pages covering blocks of such things as tall grass and flowers. [[Category:Blocks]] [[Category:Items]] [[cs:Kategorie:Rostliny]] [[es:Categoría:Plantas]] [[fr:Catégorie:Plante]] [[hu:Kategória:Növények]] [[it:Categoria:Piante]] [[ja:カテゴリ:植物]] [[ko:분류:식물]] [[nl:Categorie:Planten]] [[pl:Kategoria:Rośliny]] [[pt:Categoria:Plantas]] [[ru:Категория:Растения]] [[th:หมวดหมู่:พืช]] [[zh:Category:植物]]</li></ul>		13w04a			Added scoreboard.
		13w05a			Added team based functionality to scoreboards.

Issues

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

Gallery

• 

  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 player is displayed in the "sidebar" slot.

References

Gameplay 

View at: Template:Gameplay/content [edit]