Minecraft Wiki
Advertisement
Crafting Table
This article describes content that may be included in a future update. 
This content has appeared in development versions, but the full update containing it has not been released yet.

Loot tables are upcoming technical JSON tables that represent what items should be in a naturally generated chest, what items should drop when killing a mob, or what items can be fished.

Usage

The loot tables are structured as a String tag which determines the table to use, and a Long tag determining the seed. Chests or mobs with the same seed and table will drop the same items. Loot tables do not determine which slot of a chest is used; that is randomly determined based on the seed.

For Chests, Trapped Chests, Storage Minecarts and Minecarts with Hoppers:

    •  LootTable: Loot table to be used to fill the chest when it is next opened, or the items are otherwise interacted with. When the chest is part of a double chest, only the half corresponding to the tagged single-chest will be affected.
    •  LootTableSeed: Seed for generating the loot table. 0 or omitted will use a random seed.

These tags will be removed once the items have been interacted with (by opening the chest, breaking the chest, etc.), and only then will items be put in the chest.

For Mobs:

  • The root tag.
    •  DeathLootTable: Loot table to be used for the items that drop when the entity is killed.
    •  DeathLootTableSeed: Seed for generating the loot table. 0 or omitted will use a random seed.

The loot tables of Mobs and Chests can be altered with /entitydata and /blockdata.

Custom maps can use loot tables to change what loot will spawn in chests or drop by mobs. They can either modify existing loot tables or create new ones. This is the file structure:

  • <world save folder>
    • data
      • loot_tables

Each folder under "loot_tables" is a namespace. The default files are under the namespace "minecraft", but custom maps and mods each have their own namespaces. For example, if you were to create a custom map called "Awesome Parkour Map," your namespace might be "awesome_parkour_map" (they can't contain spaces). It would contain any loot tables the map uses.

To override the default loot tables, you would place them in the "minecraft" namespace. They are organized by entities, chests, and fishing, as shown in the section List of loot tables. To use a custom namespace, set the loot table tag to "namespace:table_name", where "namespace" is the name of your namespace and "table_name" is the filename of your table, without the .json extension.

Tags

Loot tables are defined using the JSON format. Below are a list of tags used.

  •  The root tag
    •  pools: A list of all pools for this entity. Each pool used will generate items from its list of items based on the number of rolls. Pools are applied in order.
      •  A pool
        •  conditions: Determines conditions for this pool to be used. If multiple conditions are specified, all must pass.
          •  A condition
            •  condition: Name of condition. Valid conditions are described below.
        •  rolls: Specifies the exact number of rolls on the pool.
        •  rolls: Specifies a random number of rolls within a range.
          •  min: Minimum number of rolls.
          •  max: Maximum number of rolls.
        •  entries: A list of all things that can be produced by this pool. One entry is chosen per roll as a weighted random selection from all entries without failing conditions.
          •  An entry
            •  conditions: Determines conditions for this entry to be used. If multiple conditions are specified, all must pass.
              •  A condition
                •  condition: Name of condition. Valid conditions are described below.
            •  type: Type of entry. Can be item for item entries, loot_table to produce items from another loot table, or empty for an entry that generates nothing.
            •  name:
              • For type 'item', ID name of the item to be produced, e.g. minecraft:diamond. The default, if not changed by functions, is a stack of 1 of the default instance of the item.
              • For type 'loot_table', loot table to be used, e.g. minecraft:gameplay/fishing/junk.
            •  functions: For type 'item', applies functions to the item stack being produced. Functions are applied in order, so for example looting_enchant must be after set_count to work correctly.
              •  A function:
                •  function: Name of the function to apply. Valid functions are described below.
                •  conditions: Determines conditions for this function to be applied. If multiple conditions are specified, all must pass.
                  •  A condition
                    •  condition: Name of condition. Valid conditions are described below.
            •  weight: Determines how often this entry will be chosen out of all the entries in the pool. Entries with higher weights will be used more often (chance is this entry's weighttotal of all considered entries' weights).
            •  luck: Unused, but set in the built-in fishing.json. Possibly intended to be luck_multiplier.
            •  luck_multiplier: Increases the entry's weight based on luck being applied to this application of the loot table, formula is floor( weight + weight * luck_multiplier * luck ). Currently, luck is only set (to the level of the Luck of the Sea enchantment) when fishing, and is not passed through loot_table entries.

Functions

Loot tables use various functions to change the item stack being produced, such as adjusting the stack size or adding enchantments. Below are a list of valid functions, and the tags used by them. The tags are placed in the same function object as  function:.

  • enchant_randomly - Enchants the item with one randomly-selected enchantment. The level of the enchantment, if applicable, will be random.
    •  enchantements: List of enchantment names to choose from. If omitted, all enchantments applicable to the item will be possible.
  • enchant_with_levels - Enchants the item, with the specified enchantment level (roughly equivalent to using an enchantment table at that level).
    •  treasure: Determines whether treasure enchantments are allowed on this item.
    •  levels: Specifies the exact enchantment level to use.
    •  levels: Specifies a random enchantment level within a range.
      •  min: Minimum level to use.
      •  max: Maximum level to use.
  • furnace_smelt - Smelts the item as it would be in a furnace. Used in combination with the entity_properties condition to cook food for animals on death.
  • looting_enchant - Adjusts the stack size based on the level of the Looting enchantment on the killer entity.
    •  count: Specifies an exact number of additional items per level of looting.
    •  count: Specifies a random number (within a range) of additional items per level of looting. Note the random number generated may be fractional, and will be rounded after multiplying by the looting level.
      •  min: Minimum increase.
      •  max: Maximum increase.
  • set_attributes - Add attribute modifiers to the item.
    •  modifiers
      •  A modifier
        •  name: Name of the modifier.
        •  attribute: The name of the attribute this modifier is to act upon.
        •  operation: Must be either "addition", "multiply_base" or "multiply_total".
        •  amount: Specifies the exact amount of change of the modifier.
        •  amount: Specifies a random amount within a range.
          •  min: Minimum amount.
          •  max: Maximum amout.
        •  id: Optional : UUID of the modifier following. If non specified, a new UUID will be generated.
        •  slot: Slots the item must be in for the modifier to take effect, this value can be one of the following : "mainhand", "offhand", "feet", "legs", "torso", or "head".
        •  slot: One of the listed slots will be chosen randomly.
  • set_count - Sets the stack size.
    •  count: Specifies the exact stack size to set.
    •  count: Specifies a random stack size within a range.
      •  min: Minimum stack size.
      •  max: Maximum stack size.
  • set_damage - Sets the item's damage value (durability) for tools.
    •  damage: Specifies the damage fraction to set (1.0 is undamaged, 0.0 is zero durability left).
    •  damage: Specifies a random damage fraction within a range.
      •  min: Minimum value.
      •  max: Maximum value.
  • set_data - Sets the item data value of the item.
    •  data: Specifies the exact value to set.
    •  data: Specifies a random value within a range.
      •  min: Minimum value.
      •  max: Maximum value.
  • set_nbt - Adds NBT data to an item.
    •  tag: Tag string to add, similar to those used by commands. Note that the first bracket is required and quotation marks need to be escaped using a backslash (\).

Conditions

Loot tables use various conditions which add requirements to a drop, pool, or function. Below are a list of valid conditions, and the tags used by them. The tags are placed in the same condition object as  condition:.

  • entity_properties - Test properties of an entity.
    •  entity: Specifies the entity to check for the condition. Set to this to use the entity that died, killer for the killer, or killer_player for a killer that is a player.
    •  properties: Properties to be checked.
      •  on_fire: Test whether the entity is or is not on fire.
  • entity_scores - Test the scoreboard scores of an entity.
    •  entity: Specifies the entity to check for the condition. Set to this to use the entity that died, killer for the killer, or killer_player for a killer that is a player.
    •  scores: Scores to check. All specifies scores must pass for the condition to pass.
      •  A score: Key name is the objective while the value is the exact score value required for the condition to pass.
      •  A score: Key name is the objective while the value specifies a range of score values required for the condition to pass.
        •  min: Minimum score.
        •  max: Maximum score.
  • killed_by_player - Test if a killer_player entity is available.
    •  inverse: If true, the condition passes if killer_player is not available.
  • random_chance - Test if a random number 0.0–1.0 is less than a specified value.
    •  chance: Success rate as a number 0.0–1.0.
  • random_chance_with_looting - Test if a random number 0.0–1.0 is less than a specified value, affected by the level of Looting on the killer entity.
    •  chance: Base success rate.
    •  looting_multiplier: Looting adjustment to the base success rate. Formula is chance + looting_level * looting_multiplier.

List of loot tables

Below is a list of all loot tables that exist by default. More tables can be added in the world save for use with custom maps.

  • loot_tables
    • chests - Items from loot chests
    • entities - Items dropped from entities. May cause issues when applied to chests, due to some items spawning in stacks of 0
      • sheep - Sheep with wool, also inherited by colored sheep
        • black
        • blue
        • brown
        • cyan
        • gray
        • green
        • light_blue
        • lime
        • magenta
        • orange
        • pink
        • purple
        • red
        • silver
        • white
        • yellow
      • bat
      • blaze
      • cave_spider
      • chicken
      • cow
      • creeper
      • elder_guardian
      • enderman
      • endermite
      • ghast
      • giant
      • guardian
      • horse
      • iron_golem
      • magma_cube
      • mushroom_cow
      • ocelot
      • pig
      • rabbit
      • sheep - Sheep without wool
      • shulker
      • silverfish
      • skeleton
      • skeleton_horse
      • slime
      • snowman - Snow golems
      • spider
      • squid
      • witch
      • wolf
      • zombie
      • zombie_horse
      • zombie_pigman
    • gameplay
      • fishing
        • fish
        • junk
        • treasure
      • fishing - Loads the three tables from the fishing folder, applying luck to each one
    • empty - Contains no items

Custom Maps

Custom maps can use loot tables to change what loot will spawn in chests or drop by mobs. They can either change existing loot tables or create new ones. This is the file structure:

  • <world save folder>
    • data
      • loot_tables
        • minecraft

The JSON files go in this folder. For example, the file for zombies would go in data/loot_tables/minecraft/entities/zombie.json. This will make every zombie in that world use your loot table rather than the default zombie loot table. To use custom loot tables, add the file to the "minecraft" directory. Then, summon the mob with the data tag DeathLootTable set to the name of the file (without the .json extension).

History

u
1.9
{{Extension DPL}}<ul><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><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>
October 19, 2015Dinnerbone announces loot tables.
15w43aAdded loot tables.
15w43bAdded condition entity_scores.
15w43cRenamed "villager_golem.json" to "iron_golem.json"
Added fishing loot tables, sheep without wool, and zombie and skeleton horses.
Renamed the tag  item: to  name:, and the tag  items: to  entries:
Added the tag  type: and support to load a loot table instead of an item.
Added the tag  luck: to default files, though it currently does nothing in the code.
Added the function set_damage
15w44aAdded the function enchant_randomly and set_attributes.
Advertisement