The scoreboard system is a complex gameplay mechanic intended mostly for map makers. It is used via commands and command blocks.
Objectives
Objectives are a combination of name, display name, and criteria, and track an integer number of points for players. The full score range is -2,147,483,648 to 2,147,483,647, and does not support decimals.
An objective's name is used internally when referenced in commands, target arguments, and in the file format. It is case-sensitive and must be a single word.
Conversely, the display name can be multiple words, and is displayed publicly in various situations. It is also case-sensitive, and does not have to be unique.
An objective's criteria determines its behavior:
| Criteria | Description | Can be Modified? |
|---|---|---|
| dummy | Score is only changed by commands, and not by game events such as death. This is useful for event flags, state mappings, and currencies. | Yes |
| trigger | Score is only changed by commands, and not by game events such as death. The /trigger command can be used by a player to set or increment/decrement their own score in an objective with this criteria. The /trigger command will fail if the objective has not been "enabled" for the player using it, and the objective will be disabled for the player after they use the /trigger command on it. Note that the /trigger command can be used by ordinary players even if Cheats are off and they are not an Operator. This is useful for player input via /tellraw interfaces. | Yes |
| deathCount | Score increments automatically for a player when they die. | Yes |
| playerKillCount | Score increments automatically for a player when they kill another player. | Yes |
| totalKillCount | Score increments automatically for a player when they kill another player or a mob. | Yes |
| health | Ranges from 0 to 20 on a normal player; represents the amount of half-hearts the player has. May appear as 0 for players before their health has changed for the first time. Extra hearts and absorption hearts also count to the health score, meaning that with Attributes/Modifiers or the Health Boost or Absorption Status effects, health can far surpass 20. | No |
In snapshot 13w36a, hundreds of new criteria were added.[1] These criteria use the Statistics and Achievements systems to form compound criteria.[2] 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.[3]
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", "timeSinceDeath", "treasureFished", and "walkOneCm". Score increments automatically for a player when they perform the action specified by the sub-criterion. | Yes | 26 | ||||
| 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.
Certain items, such as iron ingots, pickaxes, and cake, have achievement counterparts that increment in the same way. |
Yes | 199 (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. |
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. |
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", "EntityHorse", "Ghast", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "Sheep", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf", and "Zombie". Increments when a player has killed the specified mob. | Yes | 24 | ||||
| stat.entityKilledBy | The sub-criteria are the name of an entity. Valid names are: "Bat", "Blaze", "CaveSpider", "Chicken", "Cow", "Creeper", "Enderman", "EntityHorse", "Ghast", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "Sheep", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf", and "Zombie". Increments when a player has been killed by the specified mob. Note that if the name of a passive mob is used the value will never increase, as those mobs are not capable of hurting the player. |
Yes | 24 | ||||
| teamkill | The sub-criteria are the color of a team. Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Increments when a player has killed a member of a team with the specified color. | Yes | 16 | ||||
| killedByTeam | The sub-criteria are the color of a team. Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Increments when a player has been killed by a member of a team with the specified color. | Yes | 16 |
- ↑ a 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. "*" (an asterisk) may be used in place of player to represent every player tracked by the scoreboard. | objective must exist and cannot be read-only, and score must be between -2,147,483,648 and 2,147,483,647, inclusive. Note that player does not need to be online or even exist. If player exists and a dataTag is specified, player must match dataTag. |
| 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. |
| 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. For player "*" 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:
In all cases, selector's score in objective will remain unchanged. "*" may be used in place of either targetName or selector (but not both) to represent all players tracked by the scoreboard. |
objective and targetObjective must exist, targetObjective cannot be read-only, and all requested targets/selectors must have scores in the specified objectives (if some do and some do not, the operation will succeed only for the combinations where both the target and the selector have a score). Note that player does not need to be online or even exist. |
| scoreboard teams list [teamname] | Lists all teams, with their display names and the amount of players in them. The optional teamname parameter can be used to display all players on a particular team. | If teamname is specified, it must exist and must have players. If no teamname is specified, there must be at least one registered team on the scoreboard. |
| scoreboard teams add <name> [display name...] | Creates a team with the given name and optional display name. | name must not be used by an existing team, and must be at most 16 characters. display name must be at most 32 characters. |
| scoreboard teams remove <name> | Deletes the named team from the scoreboard system. | name must be an existing team. |
| scoreboard teams empty <name> | Removes all players from the named team. | name must be an existing team, and the team must have at least one player. |
| scoreboard teams join <team> [players...] | Assigns the specified players to the specified team. If no player is specified, the player running the command joins the team. "*" may be used to represent all players tracked by the scoreboard. | team must exist. Note that the named players do not need to be online or even exist, and can even already be on the team. |
| scoreboard teams leave [players...] 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", only the nametags of players on other teams will be hidden. When set to "hideForOwnTeam", only nametags of other players on one's own team will be hidden. When set to "always", all nametags will be visible. | team must exist, and the setting must be "never", "hideForOtherTeams", "hideForOwnTeam", or "always". |
| 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". |
- ↑ 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".
- An objective.
- PlayerScores: A list of compound tags representing scores tracked by the scoreboard system.
- A tracked player/objective pair with a score.
- Score: The score this player has in this objective.
- Name: The name of the player who has this score in this objective.
- Objective: The internal name of the objective which this player has this score in.
- 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.
- A tracked player/objective pair with a score.
- 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.
- A 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.
- Objectives: A list of compound tags representing objectives.
- data: The scoreboard data.
History
| r | |||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1.5{{Extension DPL}}<ul><li>[[Portfolio|Portfolio]]<br/>{{exclusive|education}}
{{Item
| image = Portfolio.png
| renewable = No
| stackable = Yes (64)
}}
A '''portfolio''' is an [[item]] that can save [[photo]]s taken with a [[camera]].<ref>https://education.minecraft.net/support/knowledge-base/using-cameras-portfolios/</ref>
== Obtaining ==
Portfolios can be obtained in the [[creative inventory]] or through the {{cmd|give}} command.
== Usage ==
[[File:Portfolio Interface.png|thumb|upright=1.5|The portfolio interface]]
Once a photo has been taken using the [[camera]], it appears in the portfolio. Once equipped, right-clicking brings up a two-page book of photos the [[player]] has taken, in chronological order. Captions can be added below each picture. Pressing the "Export Portfolio" button creates a .zip file with all photos as JPGs in a specified folder. The portfolio is also used to load custom items in [[Minecraft China]].
== Data values ==
=== ID ===
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Portfolio
|spritetype=item
|nameid=portfolio
|id=456
|form=item
|foot=1}}
== History ==
{{History|pocket alpha}}
{{History||v0.16.0|snap=build 1|[[File:Portfolio BE1.png|32px]] Added portfolios.}}
{{History|||snap=build 2|Portfolios have been removed.}}
{{History|bedrock}}
{{History||1.16.100|Data-driven portfolios, allowing for add-ons to create custom portfolios. Normal Portfolios are still unobtainable.}}
{{History|education}}
{{History||1.0|[[File:Portfolio BE1.png|32px]] Added portfolios.}}
{{History|foot}}
== References ==
{{Reflist}}
{{Items}}
{{Education Edition}}
[[Category:Non-renewable resources]]
[[Category:Education Edition items]]
[[Category:Storage]]
[[de:Fotoalbum]]
[[es:Portafolio]]
[[ja:ポートフォリオ]]
[[ko:포트폴리오]]
[[pl:Portfolio]]
[[pt:Portfólio]]
[[ru:Портфолио]]
[[uk:Портфоліо]]
[[zh:公文包]]</li><li>[[Trident|Trident]]<br/>{{For|the Hidden Depths DLC weapon in ''Minecraft Dungeons''|MCD:Trident}}
{{ItemEntity
|durability= 250
|renewable= Yes
|stackable= No
|size=Height: 0.25 Blocks<br>Width: 0.25 Blocks
|title=Trident|image= <gallery>
Trident (item).png | Item
Trident.png | Entity
</gallery>}}
A '''trident''' is a [[weapon]] used in both melee and ranged combat and is a rare drop from [[drowned]].
==Obtaining==
Tridents are not craftable. A trident can be obtained only when dropped by a [[drowned]], Converted drowned are never equipped with tridents.
===Mob loot===
==== '''''Java Edition''''' ====
6.25% (or 1 in 16) of [[Drowned]] in Java Edition spawn with a trident of random durability as their natural weapon. They have an 8.5% chance to drop their trident when killed by a player. The chance is increased by 1% for each level of [[Looting]] up to a max of 11.5% with Looting III. This means the overall chance of obtaining a trident from any given drowned is 0.53125% (about 1 in 188) or 0.71875% with looting III.
{{IN|Java}}, a trident held by a drowned has a chance to be enchanted, but the trident's enchantments have no effects for drowned.<ref>{{bug|MC-127321}}</ref>
==== '''''Bedrock Edition''''' ====
Only 15% (or 3 in 20) of [[Drowned]] in Bedrock Edition spawn with tridents. Of these, they have a 25% chance to drop their trident when killed by a player. This chance is increased by 4% for each level of looting up to a max of 37% with looting III. This means the overall chance of obtaining a trident from any given drowned is 3.75% (or 3 in 80) or 5.55% with looting III.
===Thrown tridents===
Tridents thrown onto the ground by a player can be picked up; however, tridents thrown by [[drowned]] cannot be picked up, similar to arrows shot by [[skeleton]]s, [[stray]]s, and [[pillager]]s. Only the owner of a trident thrown in Creative mode or enchanted with Loyalty can pick it up; other players in Creative and players in Survival mode including its own owner can't pick up the trident thrown in Creative.
===Trading===
Drowned who are holding tridents will sometimes drop their trident at full durability if given a nautilus shell when they aren't attacking anything.{{only|BE}}
==Usage==
===Drowned===
{{main|Drowned}}
15% of drowned {{in|bedrock}}, and 6.25% {{in|java}}, spawn with a trident as its natural weapon. It throws the trident at its opponent every 1.5 seconds, dealing {{hp|9}} [[damage]] in normal difficulty. A drowned can throw unlimited tridents, and these tridents cannot be picked up by the [[player]].
A [[villager]] can be turned into a [[zombie villager]] if it is killed by a trident thrown by a drowned: the chance of conversion is 0% on Easy [[difficulty]], 50% on Normal, and 100% on Hard and [[Hardcore]].
{{IN|bedrock}}, a drowned can use the trident's melee attack if its target is within three blocks. The melee attack deals {{hp|9}} damage.
===Melee attack===
Pressing {{control|attack}} while holding a trident deals damage to both [[mob]]s and players. Tridents deal {{hp|9}} melee damage. A successful hit consumes durability of the trident.
===Ranged attack===
[[File:Steve aiming with Trident.png|150px]] [[File:Alex aiming with Trident.png|150px]]
Pressing and holding {{control|use}} while holding a trident charges it. When released at full charge, the trident is thrown and deals damage to any [[entity]] it hits. It flies on a ballistic trajectory similar to that of an [[arrow]], but at 80% strength. If the trident hits a block, it sticks to the block. If it hits an entity, it bounces off the entity and lands nearby. It is also blocked by [[shield]]s and can be retrieved once it lands in the ground. Thrown tridents can trigger wooden [[button]]s, wooden [[pressure plate]]s, and [[target]] blocks. A trident can be thrown at a [[chorus flower]] or [[pointed dripstone]] to break it, which causes the block to be dropped as its respective item.
{{IN|bedrock}} and [[Java Edition Combat Test 4]], tridents can be shot by [[dispenser]]s regardless of enchantment.
Tridents [[Enchanting#Summary_of_enchantments_by_item|enchanted]] with [[Loyalty]] return to the thrower after hitting an entity{{only|java}}/hitting and bouncing off an entity then hitting a block{{only|bedrock}}<ref>{{bug|MCPE-51726}}</ref> or just a block. A Loyalty-enchanted trident fired from a [[dispenser]] just sticks to the block it strikes. Higher levels of enchantment result in shorter recovery times. {{IN|java}}, throwing a trident enchanted with Loyalty into the [[void]] destroys it,<ref>{{bug|MC-125755|||WAI}}</ref> while {{in|bedrock}} it automatically returns to the player. Tridents (if enchanted with Loyalty), can take [[fire]] damage but still return to the player if thrown in [[lava]]. This is especially helpful in [[the Nether]] should the [[player]] be using a trident instead of a [[bow]]. If a trident enchanted with Loyalty attempts to return to a player with no available inventory space, the trident floats near the player until inventory space becomes available.
Thrown tridents take 1 durability damage, regardless of whether it hit an entity or not. Tridents with 1 durability remaining cannot be thrown.
Tridents enchanted with [[Riptide]] launch the player a certain distance when thrown, with the distance increasing for higher enchantment levels. They can be thrown only if the player is standing in [[water]], or if it is raining on the block they are standing on. If the player charges it but walks into a nearby dry area, the charge is canceled. If the player throws a Riptide trident and collides with a mob, the mob takes melee damage (including critical damage if the player is falling). {{IN|java}} tridents enchanted with Riptide take one durability damage upon throwing, and lose an additional 1 durability if it collides with an entity on both editions. Each level of Riptide increases the distance traveled by six blocks. The enchantment at level one launches the player nine blocks, fifteen blocks at level two, and twenty-one blocks at level three.
Tridents enchanted with [[Channeling]] summon a lightning bolt if there is a thunderstorm, although only upon hitting a mob or player standing in the rain as well as a [[Lightning Rod|lightning rod]] placed in the rain.
Unlike other projectiles, the trident does not slow down when thrown through water or lava.
{{IN|java}}, the [[Impaling]] enchantment affects ''all water mobs''. {{IN|bedrock}}, it deals extra damage to [[player]]s and mobs in water or rain.
Unlike arrows, thrown tridents do not despawn.{{only|bedrock}} Tridents despawn after 60 seconds if they are not picked up.{{only|java}}<ref>{{bug|MC-125817}}</ref>
;Magical damage
Using [[Riptide]], nearby players or mobs are dealt [[Harming|splash damage]] within an 8.25×8.25×4.25 cubical area. It stacks with the [[Impaling]] enchantment and [[Strength]] effect. Critical hits do not increase splash damage, but affect the target.
{{IN|bedrock}}, thrown tridents can damage the [[ender dragon]] while resting on the bedrock fountain. {{IN|java}}, they act just like arrows — deflected, but burn as if they had [[Flame]].
=== Damage===
Thrown tridents and splashes deal {{hp|8}} damage. The damage remains the same regardless of the trident's speed. It has a faster charging speed than a [[bow]] or [[crossbow]] (barring the [[Quick Charge]] enchantment.)
====Java Edition====
{{IN|java}}, tridents have an attack speed of 1.1 and take ~0.91 seconds to [[Damage#Attack cooldown|recover]].
{| class="wikitable" style="text-align:center" data-description="Sword attack damage by type"
!Attack
!{{ItemSprite|Trident|text=Melee}}
!{{ItemSprite|Trident|text=Melee (critical)}}
!{{ItemSprite|Trident|text=Range}}
|-
!Attack damage
|{{hp|9}}
|{{hp|13.5}}
|{{hp|8}}
|-
!Damage/Second (DPS)<ref group="note">This does not take travel time into account</ref>
|9.9
|14.3
| ?
|-
!Lifetime damage inflicted<ref group="note">The formula to find the total lifetime damage is ''Durability × Damage per hit = Lifetime damage minimum'' (e.g., 250 × 9 = 2250). It ignores enchantments and critical hits, and assumes the trident is at maximum charge</ref>
|{{hp|2250}}
|{{hp|3375}}
|{{hp|2000}}
|-
!Durability
| colspan="3" |250
|}
{{notelist}}
====Bedrock Edition====
{{IN|bedrock}}, tridents have no attack cooldown and do the following damage:
{| class="wikitable" style="text-align:center" data-description="Sword attack damage by type"
!Attack
!{{ItemSprite|Trident|text=Melee}}
!{{ItemSprite|Trident|text=Range}}
|-
!Attack damage
|{{hp|9}}
|{{hp|8}}
|-
! ''Lifetime damage inflicted''<ref group="note">The formula to find the total lifetime damage is ''Durability × Damage per hit = Lifetime damage minimum''. It excludes enchantments and critical hits.</ref>
|{{hp|2259}}
|{{hp|2008}}
|-
!Durability
| colspan="2" |251
|}
{{notelist}}
===Elytra===
A trident with the [[Riptide]] enchantment can be used to propel a player with a pair of [[elytra]], but only in [[rain]]y weather, during snowy weather in certain biomes<ref>{{bug|MC-128169}}</ref> or while the [[player]] is in a body of water. A Riptide trident can boost the player to speeds as high as 125 blocks per second,<ref>{{bug|MC-147173||Using riptide tridents while elytra flying can boost the player to excessive speeds}}</ref> much faster than the 33.5 blocks-per-second speed achievable using [[firework rocket]]s.
===Impaling damage ===
{{IN|java}}, the [[Impaling]] enchantment deals extra damage to all water mobs. {{IN|bedrock}} and in [[Java Edition Combat Test 3]], it deals extra damage to all players and mobs in water or rain.
{| class="wikitable" style="text-align:center" data-description="Trident Damage by Impaling Level" |
|+ Trident Damage by Impaling level
|-
!Level
!Increase
!Melee
!Ranged
|-
|I
| adds {{hp|2.5}}
|{{hp|11.5}}
|{{hp|10.5}}
|-
|II
|adds {{hp|5}}
|{{hp|14}}
|{{hp|13}}
|-
|III
| adds {{hp|7.5}}
|{{hp|16.5}}
|{{hp|15.5}}
|-
|IV
|adds {{hp|10}}
|{{hp|19}}
|{{hp|18}}
|-
|V
|adds {{hp|12.5}}
|{{hp|21.5}}
|{{hp|20.5}}
|}
{{-}}
===Enchantments===
Tridents have a base enchantability of 1 and can receive the following [[enchantment]]s:
{| class="wikitable col-2-center col-3-right"
|+
!Name
!Max Level
![[Enchanting|Method]]
|-
|[[Loyalty]]<ref group="note" name="note1">Loyalty and Channeling are mutually exclusive from Riptide, but not from each other.</ref>
|III
|{{Inventory slot|Enchanting Table}}{{Inventory slot|Anvil}}
|-
|[[Channeling]]<ref group="note" name="note1" />
|I
|{{Inventory slot|Enchanting Table}}{{Inventory slot|Anvil}}
|-
|[[Riptide]]<ref group="note" name="note1" />
|III
|{{Inventory slot|Enchanting Table}}{{Inventory slot|Anvil}}
|-
|[[Impaling]]
|V
|{{Inventory slot|Enchanting Table}}{{Inventory slot|Anvil}}
|-
|[[Unbreaking]]
|III
|{{Inventory slot|Enchanting Table}}{{Inventory slot|Anvil}}
|-
|[[Mending]]
|I
|{{Inventory slot|Anvil}}
|-
|[[Curse of Vanishing]]
|I
|{{Inventory slot|Anvil}}
|}
; Notes
<references group="note" />
===Repairing ===
Tridents have the same [[durability]] as an [[sword|iron sword]]. Whenever a trident deals damage, its durability decreases by 1.
Tridents can be repaired by:
*combining two damaged tridents in a [[grindstone]], or on a [[crafting table]] or the 2×2 inventory grid, which removes any enchantments except for [[Curse of Vanishing]] and [[Curse of Binding]]
*combining a damaged trident with another trident on an [[anvil]], which preserves enchantments.
*applying the [[Mending]] enchantment.
==Sounds==
{{Edition|Java}}:<br>
Thrown tridents use the Friendly Creatures sound category for entity-dependent sound events.
{{Sound table
|sound=Trident pierce1.ogg
|sound2=Trident pierce2.ogg
|sound3=Trident pierce3.ogg
|subtitle=Trident stabs
|source=neutral
|description=When a trident hits a mob
|id=item.trident.hit
|translationkey=subtitles.item.trident.hit
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|sound=Trident ground impact1.ogg
|sound2=Trident ground impact2.ogg
|sound3=Trident ground impact3.ogg
|sound4=Trident ground impact4.ogg
|subtitle=Trident vibrates
|source=neutral
|description=When a trident hits the ground
|id=item.trident.hit_ground
|translationkey=subtitles.item.trident.hit_ground
|volume=0.9
|pitch={{frac|12|11}}-{{frac|4|3}}
|distance=16}}
{{Sound table
|sound=Trident throw1.ogg
|sound2=Trident throw2.ogg
|subtitle=Trident clangs
|source=player
|description=When a player throws a trident
|id=item.trident.throw
|translationkey=subtitles.item.trident.throw
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|rowspan=2
|sound=Trident thunder1.ogg
|sound2=Trident thunder2.ogg
|subtitle=Trident thunder cracks
|source=neutral
|description=When a Channeling trident hits a mob
|id=item.trident.thunder
|translationkey=subtitles.item.trident.thunder
|volume=5.0
|pitch=1.0
|distance=16}}
{{Sound table
|subtitle=Trident thunder cracks
|source=weather
|description=When a trident with Channeling strikes a lightning rod
|id=item.trident.thunder
|translationkey=subtitles.item.trident.thunder
|volume=5.0
|pitch=1.0
|distance=16}}
{{Sound table
|sound=Riptide I.ogg
|subtitle=Trident zooms
|source=player
|description=When a Riptide I trident is used
|id=item.trident.riptide_1
|translationkey=subtitles.item.trident.riptide
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|sound=Riptide II.ogg
|subtitle=Trident zooms
|source=player
|description=When a Riptide II trident is used
|id=item.trident.riptide_2
|translationkey=subtitles.item.trident.riptide
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|sound=Riptide III.ogg
|subtitle=Trident zooms
|source=player
|description=When a Riptide III or higher trident is used
|id=item.trident.riptide_3
|translationkey=subtitles.item.trident.riptide
|volume=1.0
|pitch=1.0
|distance=16}}
{{Sound table
|sound=Trident return1.ogg
|sound2=Trident return2.ogg
|sound3=Trident return3.ogg
|subtitle=Trident returns
|source=neutral
|description=When a trident starts returning <ref group=sound>The first sound is only played {{frac|1|9}} of the time, while the others are played {{frac|4|9}} of the time</ref>
|id=item.trident.return
|translationkey=subtitles.item.trident.return
|volume=8.0
|pitch=''varies'' <ref group=sound>1.0 for <code>return1</code>, 1.0/0.8/1.2/1.2 for <code>return2</code>, and 1.0/0.8/0.8/1.2 for <code>return3</code></ref>
|distance=16}}
{{Sound table
|sound=Trident throw1.ogg
|sound2=Trident throw2.ogg
|subtitle=Drowned throws Trident
|source=hostile
|description=When a drowned shoots a trident
|id=entity.drowned.shoot
|translationkey=subtitles.entity.drowned.shoot
|volume=1.0
|pitch={{frac|5|6}}-1.25
|distance=16}}
{{Sound table
|sound=Random break.ogg
|subtitle=Item breaks
|source=player
|description=When a trident's durability is exhausted
|id=entity.item.break
|translationkey=subtitles.entity.item.break
|volume=0.8
|pitch=0.8-1.2
|distance=16
|foot=1}}
{{Edition|Bedrock}}:
{{Sound table
|type=bedrock
|sound=Trident pierce1.ogg
|sound2=Trident pierce2.ogg
|sound3=Trident pierce3.ogg
|source=player
|description=When a trident hits a mob
|id=item.trident.hit
|volume=1.0
|pitch=1.0}}
{{Sound table
|sound=Trident ground impact1.ogg
|sound2=Trident ground impact2.ogg
|sound3=Trident ground impact3.ogg
|sound4=Trident ground impact4.ogg
|source=player
|description=When a trident hits the ground
|id=item.trident.hit_ground
|volume=0.9
|pitch=1.0}}
{{Sound table
|sound=Trident throw1.ogg
|sound2=Trident throw2.ogg
|source=player
|description=When a player throws a trident
|id=item.trident.throw
|volume=1.0
|pitch=1.0}}
{{Sound table
|sound=Trident thunder1.ogg
|sound2=Trident thunder2.ogg
|source=player
|description=When a trident with Channeling strikes a mob<ref group="sound">{{Bug|MCPE-43402}}</ref><wbr><ref group=sound>{{bug|MCPE-173931||Tridents don't make channeling sounds when striking a lightning rod}}</ref><wbr>{{Upcoming|BE 1.20.30}}
|id=item.trident.thunder
|volume=1.0<wbr>{{Until|BE 1.20.30}}<br>1000.0<wbr>{{Upcoming|BE 1.20.30}}
|pitch=1.0}}
{{Sound table
|sound=Riptide I.ogg
|source=player
|description=When a Riptide I trident is used
|id=item.trident.riptide_1
|volume=1.0
|pitch=1.0}}
{{Sound table
|sound=Riptide II.ogg
|source=player
|description=When a Riptide II trident is used
|id=item.trident.riptide_2
|volume=1.0
|pitch=1.0}}
{{Sound table
|sound=Riptide III.ogg
|source=player
|description=When a Riptide III trident is used
|id=item.trident.riptide_3
|volume=1.0
|pitch=1.0}}
{{Sound table
|sound=Trident return1.ogg
|sound2=Trident return2.ogg
|sound3=Trident return3.ogg
|source=player
|description=When a trident starts returning <ref group=sound>The first sound is only played {{frac|1|9}} of the time, while the others are played {{frac|4|9}} of the time</ref>
|id=item.trident.return
|volume=8.0
|pitch=''varies'' <ref group=sound>1.0 for <code>return1</code>, 1.0/0.8/1.2/1.2 for <code>return2</code>, and 1.0/0.8/0.8/1.2 for <code>return3</code></ref>}}
{{Sound table
|sound=Trident throw1.ogg
|sound2=Trident throw2.ogg
|source=hostile
|description=When a drowned shoots a trident<ref group="sound">{{Bug|MCPE-53297}}</ref><wbr>{{Upcoming|BE 1.20.30}}
|id=mob.drowned.shoot
|volume=1.0
|pitch=0.8-1.2
|foot=1}}
==Data values==
===ID===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Trident
|spritetype=item
|nameid=trident
|form=item
|foot=1}}
{{ID table
|edition=java
|showentitytags=y
|generatetranslationkeys=y
|displayname=Trident
|spritetype=entity
|nameid=trident
|entitytags=impact_projectiles
|foot=1}}
{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Trident
|spritetype=item
|nameid=trident
|id=546
|form=item
|foot=1}}
{{ID table
|edition=bedrock
|shownumericids=y
|generatetranslationkeys=y
|displayname=Trident
|spritetype=entity
|nameid=thrown_trident
|id=73
|foot=1}}
===Entity data ===
Tridents have entity data associated with them that contain various properties of the entity.
{{el|java}}:
{{main|Entity format}}
{{/ED}}
{{el|bedrock}}:
:See [[Bedrock Edition level format/Entity format]].
==Achievements==
{{load achievements|Do a Barrel Roll!;Bullseye}}
==Advancements==
{{load advancements|A Throwaway Joke;Very Very Frightening;Not Today;Sniper Duel;Bullseye}}
==History==
{{History|java}}
{{History||November 18, 2017|link={{YouTubeLink|mAapz_nIC_Y}}|A trident was shown killing a [[zombie]] in a clip presented at [[MineCon Earth]].}}
{{History||1.13|snap=18w07a|[[File:Trident.png|60px]] {{InvSprite|Trident Revision 1}} Added tridents, which are currently unobtainable in [[Survival]].}}
{{History|||snap=18w10a|[[File:Trident (item).png|32px]] Tridents now have a new texture in the [[inventory]].}}
{{History|||snap=18w11a|Added [[drowned]] mobs, which can spawn with a trident, allowing tridents to now become obtainable in [[Survival]].}}
{{History|||snap=18w14a|If the [[player]] is not in [[water]] and it is not [[rain]]ing, the player can no longer throw tridents [[enchantment|enchanted]] with [[Riptide]], but they can still deal melee [[damage]].}}
{{History|||snap=18w20a|Like with swords, tridents no longer can break blocks when held in [[Creative]] mode.<ref>{{bug|MC-126300}}</ref>}}
{{History||1.14|snap=18w43a|Thrown tridents can now break [[chorus flower]]s.}}
{{History||1.15|snap=19w39a|[[File:Enchanted Trident.png|60px]] [[File:Enchanted Trident (item).gif|32px]] Tridents that are [[enchanting|enchanted]] now have a glint.
|Trident items use a 3D model again. When dropped, it rotates off center<ref>{{bug|MC-161886}}</ref> (like with beds at the time and shields currently).}}
{{History|||snap=19w42a|Trident items now use the 2D sprite again.<ref>{{bug|MC-161872}}</ref>}}
{{History||1.17|snap=20w48a|Thrown tridents can now break [[pointed dripstone]].}}
{{History|upcoming java}}
{{History||Villager Trade Rebalance<br>(Experimental)|link=Java Edition 1.20.2|snap=23w31a|Trident-exclusive enchantments are no longer obtainable from villager [[trading]].}}
{{History||Combat Tests|snap=1.14.3 - Combat Test|The attack speed of tridents has been increased to 2.
|The base [[damage]] of tridents has been decreased from {{hp|9}} to {{hp|7}}.
|The attack reach of tridents has been increased to 4 [[block]]s.}}
{{History|||snap=Combat Test 2|The damage of tridents has been increased to {{hp|8}}.}}
{{History|||snap=Combat Test 4|Tridents can now be shot from [[dispenser]]s.
|Tridents with [[Loyalty]] that fall into the [[void]] now return to their owner upon breaking in the void.
|Tridents with [[Impaling]] now deal [[enchanting|enchantment]] damage to all [[mob]]s that are in [[water]] or [[rain]].}}
{{History|||snap=Combat Test 5|The damage of tridents has been decreased to {{hp|7}} again.}}
{{History|bedrock}}
{{History||1.4.0|snap=beta 1.2.13.8|[[File:Trident.png|60px]] [[File:Trident (item).png|32px]] Added tridents.
|Tridents are currently a part of [[Experimental Gameplay]].}}
{{History|||snap=beta 1.2.14.2|Tridents have been fully implemented.}}
{{History|||snap=beta 1.2.20.1|A new animation has been added for tridents with [[Riptide]] when they are thrown.}}
{{History||1.5.0|snap=beta 1.5.0.0|Tridents can now be [[enchantment|enchanted]] with [[Mending]] and [[Unbreaking]].}}
{{History|||snap=beta 1.5.0.7|Tridents no longer break [[block]]s in [[Creative]] mode.}}
{{History||1.10.0|snap=beta 1.10.0.3|Thrown tridents can now break [[chorus flower]]s.}}
{{History||1.16.0|snap=beta 1.15.0.51|Drowned can no longer have a trident when converted.|Drowned that are not holding a trident are no longer able to drop one.}}
{{History||1.16.220|snap=beta 1.16.220.50|Tridents are now able to break pointed dripstone.}}
{{History|||snap=beta 1.16.220.51|Drowned now hold their tridents correctly when targeting a player.}}
{{History|console}}
{{History||xbox=TU69|ps=1.76|wiiu=Patch 38|[[File:Trident.png|60px]] [[File:Trident (item).png|32px]] Added tridents.}}
{{History|education}}
{{History||1.4.0|[[File:Trident.png|60px]] [[File:Trident (item).png|32px]] Added tridents.}}
{{History|foot}}
==Issues==
{{issue list}}
==Trivia==
* If a player throws a Loyalty-enchanted trident and the player's inventory subsequently fills, the trident hovers around or through the player's skin until an inventory slot opens, which it fills immediately. Multiple tridents can be 'queued' to re-enter the player's inventory in this manner.
*{{IN|java}} in Creative mode, sword enchantments can be applied to tridents. This includes Sharpness, Fire Aspect, and Looting. Sharpness, Smite, and Bane of Arthropods increases their damage against their specific mobs, as well.{{more info needed|Does the damage also increase when the trident is thrown?}}
*Thrown tridents pass through [[Nether Portal (block)|nether portal block]]s without being transported to [[the Nether]] or the [[Overworld]].
*Using a trident enchanted with Riptide while riding an entity cancels the charge and does nothing.
==Gallery==
<gallery>
TridentMineconEarth.jpg|Tridents are shown in a clip of Minecon Earth 2017.
Returning trident.jpg|A trident [[enchantment|enchanted]] with [[Loyalty]] returning to the [[player]].
Riptide Trident.png|A player "flying" high in the [[air]] after throwing a trident enchanted with [[Riptide]] III vertically upward.
Trident in ground.png|A trident stuck in [[sand]].
Two-hand drowned.png|A drowned holding a trident and a [[nautilus shell]].
Enchanted Trident (item).gif|An enchanted trident.
Alex with Trident.png|An official T-Shirt design of [[Alex]] with a trident.
Acid Drowned.png|"Acid Drowned," an officially licensed T-Shirt featuring a [[drowned]] with a trident.
ArgoMajor Trident.jpg|First image of a trident in ''Bedrock Edition''.
</gallery>
==References==
{{reflist}}
==External Links==
*[https://www.minecraft.net/en-us/article/taking-inventory--trident Taking Inventory: Trident] – Minecraft.net on January 30, 2020
{{Items}}
{{Entities}}
[[Category:Combat]]
[[de:Dreizack]]
[[es:Tridente]]
[[fr:Trident]]
[[ja:トライデント]]
[[ko:삼지창]]
[[pl:Trójząb]]
[[pt:Tridente]]
[[ru:Трезубец]]
[[th:ตรีศูล]]
[[zh:三叉戟]]</li></ul> | 13w04a | Added scoreboard. | |||||||||||||||||||||||||||||||||
| 13w05a | Added team-based functionality. | ||||||||||||||||||||||||||||||||||
1.7
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
| 13w36a | Added statistic-based objective criteria. | |||||||||||||||||||||||||||||||||
| u | |||||||||||||||||||||||||||||||||||
1.8{{Extension DPL}}<ul><li>[[Amethyst Shard|Amethyst Shard]]<br/>{{Item
| title = Amethyst Shard
| image = Amethyst Shard.png
| renewable = Yes
| stackable = Yes (64)
}}
An '''amethyst shard''' is a crystal obtained from mining a fully grown [[amethyst cluster]] or can be obtained from chests in [[Ancient City|ancient cities]].
== Obtaining ==
=== Mining ===
An [[amethyst cluster]] mined using a non-[[Silk Touch]], non-[[Fortune]] [[pickaxe]] drops 4 amethyst shards. When mined using any other tool, [[item]] or mechanism (such as [[explosion]]s or [[piston]]s) it drops 2 shards. The maximum amount of amethyst shards dropped can be increased with Fortune. Fortune I gives a {{frac|1|3}} chance for eight shards, averaging 5.33 shards; Fortune II gives a 25% chance (each) to give eight or 12 shards, averaging 7 shards, and Fortune III gives a 20% chance (each) to give 8, 12, or 16 shards, averaging 8.8 shards.
If the amethyst cluster in any of its growth stages is mined using a pickaxe enchanted with [[Silk Touch]], it drops itself rather than amethyst shards.
=== Chest loot ===
{{LootChestItem|amethyst-shard}}
== Usage ==
=== Crafting ingredient ===
{{Crafting usage}}
=== Smithing ingredient ===
{{Smithing
|head=1
|ingredients=Any Armor Trim +<br/>Any Armor Piece + <br/>Amethyst Shard
|Any Armor Trim Smithing Template
|Netherite Chestplate
|Amethyst Shard
|Amethyst 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|amethyst shard}}
=== Allay duplication ===
If an amethyst shard is given to an [[allay]] that is currently dancing to an active [[jukebox]], the allay emits heart particles, consumes the amethyst shard and duplicates into another allay. After this, there is a 5 minute cool down until both allays can be duplicated like this again.
== Sounds ==
{{Edition|Java}}:
{{Sound table
|sound=Amethyst shimmer.ogg
|subtitle=Amethyst chimes
|source=neutral
|description=When an amethyst shard duplicates an allay
|id=block.amethyst_block.chime
|translationkey=subtitles.block.amethyst_block.chime
|volume=0.4
|pitch=1.0
|distance=16
|foot=1}}
{{Edition|Bedrock}}:
{{Sound table
|type=bedrock
|sound=Amethyst shimmer.ogg
|source=block
|description=When an amethyst shard duplicates an allay
|id=chime.amethyst_block
|volume=1.0
|pitch=0.5-1.7
|foot=1}}
== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Amethyst Shard
|spritetype=item
|nameid=amethyst_shard
|form=item
|foot=1}}
{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Amethyst Shard
|spritetype=item
|nameid=amethyst_shard
|form=item
|id=625
|foot=1}}
==History==
{{History||October 3, 2020|link={{ytl|DBvZ2Iqmm3M|t=23m14s}}|Amethyst shards are mentioned, but not shown at [[Minecraft Live 2020]].}}
{{History|java}}
{{History||1.17|snap=20w45a|[[File:Amethyst Shard JE1.png|32px]] Added amethyst shards.}}
{{History|||snap=20w46a|[[File:Amethyst Shard JE2 BE1.png|32px]] The texture for amethyst shards has changed.}}
{{History||1.19|snap=22w13a|Amethyst shards can now be found in [[ancient city]] [[chest]]s.}}
{{History||1.19.1|snap=22w24a|Amethyst shards can now be used to duplicate [[allay]]s.}}
{{History||1.20<br>(Experimental)|link=1.19.4|snap=23w04a|Amethyst shards can now be used as an armor trim material.}}
{{History||1.20|snap=23w12a|Amethyst shards can now be used to craft [[calibrated sculk sensor]]s.}}
{{History|bedrock}}
{{History||1.17.0|snap=beta 1.17.0.50|[[File:Amethyst Shard JE2 BE1.png|32px]] Added amethyst shards.}}
{{History|||snap=beta 1.17.0.52|Amethyst shards are now available without enabling [[Experimental Gameplay]].}}
{{History||1.19.0|snap=beta 1.19.0.26|Amethyst shards can now be found in [[ancient city]] [[chest]]s.}}
{{History||1.19.10|snap=beta 1.19.10.22|Amethyst shards can now be used to duplicate allays.}}
{{History||1.20.0<br>(Experimental)|link=Bedrock Edition 1.19.80|snap=beta 1.19.80.21|Amethyst shards can now be used as an armor trim material.}}
{{History|||snap=beta 1.19.80.22|Amethyst shards can now be used to craft calibrated sculk sensors.}}
{{History|foot}}
==Issues==
{{issue list}}
==Trivia==
* Although in real life {{w|amethyst}} is a variety of {{w|quartz}} like [[Nether Quartz|nether quartz]], the two resources are not interchangeable.
== External Links ==
*[https://www.minecraft.net/en-us/article/taking-inventory--amethyst-shard Taking Inventory: Amethyst Shard] – Minecraft.net on May 20, 2021
{{Items}}
[[Category:Renewable resources]]
[[de:Amethystscherbe]]
[[es:Fragmento de amatista]]
[[fr:Éclat d'améthyste]]
[[it:Scheggia di ametista]]
[[ja:アメジストの欠片]]
[[lzh:紫水玉片]]
[[pl:Odłamek ametystu]]
[[pt:Fragmento de ametista]]
[[ru:Осколок аметиста]]
[[uk:Уламок аметисту]]
[[zh:紫水晶碎片]]</li><li>[[Gold Ingot|Gold Ingot]]<br/>{{About|the item|the ore|Gold Ore|the mineral block|Block of Gold|the nugget|Gold Nugget}}
{{Item
| image = Gold Ingot.png
| renewable = Yes
| stackable = Yes (64)
}}
A '''gold ingot''' is a [[metal]] ingot used to craft various [[item]]s, and also used as currency for [[bartering]] with [[piglin]]s.
== Obtaining ==
Gold ingots are mainly obtained by smelting [[raw gold]], [[gold ore]] and [[nether gold ore]], or just mining nether gold ore, dropping gold nuggets. Gold generates more frequently in [[badlands]] biomes.
=== Crafting ===
{{Crafting
|head=1
|showname=0
|Block of Gold
|Output=Gold Ingot,9
|type=Material
}}
{{Crafting
|A1= Gold Nugget
|B1= Gold Nugget
|C1= Gold Nugget
|A2= Gold Nugget
|B2= Gold Nugget
|C2= Gold Nugget
|A3= Gold Nugget
|B3= Gold Nugget
|C3= Gold Nugget
|Output= Gold Ingot
|type= Material
|foot=1
}}
=== Smelting ===
{{see also|Gold Ore#Natural generation}}
{{Smelting
|head=1
|Gold Ore;Nether Gold Ore;Deepslate Gold Ore
|Gold Ingot
|1
}}
{{Smelting
|foot=1
|Raw Gold
|Gold Ingot
|1
}}
=== Mob loot ===
[[Zombified piglin]]s have a 2.5% ({{frac|1|40}}) chance of dropping a gold ingot if killed by a player or tamed wolf. The chance is increased by 1% per level of [[Looting]], for a maximum of 5.5% with Looting III.
=== Chest loot ===
{{LootChestItem|gold-ingot}}
== Usage ==
=== Crafting ingredient===
As a material for weapons, tools, and armor, gold is not a straight upgrade from iron (except in the case of [[Horse Armor|horse armor]]). Gold has a higher mining speed and enchantability than any other material, but attack power and durability is less.
{{crafting usage}}
=== Trading ===
Apprentice-level cleric [[Villager|villagers]] buy 3 gold ingots for an [[emerald]] as part of their trade.
=== Repairing ===
Golden [[helmet]]s, [[chestplate]]s, [[leggings]], [[boots]], [[sword]]s, [[pickaxe]]s, [[axe]]s, [[hoe]]s and [[shovel]]s can be [[item repair|repaired]] with gold ingots in an [[anvil]].
=== Bartering ===
{{main|Bartering}}
[[Piglin]]s throw the player [[Bartering#Mechanics|item(s)]] if the player throws or {{ctrl|uses}} a gold ingot on them.
=== Beacons ===
Gold ingots can be used to select powers from a [[beacon]]. The player must select one of the available powers, and then insert an ingot in the item slot.
A gold ingot can be substituted for an [[iron ingot]] or [[netherite ingot]], an [[emerald]], or a [[diamond]].
=== Smithing ingredient ===
{{Smithing
|head=1
|ingredients=Any Armor Trim +<br/>Any Armor Piece + <br/>Gold Ingot
|Any Armor Trim Smithing Template
|Netherite Chestplate
|Gold Ingot
|Gold 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 palettes are shown on the designs on trimmed armor:
*{{TrimPalette|gold ingot}}
*{{TrimPalette|gold ingot|darker=1}} (a darker color palette is used when a golden armor piece is trimmed using a gold ingot).
== Achievements ==
{{load achievements|Oooh, shiny!}}
== Advancements ==
{{load advancements|Oh Shiny}}
== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showitemtags=y
|showforms=y
|generatetranslationkeys=y
|displayname=Gold Ingot
|spritetype=item
|nameid=gold_ingot
|itemtags=beacon_payment_items, piglin_loved
|form=item
|foot=1}}
{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Gold Ingot
|spritetype=item
|nameid=gold_ingot
|id=306
|form=item
|foot=1}}
== History ==
{{History|java indev}}
{{History||0.31|snap=20100128|[[File:Gold Ingot JE1.png|32px]] Added gold ingots.}}
{{History|||snap=20100129|[[File:Gold Ingot JE2 BE1.png|32px]] The texture of gold ingots has been changed.
|Gold ingots can be [[smelting|smelted]] from [[gold ore]] with [[flint and steel]] and [[drops|drop]] 3-5 gold ingots.
|Gold ingots can be used to craft [[gold block]]s.
|[[Gold block]]s now require 9 gold ingots (3×3) instead of 4 (2×2) to be [[crafting|crafted]], making them much more expensive.}}
{{History|||snap=20100130|Gold ingots can now be used to craft gold [[sword]]s, [[shovel]]s, [[pickaxe]]s and [[axe]]s.}}
{{History||20100206|Gold ingots are now used to [[crafting|craft]] gold [[hoe]]s.}}
{{History||?|Smelting gold ore now drops 1 gold ingot (down from 3-5).}}
{{History||20100218|Gold ingots are now used to craft gold [[helmet]]s, [[chestplate]]s, [[leggings]] and [[boots]].}}
{{history|java alpha}}
{{History||v1.2.0|snap=<nowiki>?|slink=:Category:Information needed requiring unarchived version|Gold ingots are now used to craft [[clock]]s.}}
{{History|java beta}}
{{History||1.5|Gold ingots are now used to craft [[powered rail]]s.}}
{{History||1.8|snap=Pre-release|Gold ingots can now be found in the new [[stronghold]] storerooms and [[mineshaft]] [[chest]]s.}}
{{History|java}}
{{History||1.0.0|snap=Beta 1.9 Prerelease|Gold ingots can be crafted from [[gold nuggets]], which are dropped by [[Zombified Piglin|zombie pigmen]], making gold a [[renewable resource]].}}
{{History|||snap=Beta 1.9 Prerelease 3|Gold ingots can now be found in the new [[stronghold]] altar [[chest]]s.}}
{{History|||snap=Beta 1.9 Prerelease 4|Gold ingots are now used to craft [[gold nugget]]s.}}
{{History||1.1|snap=12w01a|Gold ingots can now be found in [[village]] blacksmith chests.}}
{{History||1.2.1|snap=12w06a|Zombie pigmen now rarely drop gold ingots.}}
{{History||1.3.1|snap=12w21a|Added [[desert temple]]s, with a hidden [[chest]] room and loot containing gold ingots.
|All types of [[villager]]s now [[trading|buy]] 8–9 gold ingots for 1 [[emerald]], as a fallback trade in case no trades were generated for that villager.}}
{{History|||snap=12w22a|Added [[jungle temple]]s, which contain loot chests with gold ingots.}}
{{History||1.5|snap=13w01a|Gold ingots are now used to craft light [[weighted pressure plate]]s.}}
{{History||1.6.1|snap=13w16a|Gold ingot is now used to craft golden [[horse armor]].}}
{{History|||snap=13w18a|Gold ingot is no longer used to craft golden [[horse armor]].|Gold ingots are now found in [[nether fortress]] [[chest]]s.}}
{{History|||snap=13w23a|Gold ingots are now used to craft normal [[golden apple]]s.}}
{{History||1.8|snap=14w02a|[[Trading]] has been changed: only cleric [[villager]]s now [[trading|buy]] 8–10 gold ingots for 1 [[emerald]], as a legitimate trade.}}
{{History||1.9|snap=15w31a|Gold ingots can now be found in [[end city]] [[chest]]s.}}
{{History|||snap=15w43a|The average yield of gold ingots in [[nether fortress]] chest has been decreased.}}
{{History|||snap=15w44a|The average yield of gold ingots in [[mineshaft]] and [[desert temple]] chests has been decreased.
|Gold ingots have been added to [[dungeon]] [[chest]]s.}}
{{History||1.11|snap=16w39a|Gold ingots are now found in the new [[woodland mansion]] chests.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 266.}}
{{History|||snap=18w10a|Gold ingots now generate in [[buried treasure]] chests.}}
{{History|||snap=18w11a|Gold ingots can now be obtained as a [[drops|drop]] from [[drowned]].
|Gold ingots now generate in [[shipwreck]] chests.}}
{{History||1.14|snap=18w43a|[[File:Gold Ingot JE3.png|32px]] The texture of gold ingots has been changed.}}
{{History|||snap=18w44a|[[File:Gold Ingot JE4 BE2.png|32px]] The texture of gold ingots has been changed, once again.}}
{{History|||snap=18w50a|Gold ingots now generate in chests in [[village]] toolsmith houses and temples.}}
{{History||1.16|snap=20w06a|Gold ingots are now used to craft [[netherite ingot]]s.}}
{{History|||snap=20w07a|Gold ingots can now be used to [[bartering|barter]] with [[piglin]]s.}}
{{History|||snap=20w11a|Gold ingots can now be [[smelting|smelted]] from [[nether gold ore]].}}
{{History|||snap=20w16a|Gold ingots now generate in [[bastion remnants]] and [[ruined portal]] chests.}}
{{History||1.16.2|snap=20w30a|The average yield of gold ingots from bastion remnant chests has been slightly increased.}}
{{History||1.17|snap=21w05a|Drowneds no longer drop gold ingots, and instead drop [[copper ingot]]s.}}
{{History|||snap=21w08a|Gold ingots can now be smelted from [[deepslate gold ore]].}}
{{History|||snap=21w14a|Gold ingots can now be smelted from [[raw gold]].}}
{{History||1.20<br>(Experimental)|link=1.19.4|snap=23w04a|Gold ingots can now be used as an armor trim material.}}
{{History|||snap=23w05a|Gold ingots can now be trimmed with gold [[armor]].}}
{{History|pocket alpha}}
{{History||v0.2.0|[[File:Gold Ingot JE2 BE1.png|32px]] Added gold ingots. They are currently unobtainable and serve no purpose.}}
{{History||v0.3.2|Gold ingots are now obtainable by [[smelting]] gold ore in a [[furnace]].
|Gold ingots can be used to craft [[blocks of gold]], gold [[pickaxe]]s, [[axe]]s, [[sword]]s and [[shovel]]s.}}
{{History||v0.4.0|Gold ingots are now used to [[crafting|craft]] gold [[hoe]]s.}}
{{History||v0.6.0|Gold ingots are now used to craft gold [[armor]].}}
{{History||v0.8.0|snap=build 1|Gold ingots are now used to craft [[clock]]s.}}
{{History|||snap=build 2|Gold ingots are now used to craft [[powered rail]]s.}}
{{History||v0.9.0|snap=build 1|Gold ingots can now be found in blacksmith [[chest]]s in [[village]]s, [[stronghold]] altar chests and [[dungeon]] chests.}}
{{History||v0.12.1|snap=build 1|Gold ingots are now used to craft [[gold nugget]]s and [[golden apple]]s.
|Gold ingots are now found in [[nether fortress]] chests.}}
{{History||v0.13.0|snap=build 1|Gold ingots are now used to [[crafting|craft]] light [[weighted pressure plate]]s.
|Gold ingots now generate inside of hidden chest rooms in [[desert temple]]s.}}
{{History||v0.14.0|snap=build 1|Gold ingots are now found in [[minecart with chest]]s that generate in [[mineshaft]]s.}}
{{History||v0.15.0|snap=build 1|Gold ingots can now be found in [[jungle temple]] [[chest]]s.}}
{{History||v0.16.0|snap=build 4|Gold ingots can now be used to power [[beacon]]s.}}
{{History|pocket edition}}
{{History||1.0.0|snap=alpha 0.17.0.1|Gold ingots can now be found in [[end city]] ship chests and [[stronghold]] storerooms.}}
{{History||1.0.4|snap=alpha 1.0.4.0|Added [[trading]], cleric [[villager]]s now [[trading|buy]] 8–10 gold ingots for 1 [[emerald]].}}
{{History||1.1.0|snap=alpha 1.1.0.0|Gold ingots are now found in [[woodland mansion]] [[chest]]s.}}
{{history|bedrock}}
{{History||1.4.0|snap=beta 1.2.13.8|Added [[drowned]], which rarely [[drops|drop]] gold ingots.}}
{{History|||snap=beta 1.2.14.2|Gold ingots can now be found inside [[buried treasure]] [[chest]]s and [[shipwreck]]s.}}
{{History||1.10.0|snap=beta 1.10.0.3|Gold ingots can now be found in [[plains]] [[village]] weaponsmith chests.
|[[File:Gold Ingot JE4 BE2.png|32px]] The texture of gold ingots has been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Gold ingots can now be found in [[desert]] village temple [[chest]]s and village toolsmith chests.
|Gold ingots can now be found in [[savanna]], [[taiga]], [[snowy taiga]], [[snowy tundra]] and desert village weaponsmith chests.}}
{{History|||snap=beta 1.11.0.4|Cleric [[villager]]s now [[trading|buy]] 3 gold ingots for one [[emerald]].}}
{{History||1.16.0|snap=beta 1.16.0.51|Gold ingots are now used to craft [[netherite ingot]]s.
|Gold ingots can now be used to [[bartering|barter]] with [[piglin]]s.}}
{{History|||snap=beta 1.16.0.57|Gold ingots can now be [[smelting|smelted]] from [[nether gold ore]].
|Gold ingots now be found in [[ruined portal]] and [[bastion remnants]] chests.}}
{{History||1.16.210|snap=beta 1.16.210.57|Gold ingots can no longer be obtained as a [[drops|drop]] from [[drowned]].}}
{{History||1.17.0|snap=beta 1.16.230.52|Gold ingots can now be smelted from [[deepslate gold ore]].}}
{{History|||snap=beta 1.17.0.50|Gold ingots can now be smelted from [[raw gold]].}}
{{History||1.19.80|snap=beta 1.19.80.21|Gold ingots 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:Gold Ingot JE2 BE1.png|32px]] Added gold ingots.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Gold Ingot JE4 BE2.png|32px]] The texture of gold ingots has been changed.}}
{{History|new3DS}}
{{History||0.1.0|[[File:Gold Ingot JE2 BE1.png|32px]] Added gold ingots.}}
{{History|foot}}
== Issues ==
{{issue list}}
== Trivia ==
*Gold ingots are the only ingots in the game used alongside another [[item]] to [[crafting|craft]] another type of ingot; in this case, it is used with [[netherite scrap]] to craft a [[netherite ingot]].
== See also ==
*{{BlockLink|Block of Gold}}
*{{ItemSprite|Golden Chestplate}} [[Golden Armor]]
*{{ItemLink|Gold Nugget}}
*{{BlockLink|Gold Ore}}
*[[Ore]]s
{{Items}}
[[cs:Zlatý ingot]]
[[de:Goldbarren]]
[[es:Lingote de oro]]
[[fr:Lingot d'or]]
[[hu:Aranyrúd]]
[[ja:金インゴット]]
[[ko:금괴]]
[[nl:Goudstaaf]]
[[pl:Sztabka złota]]
[[pt:Barra de ouro]]
[[ru:Золотой слиток]]
[[uk:Золотий зливок]]
[[zh:金锭]]
[[Category:Renewable resources]]</li></ul></nowiki> | 14w02a | Entities other than players can now be part of teams and have objective scores. | |||||||||||||||||||||||||||||||||
| 14w06a | Added the trigger and team kill-based objective criteria. | ||||||||||||||||||||||||||||||||||
Added /scoreboard players enable. | |||||||||||||||||||||||||||||||||||
| "*" can be used in a player 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. | |||||||||||||||||||||||||||||||||||
| 14w07a | Added /scoreboard operation and /scoreboard 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. | |||||||||||||||||||||||||||||||||||
| 14w10a | Added 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. | |||||||||||||||||||||||||||||||||||
| 14w25a | Added =, <, and > to /scoreboard players operation. | ||||||||||||||||||||||||||||||||||
Issues
Issues relating to "Scoreboard" are maintained on the bug tracker. Report issues there.
Gallery
References
| Help | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Menu screens |
| ||||||||||||||||||
| Game customization | |||||||||||||||||||
| Editions |
| ||||||||||||||||||
| Miscellaneous | |||||||||||||||||||
