Minecraft Wiki
Advertisement
Scoreboard

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

The scoreboard system 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.

Objectives

Objectives consist of three main arguments, in order: a name, a criterion, and a display name. Objectives track a number of points for entities, and are displayed as integers with a full score range of -2,147,483,648 to 2,147,483,647.

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

Conversely, the display name of an objective 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 criterion determines its behavior, primarily what to track. A list of available criteria is provided below.

An entity's score in any objective may be changed via commands, unless it is read-only. It may be increased or decreased by a specific amount, or set to a specific value. For objectives based upon statistics, the objective can be changed via commands; however, the actual stat does not change - the objective will continue to update for players with changes in stats.

Commands can also be used to check an entity'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 entities with at most the specified number of points, while score_name_min passes entities with at least the specified number of points.

For example, inputting /testfor @p[score_deaths=5,score_deaths_min=1] into a command block will make a comparator or conditional command block 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.

Criteria

Criterion 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
xp Matches the total amount of experience the player has. 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 before their foodLevel has changed 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 player has. May appear as 0 for players before their armor has changed for the first time. No

Some criteria use the Statistics systems to form compound criteria.[1] 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.[2]

A list of known compound criteria follows:

Criteria Base Description Can be Modified? Number of sub-criteria
stat. Base for criteria related to a player's statistics. Score increments automatically for a player when they perform the action specified by the sub-criterion. Accepted sub-criteria are: "animalsBred", "armorCleaned", "aviateOneCm", "bannerCleaned", "beaconInteraction", "boatOneCm", "brewingstandInteraction", "cakeSlicesEaten", "cauldronFilled", "cauldronUsed", "chestOpened", "climbOneCm", "craftingTableInteraction", "crouchOneCm", "damageDealt", "damageTaken", "deaths", "dispenserInspected", "diveOneCm", "drop", "dropperInspected", "enderchestOpened", "fallOneCm", "fishCaught", "flowerPotted", "flyOneCm", "furnaceInteraction", "hopperInspected", "horseOneCm", "itemEnchanted", "jump", "leaveGame", "minecartOneCm", "mobKills", "noteblockPlayed", "noteblockTuned", "pigOneCm", "playOneMinute", "playerKills", "recordPlayed", "shulkerBoxOpened", "sleepInBed", "sneakTime", "sprintOneCm", "swimOneCm", "talkedToVillager", "timeSinceDeath", "tradedWithVillager", "trappedChestTriggered" and "walkOneCm". Yes 50
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. Yes 263 (398)[note 1]
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.

The value increments when a player uses a block or item. "Use" is defined as when:

The value, however, does not increment when items are used on mobs, whether to name, tame, feed, breed, saddle, leash, shear, milk, or gather stew from; when armor is put on directly; when leather armor is washed in a cauldron; 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)[note 1]
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.

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 that causes the item to break.

Yes 52 (100)[note 1]
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.

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 195 (270)[note 1]
stat.killEntity The sub-criteria are the name of an entity. Valid names are: "Bat", "Blaze", "CaveSpider", "Chicken", "Cow", "Creeper", "Enderman", "Endermite", "EntityHorse", "Ghast", "Guardian", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "PolarBear", "Rabbit", "Sheep", "Shulker", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf", and "Zombie". Increments when a player has killed the specified mob. Yes 43
stat.pickup The sub-criteria are the ID number (such as "stat.pickup.1") or ID name (such as "stat.pickup.minecraft.stone") of a block or item. Increments when a player picks up a dropped item. Yes 392
stat.drop The sub-criteria are the ID number (such as "stat.drop.1") or ID name (such as "stat.drop.minecraft.stone") of a block or item. Increments when a player drops an item by using drop item. Yes 392
stat.entityKilledBy The sub-criteria are the name of an entity. Valid names are: "Bat", "Blaze", "CaveSpider", "Chicken", "Cow", "Creeper", "Enderman", "Endermite", "EntityHorse", "Ghast", "Guardian", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "PolarBear", "Rabbit", "Sheep", "Shulker", "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 entity with the scoreboard. However it can be hurt by Rabbits and Chickens if the Rabbit was "The Killer Bunny", or the Chicken was a Chicken Jockey.

Yes 43
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
  1. a b c d Prior to 14w06a, stat.craftItem, stat.useItem, stat.breakItem, and stat.mineBlock only accepted numeric IDs and not ID names. The addition of ID names means that these compound criteria effectively have double the sub-criteria they previously had, but the new criteria serve the same exact roles as their numeric counterparts. For convenience, the first number listed is the number of blocks/items which these compound criteria accept, and the second is the literal number of sub-criteria.
Scoreboard Display

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.

Display slots

Via the /scoreboard objectives setdisplay command (see command reference), entities' 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 entities in a high score list with a heading labeled the objective's display name. Note that players will be shown even if offline, and untracked players will not be shown. In addition, fake players with names starting with a # will not show up in the sidebar under any circumstances.
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.

Tags

Scoreboard tags are a simple list of single-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 check whether an entity has a tag with the "tag" argument; the "!" character may be placed before a name to check for entities that do not have the tag. For example, inputting /testfor @p[tag=banana] into a command block will provide comparator output if a player is tagged with "banana". Similarly, /testfor @p[tag=!banana] will provide output for players who are not tagged "banana".

To test for multiple tags, use the data tag "Tags". For example, /testfor @p {Tags:["banana","apple"]} will check for a player that has both the "apple" and "banana" tags.

Teams

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

A team's name is used internally, for referencing in commands, target arguments, and in the file format. It is case-sensitive and must be a single word.

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

A team's prefix and suffix are inserted before and after the names of entities on the team, respectively. 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 an entity's name aren't formatted). Prefixes and suffixes will be added to the names of entities in chat, the active players list, the sidebar, and above their heads. Without an in-game option, third-party software may be required to edit them.

The friendly fire option allows control of whether or not members of a team are able to harm each other. Its default mode, true, makes no changes to PvP mechanics - ergo, players can harm their teammates. 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 entity can only be on one team; teams cannot share entities.

Commands can be used to check whether an entity is on a team with the "team" argument; the "!" character may be placed before a name to check for entities not on the team. For example, inputting /testfor @p[team=red] into a command block will provide comparator output if a player is on the "red" team. Similarly, /testfor @p[team=!red] will provide output for players who are not on "red". Also, /testfor @p[team=!] will check for all players on a team, while /testfor @p[team=] will check for those without a team.

Command reference

Objectives commands

Command Description Success Conditions[note 1]
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, entity 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] Displays score info for objective in the specified slot. Valid slots are listed and described in 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.

Players commands

Command Description Success Conditions[note 1]
scoreboard players list [entity] Displays all entities which are tracked, in some way, by the scoreboard system. The optional entity parameter can be used to display all scores of a particular entity, and "*" (an asterisk) in place of entity will display all scores for all entities tracked by the scoreboard system. entity must have recorded scores, if specified. If no entity is specified, there must be at least one tracked entity on the scoreboard.
scoreboard players set <entity> <objective> <score> [dataTag] Sets the entity's score in objective to score, overwriting the previous score if it exists. "*" may be used in place of entity to represent every entity 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 entity does not need to be online or even exist. If entity exists and a dataTag is specified, entity must match dataTag. Note that dataTag must define the type of tag such as {powered:1b} if looking for powered creepers.
scoreboard players add <entity> <objective> <count> [dataTag] Increments the entity's score in objective by count. "*" may be used to represent all entities 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 entity does not need to be online or even exist. If entity exists and a dataTag is specified, entity must match dataTag. Note that dataTag must define the type of tag such as {powered:1b} if looking for powered creepers.
scoreboard players remove <entity> <objective> <count> [dataTag] Decrements the entity's score in objective by count. "*" may be used to represent all entities tracked by the scoreboard.
scoreboard players reset <entity> [objective] Deletes score or all scores for entity. 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 entity from the scoreboard altogether (or for the given objective). "*" may be used to represent all entities tracked by the scoreboard. Always succeeds, even on entities who are not on the scoreboard.
scoreboard players enable <entity> <trigger> Enables entity to use the /trigger command on the specified trigger objective. This command accepts all entities, but only players are able to actually use the /trigger command. Until this has been done, players 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 entities tracked by the scoreboard. trigger must be an objective of the criteria "trigger".
scoreboard players test <entity> <objective> <min> [max] Outputs whether or not entity's score in objective is within the range min to max (inclusive). If not specified or if "*" is used, max defaults to 2,147,483,647. Using a "*" for min means -2,147,483,648. "*" may be used to represent all entities tracked by the scoreboard. objective must exist, and entity's score in it must exist and be at least min and no greater than max. Note that entity 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
  • "%=" Modular Division: set targetName's score to the remainder of the division between itself and selector's score
  • "=" Assign: set targetName's score to selector's score
  • "<" Min: if selector's score is less than targetName's score, then set targetName's score to selector's score
  • ">" Max: if selector's score is greater than targetName's score, then set targetName's score to selector's score
  • "><" Swaps the scores of selector with targetName

In all cases except "><", selector's score in objective will remain unchanged. "*" may be used in place of either targetName or selector (but not both) to represent all entities 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 targetName does not need to be online or even exist.

Tags commands

Command Description Success Conditions[note 1]
scoreboard players tag <entity> add <tagName> [dataTag] Adds a tag - tagName which can be based on a certain dataTag to/from a entity. "*" may be used in place of entity to represent all entities tracked by the scoreboard, provided the entities exist and are online.
scoreboard players tag <entity> remove <tagName> [dataTag] Removes a tag - tagName which can be based on a certain dataTag to/from a entity. "*" may be used in place of entity to represent all entities tracked by the scoreboard, provided the entities exist and are online. Tags that are to be removed must exist.
scoreboard players tag <entity> list Lists all tags the entity has. "*" may be used in place of entity to represent all entities tracked by the scoreboard, provided the entities exist and are online.

Teams commands

Command Description Success Conditions[note 1]
scoreboard teams list [teamname] Lists all teams, with their display names and the amount of entities in them. The optional teamname parameter can be used to display all entities on a particular team. If teamname is specified, it must exist and must have entities. 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 entities from the named team. name must be an existing team, and the team must have at least one entity.
scoreboard teams join <team> [entities...] Assigns the specified entities to the specified team. If no entities is specified, the entity running the command joins the team. "*" may be used to represent all entities tracked by the scoreboard. team must exist. Note that the named entities do not need to be online or even exist, and can even already be on the team.
scoreboard teams leave [entities...][note 2] Makes the specified entities leave their teams. If no entity is specified, the entity running the command leaves their team. "*" may be used to represent all entities tracked by the scoreboard. Each entity 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 <value> Will color the name of all entities on this team in chat, above their head, on the Tab menu, and on the sidebar. Also changes the color of the outline of the entities caused by the Glowing effect. 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. Does not affect non-player entities on a team. 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. Defaults to true. 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 entities on the given team, and defaults to "always". When set to "never", no nametags will show above any entity on the given team. When set to "hideForOtherTeams", the nametags of entities on the given team will be hidden to players not on the team. When set to "hideForOwnTeam", only nametags of other entities 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".
scoreboard teams option <team> deathMessageVisibility <never|hideForOtherTeams|hideForOwnTeam|always> Controls the visibility of death messages for players on the given team, and defaults to "always". When set to "never", no death messages will appear in chat for any player on the given team. When set to "hideForOtherTeams", only the death messages of players on other teams will be hidden. When set to "hideForOwnTeam", only death messages of other players on one's own team will be hidden. When set to "always", all death messages will appear in chat. team must exist, and the setting must be "never", "hideForOtherTeams", "hideForOwnTeam", or "always".
scoreboard teams option <team> collisionRule <always|never|pushOwnTeam|pushOtherTeams> Controls the way the entities on the team collide, defaults to "always". When set to "never", entities on that team will never collide with players or mobs. When set to "pushOwnTeam", entities will only push other entities on their team and mobs. When set to "pushOtherTeams", entities will only push entities on opposing teams. When set to "always", all players and mobs will be pushed. team must exist, and the setting must be "never", "pushOwnTeam", "pushOtherTeams", or "always".
  1. a b c d A command's Success Conditions must be met in order for the game to consider the command "successful". This is used to determine a variety of things, such as the output of a Redstone Comparator feeding from Command Block with a command. Note that not all "successful" commands actually do something, and not all "failed" commands fail to do something useful.
  2. If you use multiple entities for [entities...], the first one should be exist. This is because of MC-106681

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.
          •  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.
          •  RenderType: The type of data to store. Defaults to "integer".
      •  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.
          •  Locked: 1 or 0 (true/false) - false if this objective is "enabled". Only meaningful for objectives with the criteria "trigger", where this must be false before a player can use the /trigger command on it.
      •  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.
          •  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 option of this team. Valid options are: always, pushOwnTeam, never, pushOtherTeams
          •  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 is the reset code, "§r", to prevent formatting from spilling over, but it may be blank if prefix is also blank.
          •  TeamColor: The text-based color ("black", "dark_blue", etc.) given to the team. Does not exist if no color is set.
          •  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. 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 name of the objective displayed in the "belowName" slot.
        •  slot_3: The internal name of the objective displayed in the "sidebar.team.black" slot.
        •  slot_4: The internal name of the objective displayed in the "sidebar.team.dark_blue" slot.
        •  slot_5: The internal name of the objective displayed in the "sidebar.team.dark_green" slot.
        •  slot_6: The internal name 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 name of the objective displayed in the "sidebar.team.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.blue" slot.
        •  slot_13: The internal name of the objective displayed in the "sidebar.team.green" slot.
        •  slot_14: The internal name of the objective displayed in the "sidebar.team.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

release
1.5
  •  tag: Parent Tag
    •  Trim: Properties of Armor Trim.
      •  material: The material which decides the color of armor trim.
      •  pattern: The pattern of armor trim.


Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History

Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History

Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History

Template loop detected: Template:History Template loop detected: Template:History Template loop detected: Template:History

Armor durability from Indev until late Beta
Material Helmet Chestplate Leggings Boots
Leather 33 48 45 39
Golden 66 96 90 78
Chainmail 66 96 90 78

Iron

132 192 180 156
Diamond 264 384 360 312
13w04aAdded scoreboard.
13w05aAdded team-based functionality.
1.7.2
{{Extension DPL}}<ul><li>[[Chorus Fruit|Chorus Fruit]]<br/>{{about|the fruit that drops from [[chorus tree]]s|the building material|Popped Chorus Fruit|other uses|Chorus}}
{{Item
| title = Chorus Fruit
| image = Chorus Fruit.png
| renewable = Yes
| heals = {{hunger|4}}
| stackable = Yes (64)
}}

'''Chorus fruit''' is a [[food]] [[item]] native to [[the End]] that can be eaten, or [[smelting|smelted]] into [[Popped Chorus Fruit|popped chorus fruit]]. It can be eaten even when the hunger bar is full, and eating it may teleport the [[player]] up to 8 blocks in any direction.

== Obtaining ==
{{see also|Tutorials/Chorus fruit farming}}

Chorus fruit can be obtained by breaking [[Chorus Plant (block)|chorus plant blocks]]. Each block of chorus plant has a 50% chance to drop a chorus fruit. This is not affected by [[Fortune]].<ref>{{bug|MC-198924||Chorus Fruit doesn't have a higher chance with Fortune|Invalid}}</ref>

== Usage ==
To eat chorus fruit, press and hold {{control|use}} while it is selected in the hotbar. Eating one restores {{hunger|4}} [[hunger]] and 2.4 hunger [[Hunger#Mechanics|saturation]].

Unlike most foods, chorus fruits can be eaten even when the player has a full hunger bar.

The player may also be [[teleportation|teleported]]: up to 16 attempts are made to choose a random destination within ±8 on all three axes in the same manner as [[Enderman#Teleportation|enderman teleportation]], with the exception that the player may teleport into an area only 2 blocks high, or one block tall if the player is crawling. The player does not land in the average centroid of the block, but rather to any position within an 8-block range. The player will be teleported directly down to the ground regardless of the height it was used at if the player is too far from a valid destination.

The chorus fruit, unlike an [[Ender Pearl|ender pearl]], can teleport the player through [[solid block]]s. The algorithm tries to avoid [[fluid]]s; the player cannot teleport into a space occupied by [[water]] or [[lava]]. However, the player can be teleported onto dangerous blocks such as fire, cacti and magma blocks.<ref>{{bug|MC-102836||Enderman and chorus fruit can teleport to some dangerous places}}</ref>

If a teleport succeeds, a sound similar to an enderman teleporting plays originating from the teleportation origin location. Chorus fruit has a cooldown of 1 second before being able to be used again. The cooldown is represented by a white overlay on the chorus fruit in the hotbar. The cooldown is applied to all chorus fruits items, including those in the player's inventory and containers.<ref>{{bug|MC-88236|||WAI}}</ref>

Eating chorus fruit may teleport the player into areas protected by [[bedrock]], [[barrier|barrier blocks]], or other blocks that are otherwise unbreakable in [[Survival]] mode. However, it cannot teleport the player onto [[the Nether]] roof.<ref>{{bug|MC-84198|||Fixed}}</ref>

Chorus fruit is completely non-functional above the nether roof.

[[Fox]]es can also eat chorus fruit and the teleportation effect works the same as with players.

=== Smelting ingredient ===

{{smelting
|Chorus Fruit
|Popped Chorus Fruit
|0.1}}

== Sounds ==
===Generic===
{{Sound table/Entity/Food}}
===Unique===
{{edition|java}}:
{{Sound table
|rowspan=2
|sound=Teleport1.ogg
|sound2=Teleport2.ogg
|subtitle=Player teleports
|source=player
|description=When a player teleports by eating a chorus fruit
|id=item.chorus_fruit.teleport
|translationkey=subtitles.item.chorus_fruit.teleport
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|subtitle=Fox teleports
|source=Players & Friendly Creatures<wbr><ref group=sound>{{Bug|MC-257516||"Fox teleports" sound plays for both Players and Friendly Creatures sound categories}}</ref>|overridesource=1
|description=When a fox teleports by eating a chorus fruit
|id=entity.fox.teleport
|translationkey=subtitles.entity.fox.teleport
|volume=1.0
|pitch=1.0
|distance=16
|foot=1}}

{{edition|bedrock}}:
{{Sound table
|type=bedrock
|sound=Teleport1.ogg
|sound2=Teleport2.ogg
|source=hostile
|description=When something teleports by eating a chorus fruit
|id=mob.shulker.teleport
|volume=1.0
|pitch=1.0
|foot=1}}

==Data values ==

===ID===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Chorus Fruit
|spritetype=item
|nameid=chorus_fruit
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Chorus Fruit
|spritetype=item
|nameid=chorus_fruit
|id=558
|form=item
|foot=1}}

==Advancements==
{{load advancements|Husbandry;A Balanced Diet}}

==History==
{{History|java}}
{{History||1.9|snap=15w31a|[[File:Chorus Fruit JE1 BE1.png|32px]] Added chorus fruit.}}
{{History|||snap=15w34c|A cooldown for using chorus fruit has now been added.}}
{{History|||snap=15w37a|The chorus fruit's teleportation range has now been reduced from ±32 to ±8.}}
{{History|||snap=15w50a|Added a [[sound]] for chorus fruit: <code>item.chorus_fruit.teleport</code>.}}
{{History||1.10|snap=16w21a|Chorus fruit can now teleport riders off their mounts.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 432.}}
{{History||1.14|snap=18w43a|[[File:Chorus Fruit JE2 BE2.png|32px]] The texture of chorus fruit has now been changed.}}
{{History||1.20.2|snap=23w33a|Eating chorus fruit now resets fall distance.<ref>{{bug|MC-112133||Eating chorus fruit does not reset fall distance|Fixed}}</ref>}}

{{History|pocket}}
{{History||1.0.0|snap=alpha 0.17.0.1|[[File:Chorus Fruit JE1 BE1.png|32px]] Added chorus fruit.}}
{{History|||snap=alpha 1.0.0.1|The cooldown of chorus fruit now has an animation.}}
{{History|bedrock}}
{{History||1.7.0|snap=beta 1.7.0.2|The category that chorus fruit are apart of in the [[Creative inventory]] has been changed from "Nature" to "Items".}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Chorus Fruit JE2 BE2.png|32px]] The texture of chorus fruit has now been changed.}}
{{History||1.13.0|snap=beta 1.13.0.15|Chorus fruit has been moved back to the "Nature" section in the Creative inventory.}}

{{History|console}}
{{History||xbox=TU46|xbone=CU36|switch=1.0.1|ps=1.38|wiiu=Patch 15|[[File:Chorus Fruit JE1 BE1.png|32px]] Added chorus fruit.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Chorus Fruit JE2 BE2.png|32px]] The texture of chorus fruit has now been changed.}}

{{History|new 3ds}}
{{History||1.7.10|[[File:Chorus Fruit JE1 BE1.png|32px]] Added chorus fruit.}}
{{History|foot}}

==Issues==
{{issue list}}

==References==
{{reflist}}

==External Links==
*[https://www.minecraft.net/en-us/article/taking-inventory--chorus-fruit Taking Inventory: Chorus Fruit] – Minecraft.net on November 5, 2020

{{Items}}

[[Category:Plants]]
[[Category:Food]]
[[Category:Renewable resources]]

[[de:Chorusfrucht]]
[[es:Fruta chorus]]
[[fr:Chorus]]
[[ja:コーラスフルーツ]]
[[ko:후렴과]]
[[nl:Chorusfruit]]
[[pl:Owoc refrenusu]]
[[pt:Fruta do coro]]
[[ru:Плод коруса]]
[[uk:Фрукт хорусу]]
[[zh:紫颂果]]</li><li>[[Potato|Potato]]<br/>{{about|the raw potato|the cooked potato|Baked Potato|the potato that can inflict poison|Poisonous Potato}}
{{Item
| group = Age 0-1
| 1-1 = Potatoes Age 0-1.png
| 1-2 = Potatoes Age 0-1 BE.png
| group2 = Age 2-3
| 2-1 = Potatoes Age 4-6.png
| 2-2 = Potatoes Age 2-3 BE.png
| group3 = Age 4-6
| 3-1 = Potatoes Age 4-6.png
| 3-2 = Potatoes Age 4-6 BE.png
| group4 = Age 7
| 4-1 = Potatoes Age 7.png
| 4-2 = Potatoes Age 7 BE.png
| image = Potato JE3 BE2.png
| renewable = Yes
| heals = {{hunger|1}}
| stackable = Yes (64)
}}

A '''potato''' is a [[food]] [[item]] obtained from potato crops that can be used to plant them, consumed raw or [[cook]]ed to make [[baked potato]]es.

'''Potato crops''' are planted in [[farmland]] and used to grow potatoes and, rarely, [[Poisonous Potato|poisonous potatoes]].

== Obtaining ==

=== Natural generation ===
[[Village]] farm plots have a chance of being planted with potatoes. The exact chance depends on the style of the village:

{| class="wikitable"
! Village style !! Chance
|-
| {{EnvSprite|snowy-village}} Snowy || 70%
|-
| {{EnvSprite|plains-village}} Plains || 15%
|-
| {{EnvSprite|taiga-village}} Taiga || 10%
|}

Fully grown potato crops drop 2 to 5 potatoes ({{frac|3|5|7}} per crop harvested on average) and have a 2% chance of dropping an additional [[poisonous potato]]. Potato yield can be increased using a tool enchanted with [[Fortune]], with Fortune III harvesting an average of {{frac|5|3|7}} potatoes. [[Bone meal]] can be used to mature the potato to its last stage of growth.

The first two potatoes always drop, and then three more attempts are made to drop a potato with a success rate of 57.14286% to yield the extra 0–3 drops. Each level of Fortune enchantment increases the number of attempts by one.

=== Mob loot ===
[[Zombie]]s, [[husk]]s, and [[zombie villager]]s have a 2.5% ({{frac|1|40}}) chance of dropping either an [[iron ingot]], [[carrot]], or potato when killed by a player or tamed wolf. This is increased by 1% ({{frac|1|100}}) per level of looting. This gives potatoes the following chances of dropping:
* {{frac|1|120}} (about 0.83%)
* {{frac|7|600}} (about 1.17%) with Looting I
* {{frac|9|600}} (1.50%) with Looting II
* {{frac|11|600}} (about 1.83%) with Looting III
If a zombie, husk, or zombie villager is killed with fire, it drops a baked potato instead.

=== Chest loot ===
{{LootChestItem|potato}}

== Usage ==

=== Farming ===
{{main|Tutorials/Crop farming}}
When farmed, potatoes require 8 [[Block tick|stages]] to grow. However, there are four ''visible'' stages due to having only four distinct textures: every two stages have the same texture, except that growth stage 7 keeps the same appearance as stages 5–6, so that only stage 8 has the final, mature appearance. Planted potatoes require a light level of 9 or greater to continue growing. If the light level is 7 or below, the crops instantly un-plant themselves ("pop off"). It is not possible to plant potatoes if the light level is too low.

Crops grow faster if the farmland they are planted in is [[Farmland#Hydration|hydrated]]. Using [[bone meal]] on crops also increases the speed of growth by randomly increasing their growth stage by 2 to 5.

Crops break if pushed by a [[piston]] or if their supporting farmland breaks or turns to dirt (i.e. by being trampled), dropping their usual drops.

=== Food ===
To eat a potato, press and hold {{control|use}} while it is selected in the [[hotbar]]. Eating a potato restores {{hunger|1}} hunger and 0.6 [[Hunger#Mechanics|saturation]].

=== Breeding ===
[[Pig]]s follow and can be [[bred]] by a player holding a potato.

[[Villager]]s can pick up potato items to become willing, which allow them to breed. Villagers require 12 potatoes to become willing.

=== Smelting ingredient ===
{{Smelting
|showname=1
|Potato
|Baked Potato
|0.35
}}

=== Trading ===
Novice-level farmer villagers have a 25%{{only|bedrock}} or 40%{{only|java}} chance to buy 26 potatoes for an [[emerald]] as part of their trade.

=== Composting ===
Placing a potato into a [[composter]] has a 65% chance of raising the compost level by 1. This is less efficient than composting with [[Baked Potato|baked potatoes]], which has a higher success chance of 85%.

== Sounds ==
=== Block ===
{{Sound table/Block/Crop}}

=== Item ===
{{Sound table/Entity/Food}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showblocktags=y
|showforms=y
|generatetranslationkeys=y
|displayname=Potatoes
|spritetype=block
|nameid=potatoes
|blocktags=bee_growables, crops
|form=block}}
{{ID table
|displayname=Potato
|spritetype=item
|nameid=potato
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|generatetranslationkeys=y
|displayname=Potatoes
|spritetype=block
|nameid=potatoes
|id=142
|form=block}}
{{ID table
|displayname=Potato
|spritetype=item
|nameid=potato
|id=280
|form=item
|foot=1}}

=== Block states ===
{{see also|Block states}}
{{/BS}}

== Advancements ==
{{load advancements|Husbandry;A Balanced Diet}}

== History ==
{{History|java}}
{{History||1.4.2|snap=12w34a|[[File:Potato JE1 BE1.png|32px]] Added potatoes.
|[[File:Potatoes Age 0-1 JE1.png|32px]] [[File:Potatoes Age 2-3 JE1.png|32px]] [[File:Potatoes Age 4-6 JE1.png|32px]] [[File:Potatoes Age 7 JE1.png|32px]] Added potato crops.}}
{{History|||snap=12w36a|Potatoes can now be found in [[village]]s.}}
{{History||1.5|snap=13w09b|The [[Fortune]] enchantment now works when harvesting potatoes.<ref>{{bug|MC-1680}}</ref>}}
{{History||1.8|snap=14w02a|Potatoes can now be [[trading|sold]] to farmer [[villager]]s, at 15–19 potatoes for 1 [[emerald]].}}
{{History|||snap=14w04a|Farmer villagers now harvest fully grown potatoes.
|Villagers can now be made willing using 12 potatoes.}}
{{History|||snap=14w06a|[[File:Potatoes Age 0-1 JE2.png|32px]] [[File:Potatoes Age 2-3 JE2.png|32px]] [[File:Potatoes Age 4-6 JE2.png|32px]] [[File:Potatoes Age 7 JE2.png|32px]] Potato crops are now a pixel higher - previously they were offset one pixel down as to match farmland's sunken model. This is likely an accidental result of model conversion.}}
{{History|||snap=14w10a|[[File:Missing Model JE2.png|32px]] [[File:Missing Model JE2.png|32px]] [[File:Missing Model JE2.png|32px]] [[File:Missing Model JE2.png|32px]]<br>[[File:Missing Model (anisotropic filtering) JE2.png|32px]] [[File:Missing Model (anisotropic filtering) JE2.png|32px]] [[File:Missing Model (anisotropic filtering) JE2.png|32px]] [[File:Missing Model (anisotropic filtering) JE2.png|32px]]<br>Potato crops of all stages [[Missing model|no longer have a model]].}}
{{History|||snap=14w10b|[[File:Potatoes Age 0-1 JE4.png|32px]] [[File:Potatoes Age 2-3 JE4.png|32px]] [[File:Potatoes Age 4-6 JE4.png|32px]] [[File:Potatoes Age 7 JE4.png|32px]] Potato crops now have models again.<ref>{{bug|MC-50232}}</ref> In addition, they are now offset downwards by one pixel once more.<ref>{{bug|MC-50155}}</ref>}}
{{History|||snap=14w25a|[[File:Potatoes Age 0-1 JE5.png|32px]] [[File:Potatoes Age 2-3 JE5.png|32px]] [[File:Potatoes Age 4-6 JE5.png|32px]] [[File:Potatoes Age 7 JE5.png|32px]] Potato crops are now darker and subject to directional shading.}}
{{History|||snap=14w27a|[[File:Potatoes Age 0-1 JE6.png|32px]] [[File:Potatoes Age 2-3 JE6.png|32px]] [[File:Potatoes Age 4-6 JE6.png|32px]] [[File:Potatoes Age 7 JE6.png|32px]] Potato crops are no longer subject to directional shading.}}
{{History||1.9|snap=15w31a|Potatoes can now be used to lead and breed [[pig]]s.}}
{{History|||snap=15w38a|The [[drop]] chances of potatoes has now been slightly improved from average {{frac|2|3|5}} per potato crop harvested to {{frac|2|5|7}}.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this block's numeral ID was 142, and the item's 392.}}
{{History|||snap=18w11a|Potatoes now have a chance of generating in [[shipwreck]] [[chest]]s.}}
{{History||1.14|snap=18w43a|[[File:Potato JE2.png|32px]] The texture of potatoes has been changed.
|[[File:Potatoes Age 0-1 JE7.png|32px]] [[File:Potatoes Age 2-3 JE7.png|32px]] [[File:Potatoes Age 4-6 JE7.png|32px]] [[File:Potatoes Age 7 JE7.png|32px]] The textures of potato crops have been changed.}}
{{History|||snap=18w47a|Potatoes now generate in [[pillager outpost]] chests.}}
{{History|||snap=18w48a|Potatoes can now be found in chests in [[plains]] village houses.}}
{{History|||snap=18w49a|Potatoes can now be found in chests in [[snowy tundra|snowy]] village houses.}}
{{History|||snap=18w50a|Potatoes can now be found in chests in [[taiga]] village houses.
|[[File:Potato JE3 BE2.png|32px]] The texture of potatoes has been changed, once again.}}
{{History|||snap=19w03a|Added placement and new breaking [[sound]]s to potatoes.
|Placing a potato into the new [[composter]] has a 50% chance of raising the compost level by 1.}}
{{History|||snap=19w05a|Potatoes now have a 65% chance of increasing the compost level in a composter by 1.}}
{{History||1.15|snap=19w34a|[[Bee]]s can now pollinate potato crops.}}
{{History||1.17|snap=21w13a|[[File:Potatoes Age 0-1 JE8.png|32px]] [[File:Potatoes Age 2-3 JE8.png|32px]] [[File:Potatoes Age 4-6 JE8.png|32px]] [[File:Potatoes Age 7 JE8.png|32px]] The "crop" template model has changed such that pixels appear in the same physical positions on opposite sides of texture planes, changing the potato crop's appearance in the process.<ref>{{bug|MC-199242}}</ref>}}

{{History|pocket alpha}}
{{History||v0.8.0|snap=build 1|[[File:Potato JE1 BE1.png|32px]] Added potatoes.
|[[File:Potatoes Age 0-1 JE6 BE1.png|32px]] [[File:Potatoes Age 2-3 JE6 BE1.png|32px]] [[File:Potatoes Age 4-6 JE6 BE1.png|32px]] [[File:Potatoes Age 7 JE6 BE1.png|32px]]{{verify|Correct models?}} Added potato crops.
|Potatoes are a rare [[drops|drop]] from killing [[zombie]]s.}}
{{History|||snap=build 3|Potatoes now have a chance to drop when tilling [[grass block]]s.}}
{{History|||snap=build 4|Potatoes are no longer dropped from tilling grass blocks.}}
{{History||v0.9.0|snap=build 1|Potato crops now naturally spawn in [[village]]s.
|Potatoes can now be used to lead and breed [[pig]]s.}}
{{History||v0.12.1|snap=build 1|Potatoes now restore [[hunger]] instead of [[health]].
|Farmer (profession) [[villager]]s now plant and harvest potatoes.}}
{{History||v0.16.2|Potatoes can now be found in the [[chest]] inside large houses in [[ice plains]] and [[cold taiga]] [[village]]s.}}
{{History|bedrock}}
{{History||1.10.0|snap=beta 1.10.0.3|Potatoes can now be found in [[pillager outpost]]s and [[plains]] [[village]] houses.
|[[File:Potato JE3 BE2.png|32px]] The texture of potatoes has been changed.
|[[File:Potatoes Age 0-1 JE7.png|32px]] [[File:Potatoes Age 2-3 JE7.png|32px]] [[File:Potatoes Age 4-6 JE7.png|32px]] [[File:Potatoes Age 7 JE7.png|32px]]{{verify|Correct models?}} The textures of potato crops have been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Potatoes can now be used to fill up [[composter]]s.
|Potatoes can now be found in [[taiga]], [[snowy taiga]] and [[snowy tundra]] village house [[chest]]s.}}
{{History|||snap=beta 1.11.0.4|[[Trading]] has now been changed, farmer [[villager]]s now have a 25% chance to [[trading|buy]] 26 potatoes for an [[emerald]].}}
{{History||1.14.0|snap=beta 1.14.0.1|[[Bee]]s can now pollinate potato crops.}}
{{History||?|[[File:Potatoes Age 0-1 BE.png|32px]] [[File:Potatoes Age 2-3 BE.png|32px]] [[File:Potatoes Age 4-6 BE.png|32px]] [[File:Potatoes Age 7 BE.png|32px]] Potato crop planes use a mapping that results in very unnatural mirroring when viewed from certain angles, such as northwest.<ref>{{bug|MCPE-146936}}</ref>}}

{{History|console}}
{{History||xbox=TU14|xbone=CU1|ps=1.04|wiiu=Patch 1|switch=1.0.1|[[File:Potato JE1 BE1.png|32px]] Added potatoes.
|[[File:Potatoes Age 0-1 JE6 BE1.png|32px]] [[File:Potatoes Age 2-3 JE6 BE1.png|32px]] [[File:Potatoes Age 4-6 JE6 BE1.png|32px]] [[File:Potatoes Age 7 JE6 BE1.png|32px]]{{verify|Correct models?}} Added potato crops.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Potato JE3 BE2.png|32px]] The texture of potatoes has been changed.
|[[File:Potatoes Age 0-1 JE7.png|32px]] [[File:Potatoes Age 2-3 JE7.png|32px]] [[File:Potatoes Age 4-6 JE7.png|32px]] [[File:Potatoes Age 7 JE7.png|32px]]{{verify|Correct models?}} The textures of potato crops have been changed.}}

{{History|New 3DS}}
{{History||0.1.0|[[File:Potato JE1 BE1.png|32px]] Added potatoes.
|[[File:Potatoes Age 0-1 JE6 BE1.png|32px]] [[File:Potatoes Age 2-3 JE6 BE1.png|32px]] [[File:Potatoes Age 4-6 JE6 BE1.png|32px]] [[File:Potatoes Age 7 JE6 BE1.png|32px]]{{verify|Correct models?}} Added potato crops.}}
{{History|foot}}

=== Potatoes "item" ===
{{:Technical blocks/Potatoes}}

== Issues ==
{{issue list}}

== Gallery ==
<gallery>
AllSeeds.png|All the seeds that exist in the game (except [[Pitcher Plant|seeds fr]][[Torchflower Seeds|om 1.20,]] [[nether wart]] and [[cocoa beans]]).
VillageGrowingCarrotsAndPotatoes.png|[[Carrot]]s and potatoes found growing naturally in a [[village]].
File:Hot Potato.jpeg|Official render of a potato to celebrate National Potato Day.<ref> https://twitter.com/Minecraft/status/1692969488617029859?s=20| Hot potato! @ a friend to toss it.</ref>
</gallery>

== References ==
{{reflist}}

== External Links ==
*[https://www.minecraft.net/en-us/article/taking-inventory--potato Taking Inventory: Potato] – Minecraft.net on December 16, 2021

{{items}}
{{blocks|vegetation}}

[[Category:Plants]]
[[Category:Food]]
[[Category:Renewable resources]]
[[Category:Non-solid blocks]]
[[Category:Generated structure blocks]]

[[cs:Brambora]]
[[de:Kartoffel]]
[[es:Patata]]
[[fr:Pomme de terre]]
[[hu:Burgonya]]
[[it:Patata]]
[[ja:ジャガイモ]]
[[ko:감자]]
[[nl:Aardappel]]
[[pl:Ziemniak]]
[[pt:Batata]]
<br />
[[ru:Картофель]]
[[th:มันฝรั่ง]]
[[uk:Картопля]]
[[zh:马铃薯]]</li></ul>
13w36aAdded statistic-based objective criteria.
1.8
{{Extension DPL}}<ul><li>[[Melon Slice|Melon Slice]]<br/>{{Dungeons hatnote|type=consumable|Melon}}
{{Item
| title = Melon Slice
|typeimage=Melon Slice.png
| renewable = Yes
| heals = {{hunger|2}}
| stackable = Yes (64)
}}
A '''melon slice'''{{efn|Known as '''Melon Slice''' {{in|java}} and '''Melon''' {{in|bedrock}}.}} is a [[food]] item that can be eaten by the [[player]].

== Obtaining ==

=== Block loot ===

{{see also|Tutorials/Pumpkin and melon farming|title1 = Pumpkin and melon farming}}

Melon slices can be obtained by breaking (harvesting) [[melon]]s using any [[tool]] or by hand. [[Axe]]s, followed by [[sword]]s, are the fastest tools for harvesting melons.  A melon drops 3–7 melon slices, when broken; by hand, using a [[tool]], or after being broken by the movement of a [[piston]], with an average of 4.64 slices per melon.

Breaking a melon with a tool enchanted with [[Fortune]] increases the potential number of drops by 1 slice per level, up to a maximum of 9 slices.

== Usage ==

=== Food ===
{{see also|Tutorials/Hunger management|title1=Hunger management}}

To eat a melon slice, press and hold {{control|use}} while it is selected in the hotbar. Eating one restores {{hunger|2}} [[hunger]] and 1.2 hunger 
[[Hunger#Mechanics|saturation]].

=== Crafting ingredient ===

{{crafting usage}}

=== Composting ===
Placing a melon slice into a [[composter]] has a 50% chance of raising the compost level by 1.

==Sounds==
{{Sound table/Entity/Food}}

== Data values ==

=== ID ===

{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Melon Slice
|spritetype=item
|nameid=melon_slice
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|showaliasids=y
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|spritename=melon-slice
|displayname=Melon
|spritetype=item
|nameid=melon_slice
|aliasid=melon
|id=272
|form=item
|translationkey=item.melon.name
|foot=1}}

== Advancements ==
{{load advancements|Husbandry;A Balanced Diet}}

== History ==
{{History|java beta}}
{{History||1.8|snap=Pre-release|[[File:Melon Slice JE1 BE1.png|32px]] Added melons.}}
{{History|java}}
{{History||1.0.0|snap=Beta 1.9 Prerelease 4|Melons are now used in the [[crafting]] recipe of [[glistering melon]]s.}}
{{History|||snap=Beta 1.9 Prerelease 5|Melons once again drop the correct number of slices.}}
{{History||1.3.1|snap=12w21a|Melons can now be [[trading|bought]] from farmer [[villager]]s, at 5–8 melon slices for 1 [[emerald]].}}
{{History||1.7.2|snap=13w37a|Block ID 105, [[melon stem]], has been removed from the {{cmd|give}} [[commands|command]].}}
{{History||1.8|snap=14w02a|[[Villager]]s no longer [[trading|sell]] melons. They now buy [[melon]]s instead.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 360.}}
{{History|||snap=18w20b|"Melon" has been renamed to "Melon Slice."
|The ID of melon slices has been changed from <code>melon</code> to <code>melon_slice</code>.}}
{{History||1.14|snap=18w43a|[[File:Melon Slice JE2 BE2.png|32px]] The texture of melon slices has been changed.}}
{{History|||snap=19w03a|Placing a melon slice into the new [[composter]] has a 20% chance of raising the compost level by 1.}}
{{History|||snap=19w05a|Melon slices now have a 50% chance of increasing the compost level in a composter by 1.}}

{{History|pocket alpha}}
{{History||v0.5.0|[[File:Melon Slice JE1 BE1.png|32px]] Added melons. 
|Melons restore {{health|2}} each, rather than {{hunger|2}}.}}
{{History||v0.12.1|snap=?|Added Melon slice to the Creative inventory.}}
{{History|||snap=build 1|Melons now restores [[hunger]] instead of [[health]].
|Melons can no longer be obtained from [[nether reactor]]s.}}
{{History|pocket}}
{{History||1.1.0|snap=alpha 1.1.0.3|[[Breaking]] a [[melon]] with [[shears]] now always yields 9 melons.}}
{{History|bedrock}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Melon Slice JE2 BE2.png|32px]] The texture of melons has been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Melons can now be used to fill up [[composter]]s.}}
{{History|||snap=beta 1.11.0.4|Melons can now be [[trading|sold]] to farmer [[villager]]s.}}
{{History||1.16.0|snap=beta 1.16.0.57|[[Trading]] has been changed, melon slices can no longer be sold to farmer villagers.}}
{{History||1.16.100|snap=beta 1.16.100.56|The ID of melon slices has been changed from <code>melon</code> to <code>melon_slice</code>.}}

{{History|console}}
{{History||xbox=TU5|xbone=CU1|ps=1.0|wiiu=Patch 1|[[File:Melon Slice JE1 BE1.png|32px]] Added melons.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Melon Slice JE2 BE2.png|32px]] The texture of melons has been changed.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Melon Slice JE1 BE1.png|32px]] Added melons.}}
{{History|foot}}

== Issues ==
{{issue list}}

== See also ==
* [[Pumpkin]]
* [[Glistering Melon Slice]]

== Notes ==
{{fnlist}}

{{Items}}

[[Category:Plants]]

[[cs:Meloun]]
[[de:Melone]]
[[es:Rodaja de sandía]]
[[fr:Tranche de pastèque]]
[[hu:Dinnye Szelet]]
[[ko:수박]]
[[nl:Meloenschijf]]
[[pl:Arbuz]]
[[pt:Fatia de melancia]]
[[ru:Ломтик арбуза]]
[[zh:西瓜片]]
[[Category:Food]]
[[Category:Renewable resources]]</li><li>[[Honey Bottle|Honey Bottle]]<br/>{{Item
| title = Honey Bottle
| image = Honey Bottle.png
| renewable = Yes
| heals = {{hunger|6}}
|effects=Clears {{EffectLink|Poison}}
| stackable = Yes (16)
}}

A '''honey bottle''' is a [[drinks|consumable drink]] [[item]] obtainable by using a [[glass bottle]] on a full [[beehive]].  Honey bottles remove [[poison]] when drunk and can be used to craft [[Honey Block|honey blocks]] and [[sugar]].

== Obtaining ==
{{See also|Tutorials/Honey farming}}

=== Harvesting ===
A honey bottle can be obtained by using a [[glass bottle]] on either a [[beehive]] or [[beehive|bee nest]] with a honey level of 5. Doing this angers any [[bee]]s inside, causing them to attack the player, unless there is a [[campfire]] or another [[block]] on [[fire]] beneath the bee nest or beehive.

A [[dispenser]] with glass bottles can be used to collect the honey without angering the bees. The honey bottle appears as an item in the dispenser's inventory. If the dispenser is full, the honey bottle is shot out.

=== Crafting ===
{{Crafting
|Glass Bottle
|Glass Bottle
|Honey Block
|Glass Bottle 
|Glass Bottle
|Output=Honey Bottle, 4
|type= Foodstuff
}}

== Usage ==
To drink a honey bottle, press and hold {{control|use}} while it is selected in the [[hotbar]]. Drinking one restores {{hunger|6}} [[hunger]] and 1.2 hunger [[Hunger#Mechanics|saturation]]. Consuming the item also has the benefit of removing any [[poison]] effect applied to the player. Unlike drinking [[Milk Bucket|milk]], other applied effects are not removed upon drinking a honey bottle.

Honey bottles can be drunk even with a full hunger bar. Drinking a honey bottle takes 25% longer than eating other [[food]] - 2 seconds - and has a unique sound.

=== Crafting ingredient ===
{{Crafting usage}}

== Sounds ==
{{edition|java}}:
{{Sound table
|sound=Drink honey1.ogg
|sound2=Drink honey2.ogg
|sound3=Drink honey3.ogg
|sound4=Drink honey3.ogg
|subtitle=Gulping
|source=player
|description=While a player is drinking a honey bottle
|id=item.honey_bottle.drink
|translationkey=subtitles.item.honey_bottle.drink
|volume=0.5
|pitch=''varies'' <ref group=sound>0.9-1.0 for <code>drink_honey1</code> and <code>drink_honey2</code>, 0.315-0.35 for <code>drink_honey3</code>, and 0.675-0.75 for the second copy of <code>drink_honey3</code></ref>
|distance=16}}
{{Sound table
|sound=Bottle fill water1.ogg
|sound2=Bottle fill water2.ogg
|sound3=Bottle fill water3.ogg
|sound4=Bottle fill water4.ogg
|subtitle=Bottle fills
|source=block
|description=When a bottle is filled with honey
|id=item.bottle.fill
|translationkey = subtitles.item.bottle.fill
|volume=1.0
|pitch=1.0
|distance=16
|foot=1}}

{{edition|bedrock}}:
{{Sound table
|type=bedrock
|sound=Drink honey1.ogg
|sound2=Drink honey2.ogg
|sound3=Drink honey3.ogg
|sound4=Drink honey3.ogg<!--This is duplicated intentionally, see below-->
|source=player
|description=While a player is drinking a honey bottle
|id=random.drink_honey
|volume=''varies''<ref group="sound" name="bevarieshoney">0.5 for <code>drink_honey1</code> and <code>drink_honey2</code>, but <code>drink_honey3</code> is 0.175 or 0.375</ref>
|pitch=0.9-1.0}}
{{Sound table
|sound=Fill water bucket1.ogg
|sound2=Fill water bucket2.ogg
|sound3=Fill water bucket3.ogg
|source=block
|description=When a bottle is filled with honey<wbr><ref group=sound>{{Bug|MCPE-53881}}</ref>
|id=bucket.fill_water
|volume=1.0
|pitch=1.0
|foot=1}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Honey Bottle
|spritetype=item
|nameid=honey_bottle
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Honey Bottle
|spritetype=item
|nameid=honey_bottle
|id=592
|form=item
|foot=1}}

== Achievements ==

{{Load achievements|Bee Our Guest}}

== Advancements ==
{{Load advancements|Husbandry;A Balanced Diet;Bee Our Guest}}

== History ==
{{History|java}}
{{History||1.15|snap=19w34a|[[File:Honey Bottle JE1.png|32px]] Added honey bottles.}}
{{History|||snap=19w35a|Honey bottles now remove the [[Poison]] effect when consumed.
|Honey bottles are now included in the "A Balanced Diet" [[advancement]].}}
{{History|||snap=19w36a|Honey bottles are now less filling, restoring 1.2 [[Hunger#Mechanics|saturation]] instead of 9.6.}}
{{History||1.15|snap=19w41a|Honey bottles can now be used to craft [[honey block]]s.}}
{{History||1.15|snap=19w44a|Honey bottles can now be [[crafting|crafted]] with four [[glass bottle]]s and one [[honey block]].
|Honey bottles are now stackable (up to 16).}}
{{History|||snap=19w46a|Using [[glass bottle]]s to collect honey now unlocks the [[Bee Our Guest]] advancement.}}

{{History|bedrock}}
{{History||1.14.0|snap=beta 1.14.0.1|[[File:Honey Bottle BE1.png|32px]] Added honey bottles.}}
{{History|||snap=beta 1.14.0.4|[[File:Honey Bottle BE2.png|32px]] The texture of honey bottles has been changed to match {{el|je}}'s.
|Honey bottles can now be crafted with four [[glass bottle]]s and one [[honey block]].
|Honey bottles are now stackable to 16.}}
{{History|||snap=release|slink=Bedrock Edition 1.14.0|Using [[glass bottle]]s to collect honey now unlocks the [[Bee our guest]] achievement.}}
{{History|foot}}

== Issues ==
{{issue list}}

== Trivia ==

* Honey bottles are the only drinkable [[item]]s that can stack. They have a maximum stack size of 16.
* Honey bottles are the only drinkable items that can restore hunger.
* Honey bottles are 4 pixels more full than [[water bottles]].

{{Items}}

[[cs:Lahvička medu]]
[[de:Honigflasche]]
[[es:Frasco con miel]]
[[fr:Fiole de miel]]
[[ja:ハチミツ入りの瓶]]
[[ko:꿀이 든 병]]
[[lzh:蜜瓶]]
[[pl:Butelka miodu]]
[[pt:Frasco de mel]]
[[ru:Бутылочка мёда]]
[[th:ขวดน้ำผึ้ง]]
[[uk:Пляшечка меду]]
[[zh:蜂蜜瓶]]
[[Category:Food]]
[[Category:Renewable resources]]</li></ul>
14w02aEntities other than players can now be part of teams and have objective scores.
14w06aAdded the trigger and team kill-based objective criteria.
Added /scoreboard players enable.
"*" can be used in a player name argument to represent all players tracked by the scoreboard.
Added the "objective" argument to /scoreboard players reset.
Statistic objective criteria now use named IDs instead of numerical IDs.
Added the achievement.overpowered objective criterion.
14w07aAdded /scoreboard players operation and /scoreboard players test.
Scores for fake players that have a name beginning with "#" won't appear in the sidebar.
Added team-specific sidebar display slots.
Added the nametagVisibility team option.
14w10aAdded the deathMessageVisibility team option.
Added a dataTag argument to /scoreboard players set, /scoreboard players add, and /scoreboard players remove.
Added the stat.crouchOneCm, stat.sprintOneCm, and stat.timeSinceDeath objective criteria.
14w25aAdded =, <, and > to /scoreboard players operation.
14w29aPlayer/entity names in the sidebar are now secondarily sorted by alphabetical order.
14w30aAdded the stat.talkedToVillager and stat.tradedWithVillager objective criteria.
?Added >< to /scoreboard players operation.
1.8.2
{{Extension DPL}}<ul><li>[[Cooked Cod|Cooked Cod]]<br/>{{redirect|Cooked Fish|cooked salmon|Cooked Salmon}}
{{Item
| title = Cooked Cod
| image = Cooked Cod.png
| renewable = Yes
| heals = {{hunger|5}}
| stackable = Yes (64)
}}
'''Cooked cod''' is a food item obtained by cooking [[raw cod]].

== Obtaining ==

=== Mob loot ===
====Cod====
[[Cod]] always drops 1 [[Raw Cod|raw cod]] when killed, unaffected by Looting.<ref>{{bug|MC-212795||Salmon & Fish mobs are not affected by Looting}}</ref> If it is killed while on [[fire]], it drops 1 cooked cod instead.
====Dolphins ====
When killed, [[Dolphin|dolphins]] drop 0–1 raw cod. The maximum amount is increased by 1 per level of [[Looting]], for a maximum of 0-4 with Looting III. If killed while on fire, they drop cooked cod instead.
====Guardians and elder guardians====
[[Guardian]]s and [[elder guardian]]s have a 40% and 50% chance, respectively, to drop raw cod when killed. {{IN|java}}, cooked cod is dropped if a guardian is on fire when killed.

Guardians and elder guardians also drop a 2.5% chance to drop a random fish, with 60% of them being raw cod, which drops as cooked if the guardian was on fire. The chance of getting the fish drop is increased by 1% per level with [[Looting]] (for a maximum of 5.5% with Looting III), but the type of fish is not affected.
====Polar bears====
[[Polar bear]]s have a 75% chance of dropping 0–2 raw cod when killed. The maximum amount can be increased by 1 per level of Looting, for a maximum of 0-5 with Looting III. If killed while on fire, they drop cooked cod instead.
===Chest loot===
{{LootChestItem|cooked-cod}}

===Cooking===

Cooked cod can be obtained by cooking [[raw cod]] in a [[furnace]], [[smoker]], or [[campfire]]. 

{{smelting|Raw Cod|Cooked Cod|0,35}}

===Trading===

Novice-level Fisherman [[Villager|villagers]] have a 50% chance to sell 6 cooked cod for 6 raw cod and 1 [[emerald]].

== Usage ==

=== Food ===

To eat cooked cod, press and hold {{control|use}} while it is selected in the hotbar. Eating one restores {{hunger|5}} [[hunger]] and 6 hunger [[Hunger#Mechanics|saturation]].

=== Wolves ===

{{IN|Bedrock}}, cooked cod can be used to feed a wolf not at full health, healing by {{hp|5|mob=1}}. However, unlike other wolf food, cooked cod cannot be used to speed up the growth of baby wolves nor used to breed them.

==Sounds==
{{Sound table/Entity/Food}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showitemtags=y
|showforms=y
|generatetranslationkeys=y
|displayname=Cooked Cod
|spritetype=item
|nameid=cooked_cod
|itemtags=fishes
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|showaliasids=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Cooked Cod
|spritetype=item
|nameid=cooked_cod
|aliasid=cooked_fish
|id=268
|form=item
|translationkey=item.cooked_fish.name
|foot=1}}

== Achievements ==

{{load achievements|Delicious Fish}}

== Advancements ==
{{load advancements|Husbandry;A Balanced Diet}}

== Video ==
<div style="text-align:center">{{yt|nPl0HUGPMcA}}</div>

== History ==

{{History|java alpha}}
{{History||v1.2.0|snap=<nowiki>?|slink=:Category:Information needed requiring unarchived version|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish, which restores {{hp|5}}.}}
{{History|java beta}}
{{History||1.5|Cooking fish now gives the '''Delicious Fish''' [[achievement]].}}
{{History||1.8|snap=Pre-release|Cooked fish is now stackable to 64.
|Cooked fish now fills {{hunger|5}} instead of {{hp|5}}.}}
{{History|java}}
{{History||1.3.1|snap=12w21a|Farmer [[villager]]s now [[trading|buy]] 9–12 cooked fish for 1 [[emerald]].}}
{{History||1.8|snap=14w02a|[[Trading]] has been changed: fisherman [[villager]]s now [[trading|sell]] 6 cooked fish for 1 [[emerald]] plus 6 [[raw cod|raw fish]].
|Farmer villagers no longer buy cooked fish.}}
{{History|||snap=14w04a|The name of cooked fish has been corrected from <code>cooked_fished</code> to <code>cooked_fish</code>.}}
{{History|||snap=14w25a|Cooked fish are now obtainable rare [[drops]] from [[guardian]]s and [[elder guardians]].}}
{{History||1.13|snap=17w47a|The different data values for the <code>cooked_fish</code> IDs have been split up into their own IDs.
|"Cooked Fish" have been renamed to "Cooked Cod".
|Prior to [[1.13/Flattening|''The Flattening'']], these [[item]]s' numeral ID were 349 and 350.}}
{{History|||snap=18w08b|[[Cod]], and other [[fish]], have been added as [[mob]]s, which [[drops|drop]] their cooked [[item]] form when killed with [[fire]].
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked cod has been changed.}}
{{History|||snap=18w10a|Cooked cod now generates in [[buried treasure]] [[chest]]s.}}
{{History||1.14|snap=18w43a|[[File:Cooked Cod JE3.png|32px]] The texture of cooked cod has been changed.}}
{{History|||snap=18w47b|[[File:Cooked Cod JE4 BE3.png|32px]] The texture of cooked cod has been changed, once again to match {{el|be}}.}}

{{History|pocket alpha}}
{{History||v0.11.0|snap=build 1|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History||v0.12.1|snap=build 1|Cooked fish now restores [[hunger]] instead of [[health]].}}
{{History||v0.16.0|snap=build 1|Cooked fish is now [[drops|dropped]] by [[guardian]]s and [[elder guardian]]s.}}
{{History|pocket}}
{{History||1.0.4|snap=alpha 1.0.4.0|Fisherman [[villager]]s now [[trading|sell]] 6 cooked fish for 1 [[emerald]] plus 6 [[raw cod|raw fish]].}}
{{History|bedrock}}
{{History||1.4.0|snap=beta 1.2.14.2|[[Cod]] and other [[fish]] have been added as [[mob]]s, which [[drops|drop]] their cooked [[item]] form when killed with [[fire]].
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked fish has been changed.}}
{{History||1.5.0|snap=beta 1.5.0.4|[[File:Cooked Cod JE4 BE3.png|32px]] The texture of cooked fish has been changed.}}
{{History||1.7.0|snap=beta 1.7.0.2|"Cooked Fish" has been renamed to "Cooked Cod".}}
{{History||1.11.0|snap=beta 1.11.0.4|Fisherman [[villager]]s now have a 50% chance to [[trading|sell]] 6 cooked cod for 6 [[raw cod]] and 1 [[emerald]].}}
{{History||1.16.100|snap=beta 1.16.100.52|Cod now drop their cooked cod when killed with fire.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History||xbox=TU5|Cooked fish is now stackable to 64.
|Cooked fish now fills [[hunger]] instead of [[health]].}}
{{History||xbox=TU69|ps=1.76|wiiu=Patch 38|"Cooked Fish" has been renamed to "Cooked Cod".
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked cod has been changed.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History|foot}}

== Issues ==

{{Issue list}}

{{Items}}

[[Category:Food]]
[[Category:Renewable resources]]

[[de:Gebratener Kabeljau]]
[[es:Bacalao cocinado]]
[[ko:익힌 대구]]
[[pt:Bacalhau assado]]
[[ru:Жареная треска]]
[[th:Cod (ไอเทม)]]
[[zh:熟鳕鱼]]</li><li>[[Lapis Lazuli|Lapis Lazuli]]<br/>{{Item
| image = Lapis Lazuli.png
|type=
| renewable = Yes
| stackable = Yes (64)
}}
{{About|the item|the ore|Lapis Lazuli Ore|the mineral block|Lapis Lazuli Block}}

'''Lapis lazuli''' is a mineral required to [[Enchanting|enchant]] items in an [[Enchanting Table|enchanting table]].

== Obtaining ==

=== Mining ===

When mined with a stone [[pickaxe]] or better, [[lapis lazuli ore]] drops 4–9 lapis lazuli. With the [[Fortune]] III enchantment, a single block has a chance of dropping up to 36 items.

=== Crafting ===

{{Crafting
  |Block of Lapis Lazuli
  |Output=Lapis Lazuli,9
  |type=Material
}}

=== Smelting ===
{{Smelting
  |showname=1
  |Lapis Lazuli Ore; Deepslate Lapis Lazuli Ore
  |Lapis Lazuli
  |0.2
}}

=== Villager gifts ===

{{IN|java}}, cleric [[villager]]s give [[player]]s lapis lazuli if they have the [[Hero of the Village]] effect.

=== Trading ===

Apprentice-level cleric villagers sell one lapis lazuli for an [[emerald]] as part of their trades.

{{IN|bedrock}}, [[wandering trader]]s may sell 3 lapis lazuli for an emerald.

=== Chest loot ===
{{see also|Lapis Lazuli Ore#Natural generation}}
{{LootChestItem|lapis-lazuli}}

== Usage ==

=== Enchanting ===

1–3 pieces of lapis lazuli are required to use an [[Enchanting Table|enchanting table]] to enchant an [[items|item]]. More specifically, the enchanting table UI shows 3 options (see [[Enchanting mechanics]] for details): the first, second, and third options cost 1, 2, and 3 lapis lazuli, respectively.

=== Crafting ingredient ===

Lapis lazuli can be used to make [[blocks of lapis lazuli]] and [[blue dye]]. {{IN|bedrock}}, it can also be used directly as a substitute for blue dye.
{{crafting usage}}

{{IN|bedrock}}, lapis lazuli can be also used in banner patterns:
{{banner crafting usage}}

=== Loom ingredient === 
{{Banner loom usage|Lapis Lazuli}}

=== Dye ===
{{Dye usage}}

=== Smithing ingredient ===
{{Smithing
|head=1
|ingredients=Any Armor Trim +<br/>Any Armor Piece + <br/>Lapis Lazuli
|Any Armor Trim Smithing Template
|Netherite Chestplate
|Lapis Lazuli
|Lapis Trim Netherite Chestplate
|showdescription=1
|description = All armor types can be used in this recipe,<br/>a netherite chestplate is shown as an example.<br/>
|tail=1
}}

;Trim color palette
The following color palette is shown on the designs on trimmed armor:
*{{TrimPalette|lapis lazuli}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Lapis Lazuli
|spritetype=item
|nameid=lapis_lazuli
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|showaliasids=y
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Lapis Lazuli
|spritetype=item
|nameid=lapis_lazuli
|aliasid=dye / 4
|id=414
|form=item
|translationkey=item.dye.blue.name
|foot=1}}

== Advancements ==
{{load advancements|Enchanter}}

== History ==

{{History|java beta}}
{{History||1.2|[[File:Lapis Lazuli JE1 BE1.png|32px]] Added lapis lazuli.}}
{{History||1.2_02|[[Lapis lazuli ore]] can now be found at [[bedrock]] level and now drops 4–8 lapis lazuli per block mined (increased from 1) on [[singleplayer]] only. However, servers have not been affected yet.}}
{{History||1.8|snap=Pre-release|Lapis lazuli can now be found in [[mineshaft]] [[chest]]s.}}
{{History|java}}
{{History||1.4.2|snap=12w34a|Lapis lazuli can now be used to [[Armor#Dyeing|dye]] leather [[armor]] and [[wolf]] collars.}}
{{History||1.4.6|snap=12w49a|Lapis lazuli can now be [[crafting|crafted]] with [[gunpowder]] to create a [[firework star]].}} 
{{History||1.6.1|snap=13w19a|Lapis lazuli can now be used to craft blue [[stained clay]].}}
{{History||1.7.2|snap=13w41a|Lapis lazuli can now be used to craft blue [[stained glass]].}}
{{History||1.8|snap=14w02a|[[Enchanting]] now requires lapis lazuli. Different enchantments require different amounts of levels and different amounts of levels now require different amounts of lapis lazuli (between 1-3).
|Cleric [[villager]]s now [[trading|sell]] 1–2 lapis lazuli for 1 [[emerald]], making it a [[renewable resource]].}}
{{History|||snap=14w30a|Lapis lazuli can now be used to dye [[banner]]s.}}
{{History||1.9|snap=15w44a|The average yield of lapis lazuli in [[mineshaft]] [[chest]]s has been decreased.}}{{History||1.11|snap=16w39a|Added the ability to dye [[shulker box]]es.}}
{{History||1.12|snap=17w06a|Can now be used to craft blue [[concrete powder]].}}
{{History|||snap=17w15a|Added the ability to dye [[bed]]s.}}
{{History||1.13|snap=17w47a|The different data values for the <code>dye</code> ID have been split up into their own IDs.
|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 351.}}
{{History|||snap=18w11a|Lapis lazuli now generates in [[shipwreck]] [[chest]]s.}}
{{History||1.14|snap=18w43a|Lapis lazuli can now be used to craft [[blue dye]].
|Lapis lazuli can no longer be used as a [[dye]].
|All of the dye-related functions and crafting recipes of lapis lazuli (except lapis lazuli blocks) have been transferred to blue dye.
|[[File:Lapis Lazuli JE2 BE2.png|32px]] The texture of lapis lazuli has been changed.}}
{{History|||snap=18w50a|Lapis lazuli can now be found in chests in [[village]] temples.}}
{{History|||snap=19w13a|Cleric villagers now give lapis lazuli to players under the [[Hero of the Village]] effect.}}
{{History||1.17|snap=21w08a|Lapis lazuli can now drop and be smelted from [[deepslate lapis lazuli ore]].}}
{{History||1.20<br>(Experimental)|link=1.19.4|snap=23w04a|Lapis lazuli can now be used as an armor trim material.}}

{{History|pocket alpha}}
{{History||v0.3.0|[[File:Lapis Lazuli JE1 BE1.png|32px]] Added lapis lazuli.}}
{{History||v0.3.2|Lapis lazuli can now be crafted into lapis lazuli blocks, and vice versa.}}
{{History||v0.12.1|snap=build 1|Lapis lazuli is now required for [[enchanting]].}}
{{History||v0.14.0|snap=build 1|Lapis lazuli can now be found inside [[minecart with chest]]s in [[mineshaft]]s.
|Lapis lazuli can now be used to dye [[water]] in [[cauldron]]s.}}
{{History|pocket}}
{{History||1.0.4|snap=alpha 1.0.4.0|Cleric [[villager]]s now [[trading|sell]] 1–2 lapis lazuli for 1 [[emerald]].
|Lapis lazuli can now be used to [[dyeing|dye]] [[shulker shell]]s.}}
{{History||1.1.0|snap=alpha 1.1.0.0|Lapis lazuli can now be used to dye [[shulker box]]es and [[bed]]s.
|Lapis lazuli can now be used to [[crafting|craft]] blue [[concrete powder]].}}
{{History|bedrock}}
{{History||1.2.0|snap=beta 1.2.0.2|Lapis lazuli can now be used to dye [[banner]]s, [[firework star]]s and [[glass]].}}
{{History||1.4.0|snap=beta 1.2.14.2|Lapis lazuli can now be found in [[shipwreck]] treasure chests.}}
{{History|||snap=beta 1.2.20.1|Lapis lazuli can now be used to craft [[balloon]]s and [[glow stick]]s.}}
{{History||1.8.0|snap=beta 1.8.0.10|Lapis lazuli can now be used to craft [[blue dye]]s.}}
{{History||1.10.0|snap=beta 1.10.0.3|Lapis lazuli are now [[trading|sold]] by [[wandering trader]]s.
|[[File:Lapis Lazuli JE2 BE2.png|32px]] The texture of lapis lazuli has been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Lapis lazuli can now be found in [[desert]] [[village]] temple [[chest]]s.}}
{{History|||snap=beta 1.11.0.4|Cleric [[villager]]s now [[trading|sell]] one lapis lazuli for one [[emerald]].}}
{{History||1.16.100|snap=beta 1.16.100.56|The ID of lapis lazuli has been changed from <code>dye/4</code> to <code>lapis_lazuli</code>.}}
{{History||1.17.0|snap=beta 1.16.230.52|Lapis lazuli can now drop and be smelted from [[deepslate lapis lazuli ore]].}}
{{History||1.19.80|snap=beta 1.19.80.21|Lapis lazuli can now be used as an armor trim material.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Lapis Lazuli JE1 BE1.png|32px]] Added lapis lazuli.}}
{{History||xbox=TU31|xbone=CU19|ps=1.22|wiiu=Patch 3|switch=1.0.1|Lapis lazuli can now be used in [[enchanting]].}}
{{History|Ps4}}
{{History||1.90|[[File:Lapis Lazuli JE2 BE2.png|32px]] The texture of lapis lazuli has been changed.}}
{{History|foot}}

== Issues ==

{{issue list}}

== Trivia ==
* In real life, lapis lazuli is a blue gem that can be ground and processed into ultramarine pigment. Lapis lazuli pigment has been famously used in the production of illuminated manuscripts, stained glass, and cave paintings. [[Wikipedia:Lapis lazuli|See the Wikipedia article for more information]].
* Lapis lazuli is the only [[ore]] that can be used as a [[dye]]{{only|BE|short=1}} or making a dye.
* It is the only item that can be put in the second slot of an [[enchantment table]].

== References ==
{{reflist}}

{{Items}}

[[Category:Dyes]]

[[cs:Lazurit]]
[[de:Lapislazuli]]
[[es:Lapislázuli]]
[[fr:Lapis-lazuli]]
[[hu:Lazurit]]
[[ja:ラピスラズリ]]
[[ko:청금석]]
[[nl:Lapis lazuli]]
[[pl:Lazuryt]]
[[pt:Lápis-lazúli]]
[[ru:Лазурит]]
[[th:แร่แลพิสแลซูลี]]
[[uk:Лазурит]]
[[zh:青金石]]
[[Category:Renewable resources]]</li></ul></nowiki>
Added the 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.
1.9
{{Extension DPL}}<ul><li>[[Glowstone Dust|Glowstone Dust]]<br/>{{Item
| image = Glowstone Dust.png
|type=
| renewable = Yes
| stackable = Yes (64)
}}
'''Glowstone dust''' is an [[item]] obtained from mining [[glowstone]], and is mainly used to create [[potion]]s with increased strength and decreased duration.

== Obtaining ==
=== Mining ===
When broken using anything other than a [[Silk Touch]]-enchanted [[tool]], a [[glowstone]] block drops 2-4 glowstone dust. A [[Fortune]] enchantment increases the chances of higher drops, with Fortune III allowing an average yield of 3.5 glowstone dust per block.

=== Mob loot ===
[[Witch]]es have a chance of dropping 0–6 glowstone dust upon death. This is increased by 3 per level of [[Looting]], for a maximum of 0-15 glowstone dust. <!-- Do not add the blaze as it is in violation of MCW:UPTODATE due to the Legacy Console Edition being discontinued. Any edit that adds the blaze to this section will be immediately reverted. -->

=== Trading ===

{{IN|bedrock}}, journeyman-level cleric [[villager]]s sell one glowstone dust for 4 [[emerald]]s as part of their trades.

== Usage ==
=== Crafting ingredient ===
{{crafting usage}}

=== Brewing ingredient ===
{{brewing
|showname=1
|head=1
|Glowstone Dust
|Thick Potion
|base=Water Bottle
}}
{{brewing
  |name=Increased Potency
  |showbase=1
  |Glowstone Dust
  |base=[Potion of Healing II]Potion of Healing;[Potion of Regeneration II]Potion of Regeneration;[Potion of Strength II]Potion of Strength;[Potion of Swiftness II]Potion of Swiftness;[Potion of Harming II]Potion of Harming;[Potion of Poison II]Potion of Poison;[Potion of Leaping II]Potion of Leaping
  |foot=1
}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Glowstone Dust
|spritetype=item
|nameid=glowstone_dust
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Glowstone Dust
|spritetype=item
|nameid=glowstone_dust
|id=394
|form=item
|foot=1}}

== History ==
{{History|java alpha}}
{{History||v1.2.0|snap=preview|[[File:Glowstone Dust JE1 BE1.png|32px]] Added glowstone dust.
|Glowstone dust currently uses nine dust to [[crafting|craft]] 1 [[glowstone]] block.
|Also, each glowstone block drops only one glowstone dust.}}
{{History|java beta}}
{{History||1.6.6|The crafting recipe for glowstone blocks has been changed from 9 glowstone dust to 4.
|Each glowstone block now drops 2-4 glowstone dust when broken.}}
{{History|java}}
{{History||1.0.0|snap=Beta 1.9 Prerelease 3|Glowstone dust can now be [[brewing|brewed]] in a [[water bottle]] to create a [[thick potion]].
|Glowstone dust now strengthens the [[potion]]s of [[Swiftness]], [[Healing]], [[Harming]], [[Poison]], [[Regeneration]] and [[Strength]].}}
{{History|||snap=Beta 1.9 Prerelease 4|Glowstone dust now strengthens the new potion of [[Regeneration]].}}
{{History||1.3.1|snap=12w21a|Glowstone dust has become a renewable resource, as priest [[villager]]s now sell glowstone blocks.}}
{{History||1.4.2|snap=12w38b|[[Witch]]es now have a chance of [[drops|dropping]] glowstone dust.}}
{{History||1.4.6|snap=12w49a|Glowstone dust can now be used to [[crafting|craft]] a [[firework star]] with a twinkle effect.}}
{{History||1.8|snap=14w27a|Glowstone dust now strengthens the new [[potion of Leaping]].}}
{{History||1.9|snap=15w31a|Glowstone dust is now used to craft [[spectral arrow]]s.
|Glowstone dust can no longer be added to extended [[potion]]s.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 348.}}
{{History|||snap=18w07a|Glowstone dust now strengthens the new [[potion of the Turtle Master]].}}
{{History||1.14|snap=18w43a|[[File:Glowstone Dust JE2 BE2.png|32px]] The texture of glowstone dust has been changed.}}
{{History||1.16|snap=20w07a|Glowstone dust has a {{frac|2|109}} (~1.83%) chance of being offered by [[piglin]]s when [[bartering]], in a stack size of 2–4.}}
{{History|||snap=20w09a|Glowstone dust now has a {{frac|10|226}} (~4.42%) chance of being offered by piglins when bartering, in a stack size of 1–5.}}
{{History||1.16.2|snap=20w28a|Glowstone dust can no longer be obtained from bartering with piglins.}}

{{History|pocket alpha}}
{{History||v0.2.0|[[File:Glowstone Dust JE1 BE1.png|32px]] Added glowstone dust. It is currently unobtainable and serves no purpose.}}
{{History||v0.5.0|Glowstone dust is now obtainable through the [[nether reactor]].
|Glowstone dust can be used to craft [[glowstone]] blocks.}}
{{History||v0.12.1|snap=build 1|Glowstone dust can now be obtained through [[the Nether]] instead of the nether reactor.
|Glowstone dust is now available in the [[creative]] [[inventory]].|Glowstone dust can now be used to [[brewing|brew]] thick [[potion]]s and to strengthen potions.}}
{{History||v0.14.0|snap=build 1|Added [[witch]]es, which have a chance of [[drops|dropping]] glowstone dust upon [[death]].}}
{{History|bedrock}}
{{History||1.2.0|snap=beta 1.2.0.2|Glowstone dust can now be used to [[crafting|craft]] a [[firework star]] with a twinkle effect.}} 
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Glowstone Dust JE2 BE2.png|32px]] The texture of glowstone dust has been changed.}}
{{History||1.11.0|snap=beta 1.11.0.4|Glowstone dust can now be [[trading|bought]] from cleric [[villager]]s.}}
{{History||1.16.0|snap=beta 1.16.0.57|Glowstone dust can now be obtained from [[bartering]] with [[piglin]]s.}}
{{History||1.16.100|snap=beta 1.16.100.54|Glowstone dust can no longer be obtained from [[barter]]ing with [[piglin]]s.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Glowstone Dust JE1 BE1.png|32px]] Added glowstone dust.}}
{{History||xbox=TU8|0–2 glowstone dust is now [[drops|dropped]] when a [[blaze]] is killed.}}
{{History|Ps4}}
{{History||1.90|[[File:Glowstone Dust JE2 BE2.png|32px]] The texture of glowstone dust has been changed.}}

{{History|New 3DS}}
{{History||0.1.0|[[File:Glowstone Dust JE1 BE1.png|32px]] Added glowstone dust.}}
{{History|foot}}

== Issues ==
{{issue list}}

{{Items}}

[[Category:Renewable resources]]
[[Category:Brewing recipe]]

[[de:Glowstonestaub]]
[[es:Polvo de piedra luminosa]]
[[fr:Poudre lumineuse]]
[[hu:Izzókő-por]]
[[ja:グロウストーンダスト]]
[[ko:발광석 가루]]
[[nl:Gloeisteenstof]]
[[pl:Jasnopył]]
[[pt:Pó de pedra luminosa]]
[[ru:Светокаменная пыль]]
[[tr:Işık Taşı Tozu]]
[[uk:Пил світлокаменю]]
[[zh:荧石粉]]</li><li>[[Nether Quartz|Nether Quartz]]<br/>{{About|the item|the ore|Nether Quartz Ore|the mineral block|Block of Quartz|other uses|Quartz}}
{{Item
| image = Nether Quartz.png
|type=
| renewable = Yes
| stackable = Yes (64)
}}

'''Nether quartz''' is a white mineral found in [[the Nether]].

== Obtaining ==
{{see also|Nether Quartz Ore#Natural generation}}

=== Mining ===

[[Nether quartz ore]] mined using a [[pickaxe]] drops one unit of Nether quartz. If the pickaxe is enchanted with [[Fortune]], it may drop an extra unit per level of Fortune, up to a maximum of four with Fortune III. If the pickaxe is enchanted with [[Silk Touch]], the ore drops itself.

=== Chest loot ===
{{LootChestItem|nether-quartz}}

=== Smelting ===
{{Smelting
|Nether Quartz Ore
|Nether Quartz
|0,2
}}

=== Bartering ===

[[Piglin]]s may [[barter]] 5–12 nether quartz when given a [[gold ingot]].

== Usage ==

=== Crafting ingredient ===
{{crafting usage}}

=== Trading ===

Expert-level stone mason [[villagers]] have a {{frac|1|33}} chance to trade one [[emerald]] for 12 Nether quartz {{in|java}}. This trade is always offered {{in|bedrock}}.

=== Smithing ingredient ===
{{Smithing
|head=1
|ingredients=Any Armor Trim +<br/>Any Armor Piece + <br/>Nether Quartz
|Any Armor Trim Smithing Template
|Netherite Chestplate
|Nether Quartz
|Quartz Trim Netherite Chestplate
|showdescription=1
|description = All armor types can be used in this recipe,<br/>a netherite chestplate is shown as an example.<br/>
|tail=1
}}

;Trim color palette
The following color palette is shown on the designs on trimmed armor:
*{{TrimPalette|nether quartz}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Nether Quartz
|spritetype=item
|nameid=quartz
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Nether Quartz
|spritetype=item
|nameid=quartz
|id=524
|form=item
|foot=1}}

== History ==

{{History|java}}
{{History||1.5|snap=13w01a|[[File:Nether Quartz JE1 BE1.png|32px]] Added Nether quartz. 
|Nether quartz is used to craft [[daylight sensor]]s and [[redstone comparator]]s.}}
{{History|||snap=January 4, 2013|slink=http://twitter.com/jeb_/status/287481098760499201|[[Jeb]] tweeted that Nether quartz would be used for more decorative uses as well.}}
{{History|||snap=January 7, 2013|slink=http://twitter.com/jeb_/status/288311932304371712|Jeb tweeted a picture of some [[block of quartz]] tests potentially being replacements for the lack of limestone/marble in the game.}}
{{History|||snap=13w02a|Added [[block of quartz]], which is [[crafting|crafted]] with Nether quartz.}}
{{History||1.8|snap=14w02a|Nether quartz can now be used to craft [[granite]] and [[diorite]].}}
{{History||1.11|snap=16w39a|Nether quartz is now used to craft [[observer]]s.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeric ID was 406.}}
{{History||1.14|snap=18w43a|[[File:Nether Quartz JE2 BE2.png|32px]] The texture of Nether quartz has now been changed.}}
{{History|||snap=19w11a|Nether quartz is now [[trading|bought]] by [[villager]]s of the new mason profession.}}
{{History||1.16|snap=20w07a|Nether quartz now has a {{frac|1|109}} (~0.92%) chance of being offered by [[piglin]]s when [[bartering]], in a stack size of 1–4, making it [[renewable resource|renewable]].}}
{{History|||snap=20w09a|Nether quartz now has a {{frac|10|226}} (~4.42%) chance of being offered by piglins when bartering, in a stack size of 1–5.}}
{{History|||snap=20w10a|Nether quartz now has a {{frac|20|411}} (~4.87%) chance of being offered by piglins when bartering, in a stack size of 8-16.}}
{{History|||snap=20w11a|Nether quartz now has a {{frac|20|417}} (~4.80%) chance of being offered by piglins when bartering.}}
{{History|||snap=20w13a|Nether quartz now has a {{frac|20|424}} (~4.72%) chance of being offered by piglins when bartering.}}
{{History|||snap=20w16a|Nether quartz can now be found in [[bastion remnant]] chests.}}
{{History|||snap=20w20a|Nether quartz now has a {{frac|20|423}} (~4.73%) chance of being offered by piglins when bartering.}}
{{History||1.16.2|snap=20w28a|Nether quartz now has a {{frac|20|459}} (~4.36%) chance of being offered by piglins when bartering, in a stack size of 5-12.}}
{{History||1.20<br>(Experimental)|link=1.19.4|snap=23w04a|Nether quartz can now be used as an armor trim material.}}

{{History|pocket alpha}}
{{History||v0.6.0|[[File:Nether Quartz JE1 BE1.png|32px]] Added Nether quartz.}}
{{History||v0.12.1|snap=build 1|Nether quartz is no longer available from the [[Nether reactor]] and is now available from [[the Nether]].}}
{{History||v0.13.0|snap=build 1|Nether quartz is now used to craft [[daylight sensor]]s.}}
{{History||v0.14.0|snap=build 1|Nether quartz can now be used to craft [[redstone comparator]]s.}}
{{History||v0.15.0|snap=build 1|Nether quartz is now used to craft [[observer]]s.}}
{{History|bedrock}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Nether Quartz JE2 BE2.png|32px]] The texture of Nether quartz has now been changed.
|Between 20 and 26 nether quartz can now be [[trading|sold]] to stone mason [[villager]]s.}}
{{History||1.11.0|snap=beta 1.11.0.4|[[Trading]] has now been changed, 12 Nether quartz can now be sold to stone mason villagers.}}
{{History||1.16.0|snap=beta 1.16.0.57|Nether Quartz can now be obtained from bartering with piglin.}}
{{History||1.19.80|snap=beta 1.19.80.21|Nether quartz can now be used as an armor trim material.}}

{{History|console}}
{{History||xbox=TU14|xbone=CU1|ps=1.04|wiiu=Patch 1|switch=1.0.1|[[File:Nether Quartz JE1 BE1.png|32px]] Added Nether quartz.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Nether Quartz JE2 BE2.png|32px]] The texture of Nether quartz has now been changed.}}

{{History|New 3DS}}
{{History||0.1.0|[[File:Nether Quartz JE1 BE1.png|32px]] Added Nether quartz.}}
{{History|foot}}

== Issues ==

{{issue list}}

== Trivia ==

* All of the sensor related items that are craftable (comparator, daylight sensor, observer) are crafted with some Nether quartz involved.

== References ==

{{reflist}}

{{items}}

[[Category:Renewable resources]]

[[cs:Netheritový křemen]]
[[de:Netherquarz]]
[[es:Cuarzo del Nether]]
[[fr:Quartz du Nether]]
[[hu:Alvilági kvarc]]
[[ja:ネザークォーツ]]
[[ko:네더 석영]]
[[nl:Netherkwarts]]
[[pl:Kwarc]]
[[pt:Quartzo do Nether]]
[[ru:Кварц Нижнего мира]]
[[uk:Пекельний кварц]]
[[zh:下界石英]]</li></ul>
15w32aAdded the stat.sneakTime objective criteria.
15w32bAdded /scoreboard players tag.
Added the xp, food, and air objective types.
15w33aAdded the stat.pickup and stat.drop objective criteria.
Added the armor, level objective types.
15w36aAdded collisionRule.
15w49aAdded the stat.aviateOneCm objective criteria.

Issues

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

References

Advertisement