Minecraft Wiki
Advertisement

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

Objectives

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

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

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

An objective's criteria determines its behavior:

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

Some criteria use the Statistics and Achievements 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
achievement Accepted sub-criteria are: "acquireIron", "bakeCake", "blazeRod", "bookcase", "breedCow", "buildBetterPickaxe", "buildFurnace", "buildHoe", "buildPickaxe", "buildSword", "buildWorkBench", "cookFish", "diamonds", "diamondsToYou", "enchantments", "exploreAllBiomes", "flyPig", "fullBeacon", "ghast", "killCow", "killEnemy", "killWither", "makeBread", "mineWood", "onARail", "openInventory", "overkill", "overpowered", "portal", "potion", "snipeSkeleton", "spawnWither", "theEnd", and "theEnd2". Value is dependent on how many times the player has gotten the achievement (e.g. if a player has picked up three blocks of wood, their score for an objective with the "achievement.mineWood" criterion will be 3). Yes 34
stat Base for criteria related to a player's statistics. Accepted sub-criteria are: "animalsBred", "boatOneCm", "climbOneCm", "crouchOneCm", "damageDealt", "damageTaken", "deaths", "diveOneCm", "drop", "fallOneCm", "fishCaught", "flyOneCm", "horseOneCm", "jump", "junkFished", "leaveGame", "minecartOneCm", "mobKills", "pigOneCm", "playerKills", "playOneMinute", "sprintOneCm", "swimOneCm", "talkedToVillager", "timeSinceDeath", "tradedWithVillager", "treasureFished", and "walkOneCm". Score increments automatically for a player when they perform the action specified by the sub-criterion. Yes 28
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 50 (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 135 (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", "Rabbit", "Sheep", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf", and "Zombie". Increments when a player has killed the specified mob. Yes 24
stat.entityKilledBy The sub-criteria are the name of an entity. Valid names are: "Bat", "Blaze", "CaveSpider", "Chicken", "Cow", "Creeper", "Enderman", "Endermite", "EntityHorse", "Ghast", "Guardian", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "Rabbit", "Sheep", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf", and "Zombie". Increments when a player has been killed by the specified mob.

Note that if the name of a passive mob is used the value will never increase, as those mobs are not capable of hurting the player.

Yes 24
teamkill The sub-criteria are the color of a team. Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Increments when a player has killed a member of a team with the specified color. Yes 16
killedByTeam The sub-criteria are the color of a team. Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Increments when a player has been killed by a member of a team with the specified color. Yes 16
  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.

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

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

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

Display slots

Via the "scoreboard objectives setdisplay" command (see command reference), players' scores in specific objectives can be displayed in certain 'slots' in-game. Each 'Display Slot' can show one objective at a time, and multiple 'Display Slots' may be used for the same or different objectives.

Slot Description
list Displays a yellow number without a heading on the tab menu, where online players are shown. Visible even in singleplayer.
sidebar Shows on the right hand side of the screen. Shows players in a high score list with a heading labeled the objective's display name. Note that 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.

Teams

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

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

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

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

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

Command blocks can be used to check whether a player is on a team with the "team" argument; the "!" character may be placed before a name to check for players not on the team. For example, "testfor @p[team=red]" in a Command Block will provide comparator output if a player is on the "red" team. Similarly, "testfor @p[team=!red]" 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

Command Description Success Conditions[note 1]
scoreboard <objectives|players|teams> The base command of the scoreboard system. N/A
scoreboard objectives list Lists all existing objectives, with their display name and criteria. The scoreboard must have at least one objective.
scoreboard objectives add <name> <criteria> [display name...] Creates a new objective with the internal name name, specified criteria, and the optional display name. Without a specified display name, it will default to name. See above section for the meaning of these properties. All arguments are case-sensitive. name must not be used by an existing objective, and must be at most 16 characters. criteria must be a valid criteria type. display name must be at most 32 characters.
scoreboard objectives remove <name> Deletes all references to the objective with name in the scoreboard system. Data is deleted from the objectives list, player scores, and if it was on a display list, it will no longer be displayed. name must be an existing objective.
scoreboard objectives setdisplay <slot> [objective] 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.
scoreboard players list [playername] Displays all players who are tracked, in some way, by the scoreboard system. The optional playername parameter can be used to display all scores of a particular player, and "*" (an asterisk) in place of playername will display all scores for all players tracked by the scoreboard system. playername must have recorded scores, if specified. If no playername is specified, there must be at least one tracked player on the scoreboard.
scoreboard players set <player> <objective> <score> [dataTag] Sets the player's score in objective to score, overwriting the previous score if it exists. "*" may be used in place of player to represent every player tracked by the scoreboard. objective must exist and cannot be read-only, and score must be between -2,147,483,648 and 2,147,483,647, inclusive. Note that player does not need to be online or even exist. If player exists and a dataTag is specified, player must match dataTag. Note that dataTag must define the type of tag such as {powered:1b} if looking for powered creepers.
scoreboard players add <player> <objective> <count> [dataTag] Increments the player's score in objective by count. "*" may be used to represent all players tracked by the scoreboard. objective must exist and cannot be read-only, and count must be between 1 and 2,147,483,647, inclusive. Note that player does not need to be online or even exist. If player exists and a dataTag is specified, player must match dataTag. Note that dataTag must define the type of tag such as {powered:1b} if looking for powered creepers.
scoreboard players remove <player> <objective> <count> [dataTag] Decrements the player's score in objective by count. "*" may be used to represent all players tracked by the scoreboard.
scoreboard players reset <player> [objective] Deletes score or all scores for player. If objective is specified, only that objective is cleared; otherwise this applies to all objectives. Note this does not merely set the score(s) to 0: it removes the player from the scoreboard altogether (or for the given objective). "*" may be used to represent all players tracked by the scoreboard. Always succeeds, even on players who are not on the scoreboard.
scoreboard players enable <player> <trigger> Enables player to use the /trigger command on the specified trigger objective. Until this has been done, player's attempts to /trigger that objective will fail. Once they have used the /trigger command on it, it will be disabled again. "*" may be used to represent all players tracked by the scoreboard. trigger must be an objective of the criteria "trigger".
scoreboard players test <player> <objective> <min> [max] Outputs whether or not player's score in objective is within the range min to max (inclusive). If not specified 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 players tracked by the scoreboard. objective must exist, and player's score in it must exist and be at least min and no greater than max. Note that player does not need to be online or even exist.
scoreboard players operation <targetName> <targetObjective> <operation> <selector> <objective> Applies an arithmetic operation altering targetName's score in targetObjective, using selector's score in objective as input.

<operation> may be:

  • "+=" Addition: add selector's score to targetName's
  • "-=" Subtraction: subtract selector's score from targetName's
  • "*=" Multiplication: set targetName's score to the product of targetName and selector's scores
  • "/=" Integer Division: set targetName's score to itself divided by selector's score
  • "%=" 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 players tracked by the scoreboard.

objective and targetObjective must exist, targetObjective cannot be read-only, and all requested targets/selectors must have scores in the specified objectives (if some do and some do not, the operation will succeed only for the combinations where both the target and the selector have a score). Note that player does not need to be online or even exist.
scoreboard teams list [teamname] Lists all teams, with their display names and the amount of players in them. The optional teamname parameter can be used to display all players on a particular team. If teamname is specified, it must exist and must have players. If no teamname is specified, there must be at least one registered team on the scoreboard.
scoreboard teams add <name> [display name...] Creates a team with the given name and optional display name. name must not be used by an existing team, and must be at most 16 characters. display name must be at most 32 characters.
scoreboard teams remove <name> Deletes the named team from the scoreboard system. name must be an existing team.
scoreboard teams empty <name> Removes all players from the named team. name must be an existing team, and the team must have at least one player.
scoreboard teams join <team> [players...] Assigns the specified players to the specified team. If no player is specified, the player running the command joins the team. "*" may be used to represent all players tracked by the scoreboard. team must exist. Note that the named players do not need to be online or even exist, and can even already be on the team.
scoreboard teams leave [players...]
scoreboard teams leave <team> [players...]
Makes the specified players leave their teams. If no player is specified, the player running the command leaves their team. "*" may be used to represent all players tracked by the scoreboard. Each player must be on a team - it is possible to get a partial success and partial failure, but a command block will report only the failure.
scoreboard teams option <team> color <value> Will color the name of all players on this team in chat, above their head, on the Tab menu, and on the sidebar. Valid color values are "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Another valid value is "reset" (names show in default color and formatting). team must exist, and value must be a valid value.
scoreboard teams option <team> friendlyfire <true|false> The default setting, true, has no impact on PvP mechanics. When set to false, players on this team cannot harm each other with melee, bow, or Splash Potion of Harming attacks, but may still inflict negative status effects on each other. team must exist, and the setting must be "true" or "false".
scoreboard teams option <team> seeFriendlyInvisibles <true|false> When set to true, players on this team will see invisible teammates (and themselves) as semi-transparent instead of completely invisible. team must exist, and the setting must be "true" or "false".
scoreboard teams option <team> nametagVisibility <never|hideForOtherTeams|hideForOwnTeam|always> Controls the visibility of nametags for players on the given team, and defaults to "always". When set to "never", no nametags will show above any player on the given team. When set to "hideForOtherTeams", the nametags of players on the given team will be hidden to other players not on the team. When set to "hideForOwnTeam", only nametags of other players on one's own team will be hidden. When set to "always", all nametags will be visible. team must exist, and the setting must be "never", "hideForOtherTeams", "hideForOwnTeam", or "always".
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".
  1. 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.

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.
          •  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

r
1.5
{{Extension DPL}}<ul><li>[[Yellow Dye|Yellow Dye]]<br/>{{Item
| title = Yellow Dye
| renewable = Yes
| stackable = Yes (64)
}}
'''Yellow dye''' is a [[Dye#Primary|primary dye]] created by placing a [[dandelion]] or [[sunflower]] into a [[crafting]] grid.

== Obtaining ==

=== Crafting ===
{{Crafting
  |Dandelion;Sunflower
  |Output=Yellow Dye;Yellow Dye,2
  |type=Material
}}

=== Chest loot ===
{{LootChestItem|yellow-dye}}

=== Trading ===

[[Wandering trader]]s sell 3 yellow dye for an [[emerald]].

== Usage ==
{{dye usage}}

=== Crafting ingredient ===
{{crafting usage|ignore=Banner|continue=1}}
{{banner crafting usage}}

=== Loom ingredient ===
{{Banner loom usage|Yellow Dye}}

=== Trading ===
Expert-level shepherd villagers have a {{frac|1|6}} chance to buy 12 yellow dye for an emerald.

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Yellow Dye
|spritetype=item
|nameid=yellow_dye
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|showaliasids=y
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Yellow Dye
|spritetype=item
|nameid=yellow_dye
|aliasid=dye / 11
|id=406
|form=item
|translationkey=item.dye.yellow.name
|foot=1}}

== Video ==
{{yt|nOQUDjEHGRg}}

== History ==
{{History|java beta}}
{{History||1.2|[[File:Yellow Dye JE1 BE1.png|32px]] Added dandelion yellow.}}
{{History||1.6.6|Dandelions can now be generated using [[Bone Meal|bone meal]], making dandelion yellow [[renewable resource|renewable]].}}
{{History|java}}
{{History||1.4.2|snap=12w34a|Added the ability to [[Armor#Dyeing|dye]] leather [[armor]] and [[wolf]] collars.}}
{{History||1.4.6|snap=12w49a|Dandelion yellow can be crafted with [[gunpowder]] to create a [[firework star]].}} 
{{History||1.6.1|snap=13w19a|[[Stained clay]] can now be crafted.}}
{{History||1.7.2|snap=13w36a|Can now be crafted using sunflower.}}
{{History|||snap=13w37a|Each dandelion now yields only 1 dandelion yellow, instead of 2.}}
{{History|||snap=13w41a|[[Stained glass]] can now be [[crafting|crafted]].}}
{{History||1.8|snap=14w30a|Added [[banner]]s, which can be [[dye]]d.}}
{{History||1.11|snap=16w39a|Added the ability to dye [[shulker box]]es.}}
{{History||1.12|snap=17w06a|Yellow dye can now be used to craft yellow [[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 now been split up into their own IDs.
|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 351.}}
{{History||1.14|snap=18w43a|"Dandelion Yellow" has now been renamed to "Yellow Dye".
|[[File:Yellow Dye JE2 BE2.png|32px]] The texture of yellow dye has now been changed.}}
{{History|||snap=18w44a|Yellow dye can now change the text color on [[sign]]s to yellow.}}
{{History|||snap=18w49a|Yellow dye can now be found in [[chest]]s in [[village]] mason houses.}}
{{History|||snap=19w05a|Added the [[wandering trader]], which sells yellow dye.}}
{{History|||snap=19w11a|Yellow dye can now be [[trading|bought]] by shepherd villagers.}}
{{History||1.17|snap=20w45a|Yellow dye can now be used to craft [[yellow candle]]s.}}
{{History|||snap=21w19a|Yellow dye can no longer be used to craft yellow candles.}}
{{History|||snap=Pre-release 1|Yellow dye can once again used to craft yellow candles.}}
{{History||1.20<br>(Experimental)|link=1.19.3|snap=22w42a|Yellow dye can now change the text color on [[hanging sign]]s to yellow.}}
{{History||1.20|snap=23w12a|Yellow dye can now be found in [[suspicious gravel]] and [[suspicious sand]] in [[trail ruins]].}}
{{History|||snap=23w16a|Yellow dye no longer generates in [[suspicious sand]] in [[trail ruins]].|Due to the split of the archaeological loot tables for suspicious gravel within [[trail ruins]], yellow dye is now common loot.}}

{{History|pocket alpha}}
{{History||v0.3.0|[[File:Yellow Dye JE1 BE1.png|32px]] Added dandelion yellow.}}
{{History||v0.8.0|snap=build 1|Dandelion yellow is now used to craft [[cocoa beans]].}}
{{History||v0.14.0|snap=build 1|Yellow dye can now be used to dye [[water]] in [[cauldron]]s.}}
{{History||v0.16.0|snap=build 1|Dandelion yellow is no longer used to [[crafting|craft]] cocoa beans.}}
{{History|pocket}}
{{History||1.0.0|snap=alpha 0.17.0.1|Yellow dye can now be used to dye [[shulker]]s.}}
{{History||1.1.0|snap=alpha 1.1.0.0|Yellow dye can now be used to dye [[shulker box]]es, [[bed]]s, and craft [[concrete powder]].}}
{{History|bedrock}}
{{History||1.2.0|snap=beta 1.2.0.2|Yellow dye can now be used to craft patterns on [[banner]]s, [[firework star]]s, and [[stained glass]].}}
{{History||1.4.0|snap=beta 1.2.20.1|Yellow dye can now be used to craft [[balloon]]s and [[glow stick]]s.}}
{{History||1.8.0|snap=beta 1.8.0.8|Dandelion yellow can now be used to dye [[cat]] collars.}}
{{History|||snap=beta 1.8.0.10|"Dandelion Yellow" has now been renamed to "Yellow Dye".}}
{{History||1.10.0|snap=beta 1.10.0.3|Yellow dye is now [[trading|sold]] by [[wandering trader]]s.
|[[File:Yellow Dye JE2 BE2.png|32px]] The texture of yellow dye has now been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Yellow dye can now be found in [[village]] mason [[chest]]s.}}
{{History|||snap=beta 1.11.0.4|Yellow dye can now be sold to shepherd [[villager]]s.}}
{{History||1.16.100|snap=beta 1.16.100.56|The ID of yellow dye has been changed from <code>dye/11</code> to <code>yellow_dye</code>.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.00|switch=1.0.1|wiiu=Patch 1|[[File:Yellow Dye JE1 BE1.png|32px]] Added dandelion yellow.}}
{{History|ps4}}
{{History||1.83|"Dandelion Yellow" has now been renamed to "Yellow Dye".}}
{{History||1.90|[[File:Yellow Dye JE2 BE2.png|32px]] The texture of yellow dye has now been changed.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Yellow Dye JE1 BE1.png|32px]] Added dandelion yellow.}}
{{History|foot}}

== Issues ==

{{issue list}}

== References ==

{{reflist}}

{{Items}}

[[cs:Pampelišková žluť]]
[[de:Gelber Farbstoff]]
[[es:Tinte amarillo]]
[[fr:Teinture jaune]]
[[hu:Pitypangsárga]]
[[ja:黄色の染料]]
[[ko:노란색 염료]]
[[nl:Paardenbloemgeel]]
[[pl:Żółty barwnik]]
[[pt:Corante amarelo]]
[[ru:Жёлтый краситель]]
[[zh:黄色染料]]

[[Category:Items]]
[[Category:Dyes]]
[[Category:Renewable resources]]</li><li>[[Copper Ingot|Copper Ingot]]<br/>{{About|the ingot|the ore|Copper Ore|the mineral block|Block of Copper}}
{{Item
| image = Copper Ingot.png
| renewable = Yes
| stackable = Yes (64)
}}

'''Copper ingots''' are [[metal]] ingots obtained from smelting [[raw copper]] or killing [[drowned]].

== Obtaining ==

=== Crafting ===
{{Crafting
 |Block of Copper;Waxed Block of Copper|Output=Copper Ingot,9
 |type=Miscellaneous
}}

=== Smelting ===
Copper ingots can be obtained by smelting [[raw copper]] in a [[furnace]] or [[blast furnace]], as well as the ore itself if mined using [[Silk Touch]].

{{Smelting
|head=1
|Raw Copper
|Copper Ingot
|0.7
}}
{{Smelting
|foot=1
|Copper Ore; Deepslate Copper Ore
|Copper Ingot
|0.7
}}

=== Mob loot ===

==== Drowned ====

When killed by a [[player]] or a tamed [[wolf]], a [[drowned]] has a 11% ({{frac|11|100}}) chance of dropping a copper ingot. With the [[Looting]] enchantment, the chance can be increased to 13% ({{frac|13|100}}) with Looting I, 15% ({{frac|3|20}}) with Looting II, and 17% ({{frac|17|100}}) with Looting III.

== Usage ==

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

=== Smithing ingredient ===
{{Smithing
|head=1
|ingredients=Any Armor Trim +<br/>Any Armor Piece + <br/>Copper Ingot
|Any Armor Trim Smithing Template
|Netherite Chestplate
|Copper Ingot
|Copper 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|copper ingot}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Copper Ingot
|spritetype=item
|nameid=copper_ingot
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Copper Ingot
|spritetype=item
|nameid=copper_ingot
|form=item
|id=504
|foot=1}}

== History ==
{{History|java}}
{{History||1.17|snap=20w45a|[[File:Copper Ingot JE1.png|32px]] Added copper ingots.}}
{{History|||snap=20w46a|[[File:Copper Ingot JE2 BE1.png|32px]] The texture of copper ingots has been changed.|Crafting copper ingots from and into copper blocks now outputs/requires only 4 ingots.}}
{{History|||snap=21w05a|[[Drowned]] can now drop copper ingots when killed instead of [[gold ingots]], making copper ingots renewable.}}
{{History|||snap=21w10a|Copper ingots can now be smelted from [[deepslate copper ore]].}}
{{History|||snap=21w14a|Copper ingots can now be smelted from [[raw copper]].}}
{{History|||snap=21w17a|The amount of copper ingots required to make a [[block of copper]] has been changed back to 9.}}
{{History||1.17.1|snap=Pre-release 1|Increased the chance of [[drowned]] dropping a copper ingot from 5% to 11% and the increase of this chance for each level of [[Looting]] enchantment from 1% to 2% to match {{el|be}}.}}
{{History||1.20<br>(Experimental)|link=1.19.4|snap=23w04a|Copper ingots can now be used as an armor trim material.}}
{{History|||snap=1.19.4 Pre-release 1|Copper ingots can now be used to craft [[brush]]es.}}

{{History|bedrock}}
{{History||Caves & Cliffs (experimental)|link=Bedrock Edition 1.17.0|snap=beta 1.16.210.57|[[File:Copper Ingot JE2 BE1.png|32px]] Added copper ingots.}}
{{History||1.17.0|snap=beta 1.17.0.50|Copper ingots can now be used to craft [[spyglass|spyglasses]].}}
{{History|||snap=beta 1.17.0.52|Copper ingots are now available without enabling [[experimental gameplay]].}}
{{History|||snap=beta 1.17.0.54|The amount of copper ingots required to make a [[block of copper]] has been changed to 9.}}
{{History||Vanilla Experiments (experimental)|link=1.18.30|snap=beta 1.18.30.26|Copper ingots can now be used to craft copper horns.}}
{{History||1.19.0|snap=beta 1.19.0.24|Copper ingots can no longer be used to craft copper horns, as copper horns have been removed.}}
{{History||1.20.0<br>(Experimental)|link=Bedrock Edition 1.19.80|snap=beta 1.19.80.20|Copper ingots can now be used to craft [[brush]]es.}}
{{History|||snap=beta 1.19.80.21|Copper ingots can now be used as an armor trim material.}}
{{History|foot}}

== Issues ==
{{Issue list}}

== External Links ==
*[https://www.minecraft.net/en-us/article/taking-inventory--copper-ingot Taking Inventory:Copper Ingot] – Minecraft.net on December 22, 2022

{{Items}}

[[Category:Renewable resources]]

[[de:Kupferbarren]]
[[es:Lingote de cobre]]
[[fr:Lingot de cuivre]]
[[it:Lingotto di rame]]
[[ja:Copper Ingot]]
[[ko:구리괴]]
[[pl:Sztabka miedzi]]
[[pt:Barra de cobre]]
[[ru:Медный слиток]]
[[uk:Мідний злиток]]
[[zh:铜锭]]</li></ul>
13w04aAdded scoreboard.
13w05aAdded team-based functionality.
1.7.2
{{Extension DPL}}<ul><li>[[Prismarine Shard|Prismarine Shard]]<br/>{{Item
| renewable =  Yes
| stackable = Yes (64)
| type =
}}
A '''prismarine shard''' is an item obtained by defeating [[guardian]]s or [[elder guardian]]s. It can be used to craft various [[prismarine]] blocks as well as [[sea lantern]]s.

== Obtaining ==

Prismarine shards are dropped upon the death of [[guardian]]s and [[elder guardian]]s. From these mobs, 0–2 shards are dropped each time. This can be increased to a maximum of 5 with the [[Looting]] enchantment.

== Usage ==

=== Crafting ingredient ===

{{crafting usage}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Prismarine Shard
|spritetype=item
|nameid=prismarine_shard
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|showaliasids=y
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Prismarine Shard
|spritetype=item
|nameid=prismarine_shard
|aliasid=prismarineshard
|id=565
|form=item
|foot=1}}

== History ==

{{History|java}}
{{history||1.8|snap=14w25a|[[File:Prismarine Shard JE1 BE1.png|32px]] Added prismarine shards.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 409.}}
{{History||1.14|snap=18w43a|[[File:Prismarine Shard JE2 BE2.png|32px]] The texture of prismarine shards has now been changed.}}

{{History|pocket alpha}}
{{History||v0.16.0|snap=build 1|[[File:Prismarine Shard JE1 BE1.png|32px]] Added prismarine shards.}}
{{History|bedrock}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Prismarine Shard JE2 BE2.png|32px]] The texture of prismarine shards has now been changed.}}

{{History|console}}
{{History||xbox=TU31|xbone=CU19|ps=1.22|wiiu=Patch 3|[[File:Prismarine Shard JE1 BE1.png|32px]] Added prismarine shards.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Prismarine Shard JE2 BE2.png|32px]] The texture of prismarine shards has now been changed.}}

{{History|New 3DS}}
{{History||1.3.12|[[File:Prismarine Shard JE1 BE1.png|32px]] Added prismarine shards.}}
{{History|foot}}

== Issues ==

{{issue list}}

{{items}}

[[de:Prismarinscherbe]]
[[es:Fragmento de prismarina]]
[[fr:Éclat de prismarine]]
[[ja:プリズマリンの欠片]]
[[ko:프리즈머린 조각]]
[[nl:Prismarienscherf]]
[[pl:Odłamek pryzmarynu]]
[[pt:Pedaço de prismarinho]]
[[ru:Призмариновый осколок]]
[[uk:Призмариновий уламок]]
[[zh:海晶碎片]]
[[Category:Renewable resources]]</li><li>[[Redstone Repeater|Redstone Repeater]]<br/>{{Block
| image = <gallery>
Redstone Repeater.png|Redstone Repeater
Redstone Repeater BE.png|Redstone Repeater (BE)
</gallery>
| extratext = View [[#Renders|all renders]]
| transparent = Yes
| light = No
| tool = any
| stackable = Yes (64)
| flammable = No
| lavasusceptible = No
| renewable = Yes
}}
{{about|the block|repeater circuits|Transmission circuit#Repeater|other topics related to redstone|Redstone (disambiguation)}}
A '''redstone repeater''' is a [[block]] that produces a full-strength [[Redstone Dust|output signal]] from its front when its back is powered, with four configurable delay settings. It can also be locked into a power state by its side being directly powered by a repeater or a [[Redstone Comparator|comparator]].

== Obtaining ==
=== Breaking ===
A redstone repeater can be broken instantly using any [[tool]], or without a tool, and drops itself as an item. To remove a redstone repeater, {{control|mine}} it.

A redstone repeater is removed and drops as an item if:
* its attachment block is moved, removed, or destroyed;
* [[water]] or [[lava]] flows into its space;{{only|java}}
* a [[piston]] tries to push it or moves a block into its space.

=== Natural generation ===
[[File:Redstone Repeater naturally generated.png|thumb|A redstone repeater generated in the jungle temple's hidden room.]]
A single redstone repeater is generated naturally in each [[jungle temple]].
They also generate in [[Ancient City|ancient cities]].

=== Crafting ===
{{Crafting
|A2= Redstone Torch
|B2= Redstone Dust
|C2= Redstone Torch
|B3= Stone
|C3= Stone
|A3= Stone
|Output= Redstone Repeater
|type= Redstone
}}

== Usage ==
{{see also|Redstone circuit}}
A redstone repeater can be used in four different ways: to "repeat" redstone signals back to full strength, delay signals, prevent signals moving backwards, or to "lock" signals in one state.

A repeater can be placed only on top of [[opaque]] blocks (dirt, stone, etc.), on top of upside-down [[slab]]s, upside-down [[stairs]], furnaces, and glass. {{IN|be}}, a repeater can also be placed on fences and stone walls. They can also be placed on some transparent blocks. See [[Opacity/Placement]] for more information. To place a repeater, use the {{control|Place Block}} [[control]].

A redstone repeater has a front and back – the arrow on the top points to the repeater's front. A repeater also has two small redstone torches on its top – the color of the torches indicates whether its output is on (dark red when off, bright red when on) and the distance between them indicates the delay the repeater adds to the signal transmission.

A repeater is 0.125 ({{frac|1|8}}) blocks high.

=== Signal transmission ===
A repeater transmits signals only from its back to its front, but its behavior can be modified from the side (see [[#Signal locking|signal locking]], below).

[[File:Redstone Torch Power.png|Different ways to power a repeater|thumb]]
A redstone repeater can be powered by any of the following components at its back:
* an active [[power component]] (redstone torch, lever, block of redstone, etc.)
* powered [[redstone dust]]
* a powered [[redstone comparator]] or another powered redstone repeater facing the repeater
* a powered opaque block (including any opaque [[mechanism component]]s, such as [[dispenser]]s, [[redstone lamp]]s, etc.)

A redstone repeater can power any of the following components at its front:
* redstone dust
* a redstone comparator or another redstone repeater facing away from the repeater
* any opaque block (including any opaque [[mechanism component]]s)

A redstone repeater can activate any [[mechanism component]] it is facing.

An opaque block powered by a redstone repeater is called "strongly-powered" (as opposed to an opaque block "weakly-powered" by redstone dust). A strongly-powered opaque block can power adjacent redstone dust, as well as other redstone components.

=== Signal repeating ===
{{see also|Transmission circuit#Repeater}}
A redstone repeater can "repeat" a [[Redstone Dust|redstone]] signal, boosting it back up to power level 15.

Redstone signals have a maximum power level of 15 and that level drops by 1 for every block of [[redstone dust]] the signal travels through. If a signal must travel through more than 15 [[block]]s of redstone dust, a redstone repeater can be used to boost the signal back up to full strength. An extra two blocks of distance can be achieved by placing solid opaque blocks before and after the repeater.

While redstone repeaters can allow signals to travel great distances, each always adds some delay to the transmission since the minimum amount of delay is 1 redstone tick (0.1 seconds, barring lag).

=== Signal delay ===
When initially placed, a redstone repeater has a delay of one [[redstone tick]] (equivalent to two game ticks, or 0.1 seconds barring lag).

A repeater's delay can be modified by using the {{control|Use Item}} control. Each use increases the repeater's delay by one redstone tick, to a maximum of four redstone ticks, then back to one redstone tick. Longer delays can be made with multiple repeaters – for example, a repeater set to 'four' and another to 'one' provides a half-second delay (0.4s + 0.1s = 0.5s).

A repeater set to a delay of two to four redstone ticks increases the length of any shorter [[Pulse circuit#Pulses|on-pulse]] to match the length of the repeater's delay, and suppress any shorter off-pulse. For example, a repeater set to a 4-tick delay changes a 1-tick, 2-tick, or 3-tick on-pulse into a 4-tick on-pulse, and does not allow through any off-pulse shorter than 4 ticks.

Although a repeater cannot be set to have a delay of zero, [[Transmission circuit#Instant repeater|instant repeater circuits]] are possible (circuits that repeat a signal with no delay).

In Bedrock Edition, the first repeater have a delay of zero but the repeater is still showing 1-tick{{info needed}}

=== {{anchor|diode}} Signal direction ===
{{see also| Mechanics/Redstone/Transmission circuit#Diode}}

A redstone repeater acts as a diode – it allows redstone signals through in one direction (unlike [[redstone dust]] or opaque blocks that can transmit redstone signals in any direction).

A diode can be used to protect a [[redstone circuit]] from redstone signals feeding back into the circuit from its output, or can be used to isolate one part of a circuit from another.

=== {{anchor|lock}} Signal locking ===
{{see also| Mechanics/Redstone/Memory circuit}}
[[File:Latch.png|thumb|The left repeater has been locked in an unpowered output state by the right repeater.]]
A redstone repeater can be "locked" by another powered redstone repeater facing its side. When locked, the repeater does not change its output (whether powered or unpowered), no matter what the input does. When the side repeater turns back off, the repeater returns to its normal behavior.

A repeater can also be locked by a powered [[redstone comparator]] facing its side. This offers additional possibilities for locking signals because a comparator's output can be affected from 3 sides as well as by containers.

If a repeater is locked again too quickly after unlocking (e.g. the lock is controlled by a fast clock circuit), or the lock and the input are changed only on the same tick (e.g. because they're fed by the same clock and both repeaters have the same delay), the repeater does not switch states.

== Sounds ==
{{Edition|java}}:
{{Sound table/Block/Stone/JE}}
{{Edition|bedrock}}:
{{Sound table/Block/Wood/BE}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Redstone Repeater
|spritetype=block
|nameid=repeater
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|firstcolumnname=Redstone Repeater
|shownumericids=y
|showforms=y
|generatetranslationkeys=y
|displayname=Unpowered block
|spritename=unpowered-repeater
|spritetype=block
|nameid=unpowered_repeater
|id=93
|form=block
|translationkey=-}}
{{ID table
|displayname=Powered block
|spritename=powered-repeater
|spritetype=block
|nameid=powered_repeater
|id=94
|form=block
|translationkey=-}}
{{ID table
|displayname=Item
|spritename=redstone-repeater
|spritetype=item
|nameid=repeater
|id=419
|form=item
|foot=1}}

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

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

== History ==
''For a more in-depth breakdown of changes to repeater textures and models, including a set of renders for each state combination, see [[/Asset history]]''
{{History|java beta}}
{{History||1.3|[[File:Redstone Repeater (S) JE1.png|32px]] [[File:Redstone Repeater (item) JE1.png|32px]] Added redstone repeaters.
|Originally, the four possible settings were "1, 2, 5 and 7",<ref>http://twitter.com/jeb_/status/33888465502339073</ref> but [[Jeb]] decided to change the settings to "1, 2, 3, and 4".<ref>http://www.reddit.com/r/Minecraft/comments/fmdtp/teammojang_redstone_repeater_video/c1gzrn6</ref>
|The particles when [[breaking]] redstone repeaters erroneously use the [[pumpkin]] top texture.}}
{{History||unknown|The breaking particles of redstone repeaters now use the smooth stone [[slab]] top texture, even though none of the elements on the [[model]] use it.}}
{{History||1.7|[[File:Redstone Repeater (S) JE2.png|32px]] The side texture of redstone repeaters has been changed to the previous bottom part of the texture.
|[[Redstone dust]] now automatically connects to the input of a redstone repeater. Previously, it needed to be specifically pointed towards the repeater like with other blocks.}}
{{History||unknown|Redstone dust now visually connects to the output of redstone repeaters, though this does not change its behavior.}}
{{History|java}}
{{History||unknown|The breaking particles of redstone repeaters have been changed to an unlit [[redstone torch]] when unpowered and a lit redstone torch when powered.}}
{{History||1.3.1|snap=12w22a|Redstone repeaters now naturally generate inside [[jungle temple]]s.}}
{{History|||snap=1.3|[[File:Redstone Repeater (item) JE2 BE1.png|32px]] The texture of redstone repeater [[item]]s have been changed.}}
{{History||1.4.2|snap=12w42a|[[File:Redstone Repeater (S) JE3.png|32px]] The top texture of redstone repeaters has now been changed.
|[[File:Locked Redstone Repeater (S) JE1.png|32px]] Added repeater locking to redstone repeaters. Interestingly, the smallest face of the bedrock cuboid's texture changes depending on the delay, but the other two faces remain the same. When/if this changed is unknown.}}
{{History||1.5|snap=13w02a|[[File:Redstone Repeater (S) JE4.png|32px]] The side textures of redstone repeaters have been changed to use the top texture of stone [[slab]]s.}}
{{History||unknown|The breaking [[particles|particle]] of redstone repeaters has been changed once again and now matches the top texture of redstone repeaters.}}
{{History||1.8|snap=14w06a|Repeaters no longer produce block [[light]] when powered.}}
{{History|||snap=14w10a|[[File:Powered Redstone Repeater (S) JE5.png|32px]] Torches on repeaters now no longer have protruding features.
|The torches underneath redstone repeaters have now been shortened, which has changed the underside textures from [[File:Redstone Repeater JE2 BE1 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 2 JE2 BE1 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 3 JE2 BE1 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 4 JE2 BE1 (facing NWU).png|32px]] [[File: Active Redstone Repeater JE2 BE1 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 2 JE2 BE1 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 3 JE2 BE1 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 4 JE2 BE1 (facing NWU).png|32px]] [[File: Locked Redstone Repeater JE2 BE1 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 2 JE2 BE1 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 3 JE2 BE1 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 4 JE2 BE1 (facing NWU).png|32px]] [[File: Active Locked Redstone Repeater JE2 BE1 (facing NWU).png|32px]] [[File: Active Locked Redstone Repeater Delay 2 JE2 BE1 (facing NWU).png|32px]] [[File: Active Locked Redstone Repeater Delay 3 JE2 BE1 (facing NWU).png|32px]] [[File: Active Locked Redstone Repeater Delay 4 JE2 BE1 (facing NWU).png|32px]] to [[File:Redstone Repeater JE3 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 2 JE3 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 3 JE3 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 4 JE3 (facing NWU).png|32px]] [[File: Active Redstone Repeater JE3 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 2 JE3 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 3 JE3 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 4 JE3 (facing NWU).png|32px]] [[File: Locked Redstone Repeater JE3 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 2 JE3 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 3 JE3 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 4 JE3 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater JE3 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 2 JE3 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 3 JE3 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 4 JE3 (facing NWU).png|32px]].}}
{{History|||snap=14w10b|[[File:Powered Redstone Repeater (S) JE4.png|32px]] Repeater torches now have protruding features again.<ref>{{bug|MC-50242}}</ref>}}
{{History|||snap=?|[[File:Powered Redstone Repeater (S) JE7.png|32px]] The torches on redstone repeaters are now affected by directional shading.}}
{{History||1.13|snap=17w47a|All 3 IDs for the redstone repeater have now been merged into 1 ID: <code>repeater</code>.
|Added powered block state to redstone repeaters.
|Redstone repeaters now render their underside, which has changed their undersides from [[File:Redstone Repeater JE3 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 2 JE3 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 3 JE3 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 4 JE3 (facing NWU).png|32px]] [[File: Active Redstone Repeater JE3 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 2 JE3 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 3 JE3 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 4 JE3 (facing NWU).png|32px]] [[File: Locked Redstone Repeater JE3 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 2 JE3 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 3 JE3 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 4 JE3 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater JE3 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 2 JE3 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 3 JE3 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 4 JE3 (facing NWU).png|32px]] to [[File:Redstone Repeater JE4 BE2 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 2 JE4 BE2 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 3 JE4 BE2 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 4 JE4 BE2 (facing NWU).png|32px]] [[File: Active Redstone Repeater JE4 BE2 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 2 JE4 BE2 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 3 JE4 BE2 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 4 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Redstone Repeater JE4 BE2 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 2 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 3 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 4 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater JE4 BE2 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 2 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 3 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 4 JE4 BE2 (facing NWU).png|32px]].
|Prior to [[1.13/Flattening|''The Flattening'']], these [[block]]s' numeral IDs were 93 and 94, and the [[item]]'s 356.}}
{{History||1.14|snap=18w43a|[[File:Redstone Repeater (S) JE5.png|32px]] [[File:Powered Redstone Repeater (S) JE9.png|32px]] [[File:Locked Redstone Repeater (S) JE5.png|32px]] [[File:Powered Locked Redstone Repeater (S) JE6.png|32px]] [[File:Redstone Repeater (item) JE3 BE2.png|32px]] The textures of redstone repeaters have now been changed.}}
{{History|||snap=18w50a|[[File:Locked Redstone Repeater (S) JE6.png|32px]] [[File:Powered Locked Redstone Repeater (S) JE7.png|32px]] As the texture of [[bedrock]] has been changed, the textures of locked redstone repeaters have also now been changed.}}
{{History|||snap=19w12b|Redstone repeaters can now be placed on [[glass]], [[ice]], [[glowstone]] and [[sea lantern]]s.}}
{{History||1.19|snap=22w13a|Redstone repeaters now generate in [[Ancient City|ancient cities]].}}
{{History||1.20.2|snap=23w33a|Redstone repeaters now use stone sounds instead of wood sounds.<ref>{{bug|MC-182820|||Fixed}}</ref>}}

{{History|pocket alpha}}
{{History||v0.14.0|snap=build 1|[[File:Redstone Repeater (S) JE3.png|32px]] [[File:Redstone Repeater (item) JE2 BE1.png|32px]] Added redstone repeaters.}}
{{History|bedrock}}
{{History||1.2.0|snap=beta 1.2.0.2|Redstone repeaters now render their underside, which has changed their undersides from [[File:Redstone Repeater JE2 BE1 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 2 JE2 BE1 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 3 JE2 BE1 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 4 JE2 BE1 (facing NWU).png|32px]] [[File: Active Redstone Repeater JE2 BE1 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 2 JE2 BE1 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 3 JE2 BE1 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 4 JE2 BE1 (facing NWU).png|32px]] [[File: Locked Redstone Repeater JE2 BE1 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 2 JE2 BE1 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 3 JE2 BE1 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 4 JE2 BE1 (facing NWU).png|32px]] [[File: Active Locked Redstone Repeater JE2 BE1 (facing NWU).png|32px]] [[File: Active Locked Redstone Repeater Delay 2 JE2 BE1 (facing NWU).png|32px]] [[File: Active Locked Redstone Repeater Delay 3 JE2 BE1 (facing NWU).png|32px]] [[File: Active Locked Redstone Repeater Delay 4 JE2 BE1 (facing NWU).png|32px]] to [[File:Redstone Repeater JE4 BE2 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 2 JE4 BE2 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 3 JE4 BE2 (facing NWU).png|32px]] [[File: Redstone Repeater Delay 4 JE4 BE2 (facing NWU).png|32px]] [[File: Active Redstone Repeater JE4 BE2 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 2 JE4 BE2 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 3 JE4 BE2 (facing NWU).png|32px]] [[File: Active Redstone Repeater Delay 4 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Redstone Repeater JE4 BE2 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 2 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 3 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Redstone Repeater Delay 4 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater JE4 BE2 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 2 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 3 JE4 BE2 (facing NWU).png|32px]] [[File: Locked Active Redstone Repeater Delay 4 JE4 BE2 (facing NWU).png|32px]].}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Redstone Repeater (S) BE2.png|32px]] [[File:Powered Redstone Repeater (S) BE2.png|32px]] [[File:Redstone Repeater (item) JE3 BE2.png|32px]] The textures of redstone repeaters have now been changed.}}
{{History||1.20.30|snap=beta 1.20.30.20|Redstone Repeaters now use the <code>minecraft:cardinal_direction</code> [[block state]] instead of <code>direction</code>.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Redstone Repeater (S) JE3.png|32px]]{{verify|Was this model actually used here?}} [[File:Redstone Repeater (item) JE2 BE1.png|32px]] Added redstone repeaters.}}
{{History||xbox=TU19|xbone=CU7|ps=1.12|wiiu=Patch 1|switch=1.0.1|[[File:Locked Redstone Repeater (S) JE1.png|32px]]{{verify|Was this model actually used here?}} Added repeater locking to redstone repeaters.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Redstone Repeater (S) JE4.png|32px]]{{verify|Was this model actually used here?}} [[File:Redstone Repeater (item) JE3 BE2.png|32px]] The textures of redstone repeaters have now been changed.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Redstone Repeater (S) JE3.png|32px]]{{verify|Was this model actually used here?}} [[File:Redstone Repeater (item) JE2 BE1.png|32px]] Added redstone repeaters and repeater locking.}}
{{History|foot}}

=== Redstone repeater "items" ===
{{:Technical blocks/Redstone Repeater}}

== Issues ==
{{Issue list}}

== Trivia ==
* The recipe and appearance of redstone repeaters are a likely reference to the old method of repeating signals, which would also use two torches at a time, inverting each other

== Gallery ==
<gallery>
Repeater clock.gif|A redstone clock formed from a redstone torch and a repeater.
Repeater feedback.gif|A redstone clock formed from two repeaters.
Two way repeater.gif|MCRedstoneSim diagram of a two-way repeater.
Repeater bridge.png|Crossing redstone wires using repeaters.
Jeb Repeaters 1.png|
Jeb Repeaters 2.png|
Jeb Repeaters 3.png|
</gallery>

=== Renders ===
<gallery>
Redstone Repeater.png
Redstone Repeater Delay 2.png
Redstone Repeater Delay 3.png
Redstone Repeater Delay 4.png
Powered Redstone Repeater.png
Powered Redstone Repeater Delay 2.png
Powered Redstone Repeater Delay 3.png
Powered Redstone Repeater Delay 4.png
Locked Redstone Repeater.png
Locked Redstone Repeater Delay 2.png
Locked Redstone Repeater Delay 3.png
Locked Redstone Repeater Delay 4.png
Powered Locked Redstone Repeater.png
Powered Locked Redstone Repeater Delay 2.png
Powered Locked Redstone Repeater Delay 3.png
Powered Locked Redstone Repeater Delay 4.png
Redstone Repeater BE.png
Redstone Repeater Delay 2 BE.png
Redstone Repeater Delay 3 BE.png
Redstone Repeater Delay 4 BE.png
Powered Redstone Repeater BE.png
Powered Redstone Repeater Delay 2 BE.png
Powered Redstone Repeater Delay 3 BE.png
Powered Redstone Repeater Delay 4 BE.png
Locked Redstone Repeater BE.png
Locked Redstone Repeater Delay 2 BE.png
Locked Redstone Repeater Delay 3 BE.png
Locked Redstone Repeater Delay 4 BE.png
Powered Locked Redstone Repeater BE.png
Powered Locked Redstone Repeater Delay 2 BE.png
Powered Locked Redstone Repeater Delay 3 BE.png
Powered Locked Redstone Repeater Delay 4 BE.png
</gallery>

== References ==
{{Reflist}}

{{Redstone}}
{{Blocks|Utility}}
{{Items}}

[[Category:Mechanics]]
[[Category:Redstone mechanics]]
[[Category:Redstone]]
[[Category:Mechanisms]]
[[Category:Manufactured blocks]]
[[Category:Generated structure blocks]]
[[Category:Non-solid blocks]]

[[de:Redstone-Verstärker]]
[[es:Repetidor de redstone]]
[[fr:Répéteur de redstone]]
[[hu:Redstone-jelismétlő]]
[[it:Ripetitore di redstone]]
[[ja:レッドストーンリピーター]]
[[ko:레드스톤 중계기]]
[[nl:Redstoneversterker]]
[[pl:Przekaźnik]]
[[pt:Repetidor de redstone]]
[[ru:Красный повторитель]]
[[tr:Kızıltaş tekrarlayıcı]]
[[zh:红石中继器]]</li></ul>
13w36aAdded statistic-based objective criteria.
1.8
{{Extension DPL}}<ul><li>[[Nautilus Shell|Nautilus Shell]]<br/>{{Item
| type =
| stackable = Yes (64)
| renewable = Yes
}}

A '''nautilus shell''' is an item that is used for crafting [[conduit]]s.

==Obtaining==
===Fishing===
{{main|Fishing#Junk and treasure}}
Nautilus shells can be rarely obtained as a treasure item from fishing. The drop chances of nautilus shells slightly increase with each level of [[Luck of the Sea]] on the [[player]]'s [[fishing rod]].

===Mob loot===
[[Drowned]] have a 3%{{only|java|short=1}} or 8%{{only|bedrock|short=1}} chance to spawn with a nautilus shell in their off-hand, and this nautilus shell always drops upon [[death]].

===Trading===
[[Wandering trader]]s may [[trading|sell]] a nautilus shell for 5 [[emerald]]s each, but they only sell 5 of them at a time.

==Usage==
{{IN|bedrock}}, a nautilus shell is one of the few items that can be held in the off-hand.

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

=== Trading ===
Nautilus shells can be given to trident-wielding drowned with a chance for the drowned to pick up the shell and drop the trident.<sup>[''[[Bedrock Edition]] only'']</sup>

==Data values==
===ID===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Nautilus Shell
|spritetype=item
|nameid=nautilus_shell
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Nautilus Shell
|spritetype=item
|nameid=nautilus_shell
|id=570
|form=item
|foot=1}}

==History==
{{History|java}} 
{{History||1.13|snap=18w15a|[[File:Nautilus Shell JE1 BE2.png|32px]] Added nautilus shells.}}
{{History||1.14|snap=19w05a|Added [[Wandering Trader|wandering trader]]s, which sell nautilus shells.}}

{{History|bedrock}}
{{History||1.4.0|snap=beta 1.2.20.1|[[File:Nautilus Shell BE1.png|32px]] Added nautilus shells.}}
{{History|||snap=beta 1.2.20.2|[[File:Nautilus Shell JE1 BE2.png|32px]] The texture of nautilus shells has now been changed.}}
{{History||1.5.0|snap=beta 1.5.0.0|[[Drowned]] now sometimes spawn holding a nautilus shell.
|Nautilus shells are no longer behind [[Experimental Gameplay]].}}
{{History|||snap=beta 1.5.0.1|Nautilus shells can now be used to craft [[conduit]]s.}}
{{History||1.10.0|snap=beta 1.10.0.3|Nautilus shells can now be obtained from [[trading]] with [[wandering trader]]s.}}

{{History|console}}
{{History||xbox=TU69|ps=1.76|wiiu=Patch 38|[[File:Nautilus Shell JE1 BE2.png|32px]] Added nautilus shells.}}
{{History||xbox=none|ps=1.91|wiiu=none|Nautilus shells can now be obtained from [[trading]] with [[wandering trader]]s.}}
{{History|foot}}

==Issues==
{{issue list}}

==Trivia==
*[[wikipedia:Nautilus|Nautilus]]es are animals that occupy deep oceans in the real world. However, they are absent in Minecraft and there are currently no plans to add nautilus [[mob]]s into the game.
*Because {{el|bedrock}} allows for Nautilus shells to be held in the off-hand (since drowned hold them), they are the only item in that version that can be put in the off-hand slot without having a specific function.

{{items}}

[[de:Nautilusschale]]
[[es:Caparazón de nautilo]]
[[fr:Coquille de nautile]]
[[it:Conchiglia di nautilus]]
[[ja:オウムガイの殻]]
[[ko:앵무조개 껍데기]]
[[nl:Nautilusschelp]]
[[pl:Muszla łodzika]]
[[pt:Concha de náutilo]]
[[ru:Раковина наутилуса]]
[[th:เปลือกหอยงวงช้าง]]
[[uk:Мушля наутилуса]]
[[zh:鹦鹉螺壳]]
[[Category:Renewable resources]]</li><li>[[Glass Bottle|Glass Bottle]]<br/>{{about|the empty bottle||Bottle}}

{{Item
| image = Glass Bottle.png
| renewable = Yes
| stackable = Yes (64)
}}

A '''glass bottle''' is an [[item]] that can hold [[water]], [[potion]]s, [[Honey Bottle|honey]], or [[dragon's breath]].

== Obtaining ==

Glass bottles can be obtained by crafting, drinking from bottles, [[fishing]], or from [[witch]] drops.

=== Crafting ===

{{Crafting
|A2= Glass
|C2= Glass
|B3= Glass
|Output= Glass Bottle,3
|type= Brewing
}}

=== Drinking ===

Drinking a [[potion]] or [[Honey Bottle|honey bottle]] returns the empty glass bottle. Throwing a splash potion or a lingering potion does not return a glass bottle, but brewing a lingering potion gives back a glass bottle.

=== Mob loot ===

[[Witch]]es have a chance of dropping 0–6 glass bottles upon death. This is increased by 3 per level of [[Looting]], for a maximum of 0–15 glass bottles.

=== Mud ===

{{control|Using}} a [[water bottle]], [[splash water bottle]] or [[lingering water bottle]] on [[dirt]], [[coarse dirt]] or [[rooted dirt]] will transforming it into a [[mud]] block, at the same time leaving the player with an empty glass bottle.

=== Cauldrons ===

{{control|Using}} a water bottle (or, {{in|bedrock}}, a potion, splash potion, or lingering potion) on a [[cauldron]] that is not yet full adds that liquid to the cauldron, leaving the player with an empty glass bottle.

== Usage ==

Glass bottles can be filled to make [[water bottle]]s, which can then be used to [[brew]] items with a [[brewing stand]]. Glass bottles are also used to hold the resulting [[potion]].

=== Collecting liquids ===

==== Water ====
A bottle may be filled with water by holding it in the hand and {{control|using}} it on a [[water]] source block or a [[cauldron]] that has water in it. It can also be filled using a waterlogged block.{{only|java}}<ref>{{bug|MCPE-83420}}</ref>

Also, a bottle may be filled by powering a [[dispenser]] containing a bottle and pointed at a water source block. This does not work with cauldrons.<ref>{{bug|MC-165196|||Invalid}}</ref>

If filled via a water source, the water is unaffected. If filled via a cauldron, {{frac|1|3}} of the water in the cauldron is removed. Therefore, using a cauldron to fill water bottles is inefficient, except in [[the Nether]] where it is normally the only way to fill bottles.

==== Potion ====
{{IN|bedrock}}, a bottle may be filled with potion by {{control|using}} it on a [[cauldron]] containing potion. When the bottle is filled, {{frac|1|3}} of the cauldron's potion is removed.

==== Honey ====
If a [[beehive|bee nest]] or [[beehive]] is full, the player can {{control|use}} a glass bottle on the block, or may power a [[dispenser]] that contains a bottle and is pointed at the block, which empties the block and creates a [[honey bottle]]. Honey bottles can also be emptied by using them in crafting recipes (such as [[sugar]] or [[honey block]]). However, a lingering potion use on tipped arrow recipe does not give the bottle back.

==== Dragon's breath ====
{{control|Using}} a glass bottle in clouds emitted when the [[ender dragon]] breathes or shoots a [[dragon fireball]] fills the bottle with [[dragon's breath]].

When put 2 or more dragon's breath in the brewing stand, after the brewing process, a glass bottle will drop as an [[Item (entity)|entity]]. However, if put only 1 dragon's breath in the brewing stand, after the brewing process, the glass bottle is consumed and cannot be retrieved.<ref>{{bug|MC-259583}}</ref>

=== Trading ===

Expert-level cleric [[villager]]s have a 50% chance to buy 9 glass bottles for one [[emerald]] as part of their trade.{{only|bedrock}}

Expert-level cleric villagers have a {{frac|2|3}} chance to buy 9 glass bottles for one emerald.{{only|java}}

=== Crafting ingredients ===
{{Crafting usage|Glass Bottle}}

== Sounds ==
{{edition|java}}:
{{Sound table
|rowspan=2
|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 a liquid from a cauldron, or honey from a bee nest or beehive
|id=item.bottle.fill
|translationkey=subtitles.item.bottle.fill
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|subtitle=Bottle fills
|source=neutral
|description=When a bottle is filled with water from a water source
|id=item.bottle.fill
|translationkey=subtitles.item.bottle.fill
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|sound=Bottle empty1.ogg
|sound2=Bottle empty2.ogg
|subtitle=Bottle empties
|source=block
|description=When a water bottle is emptied
|id=item.bottle.empty
|translationkey=subtitles.item.bottle.empty
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|sound=Bottle fill dragon breath1.ogg
|sound2=Bottle fill dragon breath2.ogg
|subtitle=Bottle fills
|source=neutral
|description=When a bottle is filled with dragon's breath
|id=item.bottle.fill_dragonbreath
|translationkey=subtitles.item.bottle.fill
|volume=1.0
|pitch=1.0
|distance=16
|foot=1}}

{{edition|java}}:
{{Sound table
|type=bedrock
|rowspan=4
|sound=Water Splash Old.ogg
|source=block
|description=When water from a bottle is placed in a cauldron<wbr><ref group=sound name=potionsplash>{{Bug|MCPE-174867}}</ref>
|id=cauldron.fillwater
|volume=0.1
|pitch=1.0}}
{{Sound table
|source=block
|description=When water from a bottle is taken from a cauldron<wbr><ref group=sound name=potionsplash/>
|id=cauldron.takewater
|volume=0.1
|pitch=1.0}}
{{Sound table
|source=block
|description=When a bottle is filled with a potion from a cauldron<wbr><ref group=sound name=potionsplash/>
|id=cauldron.fillpotion
|volume=0.1
|pitch=1.0}}
{{Sound table
|source=block
|description=When a potion bottle is emptied into a cauldron<wbr><ref group=sound name=potionsplash/>
|id=cauldron.takepotion
|volume=0.1
|pitch=1.0}}
{{Sound table
|sound=Bottle empty1.ogg
|sound2=Bottle empty2.ogg
|source=sound<!--bottle-->
|description=When a bottle is emptied<wbr>{{Upcoming|BE 1.20.40}}
|id=bottle.empty
|volume=1.0
|pitch=1.0}}
{{Sound table
|sound=Bottle fill water1.ogg
|sound2=Bottle fill water2.ogg
|sound3=Bottle fill water3.ogg
|sound4=Bottle fill water4.ogg
|source=sound<!--bottle-->
|description=When a bottle is filled<wbr>{{Upcoming|BE 1.20.40}}
|id=bottle.fill
|volume=1.0
|pitch=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 from a bee nest or beehive<wbr><ref group=sound>{{Bug|MCPE-53881}}</ref>
|id=bucket.fill_water
|volume=1.0
|pitch=1.0}}
{{Sound table
|sound=Bottle fill dragon breath1.ogg
|sound2=Bottle fill dragon breath2.ogg
|source=sound
|description=When a bottle is filled with dragon's breath
|id=bottle.dragonbreath
|volume=0.7<wbr>{{Until|BE 1.20.40}}<br>1.0<wbr>{{Upcoming|BE 1.20.40}}
|pitch=1.0
|foot=1}}

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

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Glass Bottle
|spritetype=item
|id=427
|nameid=glass_bottle
|form=item
|foot=1}}

== Achievements ==

{{Load achievements|You Need a Mint;Local Brewery;Bee Our guest}}

== Advancements ==
{{load advancements|Local Brewery;You Need a Mint;Bee Our Guest}}

== History ==
{{History|java}}
{{History||1.0.0|snap=Beta 1.9 Prerelease 2|[[File:Glass Bottle JE1 BE1.png|32px]] Added glass bottles.}}
{{History|||snap=Beta 1.9 Prerelease 3|[[File:Water Bottle JE1 BE1.png|32px]] Glass bottles have been given their sole function of picking up [[water]] for the [[brewing]] of [[potion]]s.}}
{{History||1.4.2|snap=12w38b|[[Witch]]es now have a chance of [[drops|dropping]] glass bottles upon [[death]].}}
{{history||1.9|snap=15w33a|[[File:Dragon's Breath JE1 BE1.png|32px]] Glass bottles can now be used to obtain [[dragon's breath]].}}
{{history|||snap=15w43a|A glass bottle can be found in the [[brewing stand]] in an [[igloo]] basement.}}
{{history|||snap=15w43c|The glass bottle has been removed from igloo basements.}}
{{History|||snap=15w50a|Added [[sound]]s: <code>item.bottle.fill</code> and <code>item.bottle.fill_dragonbreath</code>.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 374.}}
{{History||1.14|snap=18w43a|[[File:Glass Bottle JE2 BE2.png|32px]] [[File:Water Bottle JE2 BE2.png|32px]] [[File:Dragon's Breath JE2 BE2.png|32px]] The textures of glass bottles, [[water bottle]]s and [[dragon's breath]] have been changed.}}
{{History|||snap=19w11a|Cleric [[villager]]s now [[trading|buy]] glass bottles.}}
{{History||1.15|snap=19w34a|[[File:Honey Bottle JE1.png|32px]] Glass bottles can now be used to collect [[Honey Bottle|honey]].
|[[Dispenser]]s may now use glass bottles to collect [[water]] and honey.}}
{{History|||snap=19w46a|Using glass bottles to collect honey now unlocks the [[Bee Our Guest]] advancement.}}
{{History||1.19|snap=22w11a|Converting [[dirt]], [[coarse dirt]] or [[rooted dirt]] into [[mud]] using a [[water bottle]], [[splash water bottle]] or [[lingering water bottle]] now leaves the player with an empty glass bottle.}}

{{History|pocket alpha}}
{{History||v0.12.1|snap=build 1|[[File:Glass Bottle JE1 BE1.png|32px]] Added glass bottles.}}
{{History||v0.14.0|snap=build 1|Glass bottles can now be used to empty [[cauldron]]s filled with [[water]] or [[potion]]s.
|Glass bottles can now be dropped by [[witch]]es.
|Potions and [[splash potion]]s can now be used to fill cauldrons, which turns them into glass bottles.}}
{{History|pocket}}
{{History||1.0.0|snap=alpha 0.17.0.1|[[File:Dragon's Breath JE1 BE1.png|32px]] Glass bottles can now be used to obtain [[dragon's breath]].
|[[Lingering potion]]s can now be used to fill [[cauldron]]s, which turns them into glass bottles.}}
{{History|bedrock}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Glass Bottle JE2 BE2.png|32px]] The texture of glass bottles has been changed.}}
{{History||1.11.0|snap=beta 1.11.0.4|Glass bottles can now be [[trading|sold]] to cleric [[villager]]s.}}
{{History||1.14.0|snap=beta 1.14.0.1|[[File:Honey Bottle BE1.png|32px]] Glass bottles can now be used to collect [[Honey Bottle|honey]].
|[[Dispenser]]s may now use glass bottles to collect [[water]] and honey.}}

{{History|console}}
{{History||xbox=TU7|xbone=CU1|ps=1.0|wiiu=Patch 1|[[File:Glass Bottle JE1 BE1.png|32px]] Added glass bottles.}}
{{History|PS4}}
{{History||1.90|[[File:Glass Bottle JE2 BE2.png|32px]] The texture of glass bottles has been changed.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Glass Bottle JE1 BE1.png|32px]] Added glass bottles.}}
{{History||1.7.10|[[File:Dragon's Breath JE1 BE1.png|32px]]  Glass bottles can now be used to obtain [[dragon's breath]].}}
{{history|foot}}

== Issues ==
{{issue list}}

==References==
{{Reflist}}

{{Items}}

[[cs:Lahvička]]
[[de:Glasflasche]]
[[es:Frasco de cristal]]
[[fr:Fiole]]
[[hu:Üvegpalack]]
[[it:Ampolla]]
[[ja:ガラス瓶]]
[[ko:유리병]]
[[nl:Glazen fles]]
[[pl:Szklana butelka]]
[[pt:Frasco]]
[[ru:Колба]]
[[zh:玻璃瓶]]
[[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.

Issues

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

Gallery

References

Advertisement