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.

The Elder Guardian is a hostile mob which only spawns underwater in ocean monuments. It is a stronger variant of the Guardian.

The Elder Guardian spawns 3 times in set sections of the ocean monument. Elder Guardians inflict Mining Fatigue III on nearby players, the purpose of this being to protect the treasures (gold blocks and wet sponges) of the monument from being stolen until after the monument has been fully conquered, as well as to prevent players from simply mining through the monument walls.

The Elder Guardian attacks by emitting a beam which harms the player. In addition, Elder Guardians can target and damage players who are riding in boats; however once the player is out of range, the Guardian's beam will disengage from the player, and deal no damage.

Behavior

Elder Guardians do not swim around as much as normal Guardians, however they act the same as regular guardians on land. Their eye will follow and stare at any nearby players, and will always look directly at who they're attacking. This makes them the first mob with dynamic eyes. (The eye is actually the head part of the model and almost all mob's heads will look toward the player making it look as if the mob's eye was looking at you.) Elder Guardians' eyes will still follow a completely unarmored player under the effects of a Potion of Invisibility, but this is entirely visual and they won't attack them. Elder Guardians will still attack squids under that same status effect though.

Once each minute, the Elder Guardian will search for players in a 50-block radius who are not afflicted with Mining Fatigue, who are afflicted with a level of fatigue lower than III, or whose affliction will wear off in less than one minute. The players found will be inflicted with Mining Fatigue III for 5 minutes, and a ghostly image of the Elder appears to the player.

Attacking

The Elder Guardian has two methods of attack, firing its laser and a thorn-like attack. The laser takes several seconds to charge, doing no damage in the meantime, and changing from purple to bright yellow. Once charged, the beam abruptly ends and deals damage. The Elder Guardian will swim around for a few seconds before firing again. If the target comes near the Elder Guardian while it is firing its beam, it will stop firing and swim away until it is at a comfortable range, at which point it will continue attacking. The beam cannot be dodged, but can be obstructed by solid blocks, and has a maximum range of approximately 14 blocks.

Combat

Elder Guardians are very resistant to melee attacks when under water, as the player will not be able to quickly approach the Guardian due to the water's slowing effect. Guardians will swim away when approached by a player it is targeting, and the Elder Guardian will deal 2 hearts of damage every time it is hit when its spikes are extended. If cornered, the Elder Guardian will usually extend its spikes and fire at the player, even at point blank range.

If the player must fight an Elder Guardian in melee, they should try to corner it and hope for the best; or else try to trick it into swimming within melee range repeatedly.

The Elder Guardian cannot shoot as fast as a player with a bow can, so a skilled player will be able to shoot the Guardian, and then hide to break the beam's lock, repeating until the Guardian is dead. Note that the new arrow mechanics introduced in 14w25a will cause arrows to slow down and eventually fall when in water, so the player may be forced to shoot at very close range. If the Guardian is in shallow water the player can use a fishing rod to pull it out of the water where the players can then kill it with melee without being shot at or hurt by the spikes. (The guardian can still shoot while out of water, but unless it's held still, it flops around too much to keep the target in range.)

The Elder Guardian has a very large amount of HP (80), making melee attacks even harder. Elder Guardians do more damage than regular Guardians. Diamond equipment enchanted with Respiration and Depth Strider, swords and bows are recommended. Fighting Elder Guardians is incredibly dangerous without armor, if not impossible. Entering their territory without armor will almost always lead to a swift death, even if armed with a sword or bow and arrow.

Video

Elder Guardian/video

History

u
[[u Template:1.8|Template:1.8]]
{{Extension DPL}}<ul><li>[[Camera|Camera]]<br/>{{about|the entity|the command|commands/camera}}
{{exclusive|edu}} 
{{unobtainable|edition=be}}
{{ItemEntity
|imagesize=80px
|renewable=No
|stackable=Yes (64)
|health={{hp|4}}
|image=Camera.png}}
{{Block
| title = Camera Block
| image = Camera (block).png
| invimage = none
| transparent = No
| light = 0
| tool = any
| stackable = Yes (64)
| flammable = No
| lavasusceptible = No
| renewable = No
}}

The '''camera''' is an [[entity]] that is capable of capturing and storing images. {{IN|edu}}, it works together with the [[portfolio]] item to create collections of [[photo]]s.<ref>https://education.minecraft.net/support/knowledge-base/using-cameras-portfolios/</ref>

== Obtaining ==
The camera can be obtained in the [[Creative inventory]] in ''Minecraft Education''. It can be obtained either by NBT editors, inventory editors, or glitches in Bedrock Edition.

To get the block form of the camera in Bedrock Edition using an NBT editor, you need to set the item name of the block in the inventory slot (<code>name:</code> ) to <code>item.camera</code>, then you need to add a compound tag called <code>Block</code> and inside of that put the int tag <code>version: 18040335</code> and the text tag <code>name: minecraft:camera</code> into the block compound tag. For the usable "[[spawn egg]]" form of the camera, you only need to set the item name of the block in the inventory slot (<code>name:</code> ) to <code>camera</code>; you do not need to add the block compound for this form of the camera. 

== Usage ==
Using a camera from the [[inventory]] captures a first-person screenshot. It can also be placed, creating a camera [[entity]] that can track the user, and take pictures from the camera's perspective. Photos that are taken using the camera appear in the [[portfolio]].

Close-up snapshots of an [[item]] on the ground can be taken by holding the Shift key while right-clicking.

Photos that are taken with the camera block are stored in <code>%localappdata%\Packages\MinecraftUWP_8wekyb3d8bbwe\LocalState\screenshots</code>.

== Sounds ==
=== Generic ===
{{Sound table/Block/Normal/BE}}
=== Unique ===
{{Sound table
|sound=Camera1.ogg
|sound2=Camera2.ogg
|sound3=Camera3.ogg
|type=bedrock
|description=When a picture is taken with a camera
|source=Players
|id=camera.take_picture
|volume=1.0
|pitch=1.0
|foot=1}}

== Data values ==
=== ID ===
{{ID table
|edition=bedrock
|firstcolumnname=Camera
|shownumericids=y
|showforms=y
|generatetranslationkeys=y
|displayname=Block
|spritename=camera
|spritetype=block
|nameid=camera
|id=242
|form=block
|itemform=item.camera}}
{{ID table
|displayname=Item
|spritename=camera
|spritetype=item
|translationtype=item
|nameid=camera
|id=593
|form=item
|foot=1}}
{{ID table
|edition=bedrock
|firstcolumnname=Camera
|shownumericids=y
|generatetranslationkeys=y
|displayname=Entity
|spritename=camera
|spritetype=entity
|nameid=tripod_camera
|id=62
|foot=1}}

=== Entity data ===

See [[Bedrock Edition level format/Entity format]].

== Video ==
{{yt|1XLRGFibFNQ}}

== History ==
{{History|pocket alpha}}
{{History||v0.1.0|[[File:Camera BE1.png|50px]] [[File:Camera (item texture) BE1.png|32px]] The textures and model of the camera can be found in the game apk file.<ref name="found">[{{Reddit|jkkmr/found_image_file_for_camera_in_minecraft_portable}} Reddit - Found image file for camera in Minecraft Portable Edition Demo APK file.]</ref><ref>https://web.archive.org/web/20160604161800/https://twitter.com/Kappische/status/103548954368679936</ref>}}
{{History||v0.2.0|[[File:Camera BE2.png|50px]] [[File:Music Disc Blocks JE1 BE1.png|32px]] Added cameras
|Changed item and tripod textures.
|To use a camera, equip it in the [[player]]'s hand, then look in the direction the player wants the picture to be taken. Long-press the screen, and a camera [[drops]] to the ground where the player are standing. Step back, then press on the camera until it starts emitting smoke [[particles]]. The smoke means a picture has been taken, and the camera may disappear immediately afterward.
|Cameras have infinite uses.
|Entity id 62 and item id 456.<ref>https://www.minecraftforum.net/topic/1233138-i-found-the-camera-id/</ref>}}
{{History||v0.5.0|The camera is now invisible and makes the standard player [[damage]] [[sound]].}}
{{History||v0.7.0|Added the "F1" feature (Hide GUI), which has now made the camera obsolete.}}
{{History||v0.8.0|snap=build 2|[[File:Egg JE1 BE1.png|32px]] Item form now uses [[egg]] texture.}}
{{History||v0.9.0|snap=build 1|The camera [[entity]] has been removed. [[Tommaso]] also stated: ''"It doesn't mean that it's dead forever, in fact I have a lot of ideas for it! I think it will be back when have [[shader]]s, sharing and [[redstone]]."''<ref>{{Reddit|sub=MCPE|281sep/camera|ci6znr8}}</ref>}}
{{History||v0.14.0|snap=build 1|[[File:Camera BE3.png|32px]] [[File:Camera (item) BE2.png|32px]] Re-added the camera. It is accessible only with [[inventory]] editors.
|In this version, if the player spawns a camera, leaves the [[world]] and joins back, it summons [[lightning]].}}
{{History||v0.14.2|The camera [[item]] ID has been changed to 498, but it cannot be used at the moment. The [[entity]] can now be spawned with a [[spawn egg]] with a [[damage]] value of 62.
|According to the language files of the game, the empty label that shows up whenever hovering a finger to a camera would now say "Take Picture". However, the button doesn't do anything.}}
{{History||v0.15.0|snap=build 1|The previous empty label on the camera mentioned above now displays the words "Take Picture".
|The [[health]] of the camera [[entity]] is now {{hp|2}} instead {{hp|4}}.
|The camera no longer summons [[lightning]].}}
{{History||v0.16.0|snap=build 1|The camera now has a [[block]] form in [[inventory]], but still spawns the entity. However, the block can be placed only with [[commands]] and editing.
|"Take picture" button on the camera works now, but no image files are created.
|The oldest ID for camera (456) now refers to [[portfolio]].}}
{{History|||snap=build 2|[[File:Camera Block.png|32px]] The camera now has an [[item]] form and the [[block]] has been removed. However, it is still obtainable in servers.
|[[Portfolio]], which works together with the camera to create collections of pictures, has been removed.}}
{{History|||snap=build 4|Camera item form has been removed, and the camera can no longer be obtained or placed using any [[commands|command]].}}
{{History|bedrock}}
{{History||1.8.0|snap=beta 1.8.0.8|[[File:Camera BE3.png|32px]] [[File:Camera Block.png|32px]] The camera has been reimplemented.
|The camera [[entity]] can now be spawned with a [[spawn egg]] with [[damage]] value 258.}}
{{History||1.12.0|snap=beta 1.12.0.2|The camera can now be obtained with the {{cmd|give}} [[commands|command]].}}
{{History||1.13.0|snap=beta 1.13.0.1|The camera can no longer be obtained with the {{cmd|give}} command.
|Functionality has been added to the camera. Screenshots that are taken by the camera can now be saved into the {{cd|screenshots}} folder.
|Cameras are now a part of the {{el|ee}} toggle as a hidden feature.
|Cameras no longer have a [[death]] animation when killed by the [[player]] and instead, instantly emit smoke [[particles]].}}
{{History||1.16.100|snap=beta 1.16.100.50|The camera can now be obtained with the {{cmd|give}} [[commands|command]] once again.}}
{{History|||snap=beta 1.16.100.55|The camera can no longer be obtained with the {{cmd|give}} command.}}
{{History|education}}
{{History||1.0|[[File:Camera BE3.png|32px]] [[File:Camera Block.png|32px]] Added cameras.}}
{{History||1.4.0|Cameras no longer have a [[death]] animation when killed by the [[player]] and instead instantly emit smoke [[particles]].}}
{{History|foot}}

=== Future ===
At the Minecraft [[Pocket Edition]] panel at [[MineCon 2012]], as well as one of [[Johan Bernhardsson|Jbernhardsson]]'s livestreams, it was stated that future plans include trying to have a proper use for cameras, perhaps an easier way to take screenshots and share them with others.<ref>{{ytl|YMhyX_lKWV4}}</ref> In the BlockTalk Q&A, the camera was briefly mentioned as part of a broader "sharing" theme planned for {{el|be}} in the future.<ref>{{ytl|Ruf6tvqsD84}}</ref>
It later got implemented into {{el|ee}}, using the camera to make screenshots and share them in a special book.

== Issues ==
{{Issue list}}

== Trivia ==
* A camera prevents a [[Book and Quill]] from working. Attempting to craft it or obtain it by commands gives a regular book instead, due to non-implementation of photo attaching to written books.
* The camera can take a screenshot, which appears a bit smaller with a thick paper outline having cuts on its edges, making it look like an old photograph.
* This feature is hidden from the Creative inventory and from the /give command item menu.

== Gallery ==
<gallery>
PEcameras030.jpg|A row of cameras, as seen in [[Pocket Edition v0.3.0 alpha|v0.3.0]].
PEcameraphoto.jpg|Example image taken by the camera [[entity]].
CameraUse-1.png|The first method of using cameras.
CameraUse-2.png|The second method of using cameras.
Dinnerbone Camera.png|A camera spawned using a [[spawn egg]] named "[[Dinnerbone]]" in the v0.15.0 beta.
Cam2.png|A camera falling from a [[tree]]. This shows that cameras are entities.
Education Edition Exclusive Features.png|The camera and camera block placed in a world along with other Education Edition features.
Screenshot by camera.jpg|An example of the screenshot taken by a camera in [[Bedrock Edition beta 1.13.0.1|beta 1.13.0.1]].
File:Say Cheese.jpeg|[[Steve]], [[Alex]], [[Jesse]], and an [[Agent]] getting their picture taken.
</gallery>

== See also ==
* [[Portfolio]]
* [[Screenshot]]

== References ==
{{Reflist}}

{{Items}}
{{Entities}}
{{Education Edition}}

[[Category:Education Edition entities]]
[[Category:Education Edition items]]
[[Category:Tools]]

[[cs:Kamera]]
[[de:Kamera]]
[[el:Camera]]
[[es:Cámara]]
[[fr:Appareil photo]]
[[hu:Kamera]]
[[ja:カメラ]]
[[ko:카메라]]
[[nl:Camera]]
[[pl:Kamera]]
[[pt:Câmera]]
[[ru:Камера]]
[[uk:Камера]]
[[zh:相机]]</li><li>[[Hopper|Hopper]]<br/>{{About|the block|the crash utility|Hopper (crash utility)}}
{{Block
|image=<gallery>
Hopper (D).png|Java
Hopper (D) BE.png|Bedrock
</gallery>
|extratext = View [[#Gallery|all renders]]
|transparent=Yes
|light=No
|tool=wooden pickaxe
|renewable=Yes
|stackable=Yes (64)
|flammable=No
|lavasusceptible=No
}}
A '''hopper''' is a low-capacity storage [[block]] that can be used to collect [[item (entity)|item entities]] directly above it, as well as to transfer [[item]]s into and out of other containers. A hopper can be locked with [[Redstone Dust|redstone power]] to stop it from moving items into or out of itself.

== Obtaining ==
=== Breaking ===
To obtain a hopper, {{control|mine}} it with a [[pickaxe]]. Using any other item to mine a hopper drops only its contents.
{{breaking row|horizontal=1|Hopper|Pickaxe|Wood|foot=1}}

===Crafting===
A hopper can be crafted from 5 iron ingots and a chest.
{{Crafting
|A1= Iron Ingot
|C1= Iron Ingot
|A2= Iron Ingot
|B2= Chest
|C2= Iron Ingot
|B3= Iron Ingot
|Output= Hopper
|type= Redstone
}}

==Usage==
{{see also|Tutorials/Hopper}}
[[File:Hopper aligment.png|Hoppers can face down or sideways.|thumb]]

A hopper can be used as a container, as a crafting ingredient, and as a redstone component.

A hopper has an "output" tube at its bottom that can face down or sideways and provides a visual indication of which block the hopper is set up to drop its items into, if that block has an inventory. To place a hopper, use the {{control|Place Block}} control while aiming at the surface to which its output should face (Hoppers ''do not'' orient themselves automatically). To place a hopper directly on the face of an already interactable block, the player can {{control|sneak}} while placing the hopper. Attempting to place a hopper aimed on the bottom face of a block instead faces downward. With some blocks, such as the [[furnace]] and [[brewing stand]], the hopper has multiple uses. A hopper does not change direction after placement, and it is not attached to the container it faces; the container can be removed or replaced, and the hopper remains unchanged.

Hoppers cannot be moved by [[piston]]s.{{only|java}} Despite not being a solid block, attached blocks such as [[rail]]s, [[lever]]s, [[tripwire]] and [[redstone]] dust can be placed on top of hoppers, but not on their sides.

===Container===
[[File:Hopper GUI.png|thumb|176px|Hopper GUI showing the hopper's five slots of inventory at the top and the player's inventory below.]]

A hopper can be used as a container and has 5 slots of inventory space.

To open the hopper GUI, use the {{control|use item|text=Use Item/Place Block}} [[control]]. To move items between the hopper inventory and the player inventory or hotbar while the hopper GUI is open, drag or shift-click the items. To exit the hopper GUI, use the {{key|Esc}} key, B button or circle button, depending on the device.

By default, the GUI of a hopper is labeled "Item Hopper". A hopper's GUI label can be changed by naming the hopper in an [[anvil]] before placing it, or, {{in|java}}, by using the [[Commands#data|data]] command (for example, to label a hopper at (0,64,0) "Steve's Hopper", use <code>/data merge block 0 64 0 {CustomName:'"Steve's Hopper"'}</code>).

{{IN|java}}, a hopper's GUI can be "locked" (or subsequently unlocked) by setting the hopper's <code>Lock</code> tag with the [[Commands#data|data]] command. If a hopper's <code>Lock</code> tag is not blank, the hopper cannot be accessed except by players holding an item with the same name as the <code>Lock</code> tag's text. For example, to lock a hopper at (0,64,0) so that only players holding an item named "Steve's Key" can access the hopper, use <code>/data merge block 0 64 0 {Lock:"Steve's Key"}</code>.

===Crafting ingredient===
A hopper can be used to craft a [[minecart with hopper]].
{{crafting usage}}

===Redstone component===
{{see also|Redstone circuit|Redstone components#Hopper}}
[[File:Hopper logic flowchart.png|thumb|Flowchart of hopper logic]]

While a hopper is ''not'' powered by redstone signals, it operates with three functions:

*'''Collect''' [[Item (entity)|item entities]] (free-floating items in the world) into its inventory from the space above it
*'''Pull''' a single item into its inventory from a container above it
*'''Push''' a single item from its own inventory into a container it faces

A hopper first attempts to push any items inside it. Afterward, it checks if the block above it is a type of container. If so, it attempts to pull from it. Otherwise, the hopper attempts to collect item entities. Notably, hoppers can push to and pull from other hoppers, forming '''hopper pipes''' or '''hopper chains''', which allow transporting items across several blocks and are further discussed below.

====Redstone signals====
When a hopper receives a redstone signal (and is considered to be "activated"), all three functions stop. To avoid confusion over the terms "activated" and "deactivated", powered hoppers are often described as being '''locked''' and unpowered hoppers described as being '''unlocked'''. Hoppers can be powered by [[Redstone_mechanics#Power|soft powered]] blocks, meaning a [[redstone dust]] trail pointing into a block touching the hopper locks it just as effectively as a [[redstone block]] or any other [[Redstone components#Power components|power component]] touching the hopper. When the hopper is unlocked during a redstone tick, it does not push or pull/collect during the same tick, but has a delay of 1 redstone tick instead.

While a locked hopper does not push or pull/collect items, it may still receive items from [[dispenser]]s, [[dropper]]s and other hoppers, and may have its items pulled out by another hopper beneath it. Hence, the item flow in a horizontal hopper pipe may be stopped by locking just one of the hoppers, but stopping a vertical hopper pipe requires locking two adjacent hoppers at the same time, such that both the pushing of the top one and the pulling of the bottom one are stopped.  

A hopper does not output any redstone signals by itself, but its fullness can be read using a [[Redstone Comparator|redstone comparator]], which needs to be placed next to it and facing away from it. An empty hopper outputs a signal strength of 0 and a completely full hopper outputs a signal strength of 15. Notably, a single stackable item (16 or 64) outputs a signal strength of 1 and a single non-stackable item outputs a signal strength of 3.  

{{IN|Java}}, if the hopper being read is part of a horizontal hopper pipe, the comparator can individually read each item passing through the chain, because items are pushed through the hoppers one by one at a speed that is manageable by the comparator. If there is an uninterrupted stream of items, the comparator does not switch off in between items. On the other hand, in a vertical hopper pipe, some of the hoppers may never produce a reading above 0, even with a continuous stream of items, because pushes and pulls both occur in the same game tick: The hoppers' items get pulled out a single game tick after they're pushed in and this isn't measurable by a comparator, because comparators need measurements lasting at least 1.5 redstone ticks to produce a reading.  

====Collecting items====
A hopper collects items dropped on top of it if the space above the hopper not occupied by a storage block. Items are gathered from the entire 1 block space above the hopper, meaning that items sitting on partial blocks such as [[soul sand]] directly above a hopper can be collected.<ref>https://bugs.mojang.com/browse/MCPE-55824</ref> It is also possible for a hopper to collect items from inside a full, solid block, a situation that might come from items rising up through solid blocks or being [[commands/summon|summoned]]. Item entities are not collected when they are outside of the collection area however; for example, items on top of a stone block directly above a hopper are not collected. Collected items are placed in the leftmost empty slot of a hopper's inventory.

{{IN|java}}, if there is no container above the hopper, then the hopper collects dropped items in the order in which they landed on the hopper. This order is remembered even while a hopper is locked. For instance, if a hopper is locked under a carpet while a fully equipped [[armor stand]] is broken above it, then it always collects items in this order when it is unlocked: [[armor stand]], [[boots]], [[leggings]], [[chestplates]], [[helmets]]. This is due to the order in which these items land.{{Verify|Wouldn't this be due to the order in which the game creates the item entities that drop drop from the armor stand?}} {{IN|Bedrock}}, hoppers do not remember the order in which items land on the hopper. Instead, hoppers with multiple dropped items above them collect the items in the order in which they entered the chunk in which the hopper is located. Items that drop from a broken armor stand are collected in a random order.<ref>https://bugs.mojang.com/browse/MCPE-120586</ref>

Hoppers usually check for dropped items every [[game tick]] and they can collect items even before they are picked up by a [[player]]{{Verify|Does this happen always, or sometimes, and in Java only or also in Bedrock?}} or destroyed by [[lava]]. However, {{In|Bedrock}} hoppers have a "collection cooldown" time. After collecting an item (or stack of items), a hopper waits {{tooltip|4 redstone ticks|8 game ticks}} (0.4 seconds, barring lag) before attempting to collect again.

Hoppers collect groups of items all at once rather than collecting them as single items one at a time. As a result, hoppers can collect item entities much faster than they can pull items from a container. Pulling from a moving [[minecart with chest]] or [[minecart with hopper]] is even slower, since the minecart is not always above the hopper.

====Pushing and pulling items====
A hopper with a storage container above it (such as a [[furnace]], [[chest]], [[dropper]], [[composter]], or another hopper) attempts to pull from the container instead of checking for floating items above it, and hence can not collect items.  A hopper always tries to push or pull items using the leftmost available slot. When a hopper is removing items from a chest, the items disappear from left to right. Similarly, when filling up a chest, the chest fills up from left to right. Hoppers prioritize pulling from the first slot of a container over pulling into the first hopper slot. If a hopper has stone in its first slot and nothing in its second while the container it is pulling from has chicken in its first slot but stone in the second, the hopper pulls the chicken from the first slot of the container into its empty second slot. However, if the hopper is unable to pull the chicken, such as if all slots are filled with stone, the hopper pulls the stone from the second slot of the container instead. Similarly, hoppers prioritize pushing from their first slot over pushing into the first slot of a container. If a hopper has stone in its first slot and chicken in its second while the container it is pushing to has chicken it its first slot but stone in the second, the hopper pushes stone from its first slot into the second slot of the container.

In [[Java Edition]] the checks done by a hopper while pulling generally require less processing than the checks done by a hopper attempting collection. Therefore, a chain of hoppers topped with storage containers rather than air/solid blocks has better performance (measured as milliseconds of processing per tick) and lower potential for processing lag. <ref name=":0">https://www.youtube.com/watch?v=LC3ZOOI1Rf0</ref> The performance improvement achieved is correlated with the number of storage slots the container has. Placing composters (with no storage slots but still with custom output logic) on top of hoppers provide the greatest efficiency, while double chests actually degrade performance, even when sharing each double chest across two hoppers.<ref name=":0" /> In [[Bedrock Edition]] a chain of hoppers with air or non-container blocks on top has better performance than a chain of hoppers topped by container blocks.<ref>https://cdn.discordapp.com/attachments/715523208530362389/890030941282631741/Redstone_MSPT_measure.xlsx</ref> This may be because, even though hoppers with containers on top do not check for items, they do check for hopper-minecarts and chest-minecarts to pull from, and that involves scanning the chunk entity list.<ref>{{bug|MCPE-109449}}</ref>

{{Schematic|caption='''Push then Pull'''
Chest A is full of items while the hopper and Chest B are empty.
|ch-$+A||-
|ho-$e|ch-$+B
}}

Item pushes and pulls are processed in the same game tick, but pushes are processed before pulls. In the schematic, the empty hopper first pulls an item from chest A as it cannot push anything into chest B. After the cooldown, the hopper first pushes its item into chest B before pulling another item from chest A, both pushing and pulling in the same tick, and the process repeats. The hopper stops pulling when A is empty, and stops pushing when B becomes full.

Hoppers also have a "transfer cooldown" time. After pulling and/or pushing items, a hopper waits {{tooltip|4 redstone ticks|8 game ticks}} (0.4 seconds, barring lag) before pulling or pushing again (a transfer rate of 2.5 items per second, barring lag). A hopper that has an item pushed into it from another hopper also starts a 4 tick cooldown period, regardless of whether it pushed or pulled items itself. Item entities can be collected at any time without affecting the transfer cooldown time. The transfer cooldown and the Bedrock Edition collection cooldown are independent of each other.

====Container interactions====
Some [[container]]s interact with hoppers in specific ways:

:;{{BlockLink|Composter}}
::Hoppers above composters can push compostable items into the composter's top face with a chance of increasing the level of the composter as if the player used the item on the composter. Items that are not compostable cannot be pushed into the composter. Hoppers below the composter can pull [[bone meal]] when the composter is in stage 8, emptying the composter and resetting it to stage 0. Hoppers to the side of a composter do not interact with it.

:;{{BlockLink|Brewing Stand}}
::A working hopper on the top face of a brewing stand deposits only into the ingredient slot and it can push only valid [[brewing]] ingredients. A hopper on side face of a brewing stand can deposit only [[blaze powder]] or filled bottles into the three brew slots. A hopper underneath a brewing stand always extracts from the three brew slots, whether brewing is finished or not—The hopper must be locked to allow potions to finish brewing.

:;{{BlockLink|Chest}}
:;{{BlockLink|Trapped Chest}}
::Large chests and large trapped chests are treated as a single container: A hopper depositing into a large chest fills up the entire chest and a hopper underneath a large chest empties the entire chest. Trapped chests being accessed by a player lock any adjacent hoppers, per the standard behavior of a hopper next to an active power source.

:;{{BlockLink|Furnace}}
:;{{BlockLink|Blast Furnace}}
:;{{BlockLink|Smoker}}
::A working hopper pointing into top of a furnace deposits only into the ingredient slot. It can push any item, including items that can't be smelted by the furnace. A hopper pointing into the side of a furnace deposits into the fuel slot, and only items that are usable as fuel. A hopper below a furnace pulls everything from the output slot and empty [[bucket]]s from the fuel slot left over from using [[lava bucket]]s as fuel. When a hopper removes items from a furnace, the experience points are 'stored' in the furnace until a player removes at least one smelted item, or the furnace block is broken.

:;{{BlockSprite|Hopper}} Hopper
::A sequence of three or more hoppers, each pushing items into the next, is called a '''hopper pipe'''. Working horizontal hopper pipes simply push items into each other at the expected rate of 2.5 items per second, but vertical hopper pipes are more complicated, as the hoppers are trying both to pull and to push. When a vertical pipe pulls from a single container, it simply transfers items at 2.5 items per second because the transfer rate is limited by the first hopper pulling items from the container. If a ''stack of items'' is in a vertical pipe, the items can be transferred twice as fast, because the hopper with the item stack is pushing items down while the hopper below it is also pulling items down.

:;{{EntityLink|Minecart with Chest}}
:;{{EntityLink|Minecart with Hopper}}
::Unlocked hoppers fill chest minecarts and hopper minecarts if any part of the entity's hitbox is within the hopper's target block-space. Hopper minecarts try to pull items from the hopper at high speed. Hoppers can pull items from minecarts above them so rails can be placed directly on the top faces of a hoppers. If a [[detector rail]] is in the right position, it could lock the hopper per standard redstone-hopper behavior.

:;{{BlockLink|Jukebox}}
::Hoppers can insert [[music disc]]s into jukeboxes, and extract the music discs after they finish playing.

:;{{BlockLink|Shulker Box}}
::Hoppers cannot put shulker boxes into other shulker boxes. This allows for the creation of certain [[Tutorials/Hopper#Potions and shulker boxes|item filters]].
::Otherwise, hoppers interact with shulker boxes normally.

:;{{BlockLink|Lectern}}
::Hoppers cannot remove or place books on lecterns. The redstone pulse emitted from a lectern when a page is turned can temporarily lock hoppers.

:;{{BlockLink|Ender Chest}}
::Hoppers cannot interact with ender chests in any way.

:;{{BlockLink|Barrel}}
:;{{BlockLink|Dispenser}}
:;{{BlockLink|Dropper}}
:;{{EntityLink|Boat with Chest}}
::Hoppers interact normally with barrels, dispensers, droppers, and boats with chests.

:;{{BlockLink|Chiseled Bookshelf}}
::Hoppers and minecart with hoppers can insert and remove books from the bookshelf. As with any other container, items are taken from the first slot that has an item that can fit in the hopper and are inserted into the first empty slot.

==Sounds==
===Generic===
{{Sound table/Block/Metal}}
===Unique===
{{Edition|Java}}:
{{Sound table
|sound=Door close.ogg
|sound2=Door open.ogg
|subtitle=Chest locked<ref group=sound name=lock>{{Bug|MC-98316||Wrong subtitles caused by missing distinction}}</ref>
|source=block
|description=When a player attempts to open a hopper locked using the {{nbt|string|Lock}} tag
|id=block.chest.locked|idnote=<ref group=sound name=lock/>
|translationkey=subtitles.block.chest.locked|translationkeynote=<ref group=sound name=lock/>
|volume=1.0
|pitch=1.0
|distance=16
|foot=1}}

{{Edition|Bedrock}}: ''None''

==Data values==
===ID===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Hopper
|spritetype=block
|nameid=hopper
|foot=1}}
{{ID table
|displayname=Block entity
|spritename=hopper
|spritetype=block
|nameid=hopper
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|firstcolumnname=Hopper
|shownumericids=y
|showforms=y
|generatetranslationkeys=y
|displayname=Block
|spritename=hopper
|spritetype=block
|nameid=hopper
|id=154
|form=block
|itemform=item.hopper}}
{{ID table
|displayname=Item
|spritename=hopper
|spritetype=item
|nameid=hopper
|id=527
|form=item
|translationkey=tile.hopper.name
|foot=1}}
{{ID table
|notnamespaced=y
|displayname=Block entity
|spritename=hopper
|spritetype=block
|nameid=Hopper
|foot=1}}

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

{{/BS}}

===Block data===
A hopper has a block entity associated with it that holds additional data about the block.

{{el|java}}:
{{see also|Block entity format}}
{{/BE}}

{{el|bedrock}}:
:See [[Bedrock Edition level format/Block entity format]].

==Achievements==
{{load achievements|Freight Station;Smelt Everything}}

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

==History==
{{History|java}}
{{History||1.5|snap=13w01a|[[File:Hopper (D) JE1.png|32px]] [[File:Hopper (N) JE1.png|32px]] [[File:Hopper (E) JE1.png|32px]] [[File:Hopper (S) JE1.png|32px]] [[File:Hopper (W) JE1.png|32px]] [[File:Hopper (U) JE1.png|32px]] Added hoppers.
|Hoppers with the [[damage]] value of 1, which are obtainable only through world editing, visually point in no direction. They functionally push items upward, however the behavior is inconsistent.
|[[File:Hopper (item) JE1.png|32px]] There is currently a temporary "work in progress" sprite for hoppers in the [[inventory]].
|Hoppers can be [[crafting|crafted]] from a [[chest]] and [[stone]] blocks with the following recipe:
{{{!}} class{{=}}"collapsible collapsed"
! Recipe
{{!}}-
{{!}}
{{Crafting Table
  |A1= Stone
  |C1= Stone
  |A2= Stone
  |B2= Chest
  |C2= Stone
  |B3= Stone
  |Output= Hopper
}}
{{!}}}
}}
{{History|||snap=13w01b|[[Rail]]s can now be placed on top of hoppers. 
|Hoppers no longer load [[item]]s into [[minecart]]s without [[chest]]s.}}
{{History|||snap=13w02a|[[File:Hopper (item) JE2 BE1.png|32px]] The [[inventory]] sprite of hoppers has been changed.
|[[File:Hopper (item) 13w02a.png|32px]] However, the [[item]] of hoppers appears bugged if [[drops|dropped]] or placed in an [[item frame]].<ref>{{bug|MC-6737}}</ref> This may be due to the game attempting to pull the item sprite from the hopper's equivalent spot in <samp>[[stitched_terrain.png]]</samp> (compare files: [[:File:13w02a stitched terrain.png|terrain]], [[:File:13w02a stitched items.png|items]]), a region which contains parts of the oak planks, end stone and iron bars textures.
|Applying a [[redstone]] signal to a hopper now deactivates the hopper until the signal is removed.
|Hoppers can no longer be used as [[fuel]] in a [[furnace]].
|Hoppers are now [[crafting|crafted]] using 5 [[iron ingot]]s rather than 5 [[stone]] blocks.
{{{!}} class{{=}}"collapsible collapsed"
! Recipe
{{!}}-
{{!}}
{{Crafting
|A1= Iron Ingot
|C1= Iron Ingot
|A2= Iron Ingot
|B2= Chest
|C2= Iron Ingot
|B3= Iron Ingot
|Output= Hopper
}}
{{!}}}
|Hoppers now pull only from the output slot of [[furnace]]s.
|Hoppers now output 1 signal strengh per 1/3 of a stack (21 [[item]]s) when interacting with a [[redstone comparator]].
|[[File:Hopper (D) JE2.png|32px]] [[File:Hopper (N) JE2.png|32px]] [[File:Hopper (E) JE2.png|32px]] [[File:Hopper (S) JE2.png|32px]] [[File:Hopper (W) JE2.png|32px]] [[File:Hopper (U) JE2.png|32px]] The texture of hoppers has been given a unique texture. Hoppers no longer use the [[cauldron]] texture. Note that the top texture does not rotate with facing direction.
|The preferred tool is now a pickaxe, rather than the axe.}}
{{History|||snap=13w02b|Hoppers now treat large [[chest]]s properly, no longer needing two hoppers connected to them to fill up the entire [[inventory]].
|Hoppers no longer take [[item]]s from containers when powered via a [[redstone]] current.
|Hoppers now display correctly as a [[drops|dropped]] or [[item frame|frame]] [[item]].}}
{{History|||snap=13w03a|Hoppers are now used to [[crafting|craft]] a [[minecart with hopper]].
|Hoppers can now empty a [[minecart with hopper]].}}
{{History|||snap=13w04a|The transfer rate of hoppers has been changed from 7 to 8 [[game tick]]s per [[item]] (2.5 items per second).}}
{{History||1.5.1|snap=pre|Hoppers now take empty [[bucket]]s out of furnace fuel slots.}}
{{History||1.7.2|snap=release|[[File:Hopper (D) JE3.png|32px]] [[File:Hopper (N) JE3.png|32px]] [[File:Hopper (E) JE3.png|32px]] [[File:Hopper (S) JE3.png|32px]] [[File:Hopper (W) JE3.png|32px]] [[File:Hopper (U) JE3.png|32px]] The UV of all blocks is broken on certain sides as a result of {{bug|MC-37106}} (few cases are listed on the wiki so far - this is a future project). This includes hoppers.}}
{{History||1.7.4|snap=13w47a|[[File:Hopper (D) JE4.png|32px]] [[File:Hopper (N) JE4.png|32px]] [[File:Hopper (E) JE4.png|32px]] [[File:Hopper (S) JE4.png|32px]] [[File:Hopper (W) JE4.png|32px]] [[File:Hopper (U) JE4.png|32px]] MC-37106 has been fixed, reverting hoppers to their pre-1.7.2 appearences.}}
{{History|||snap=13w48a|This version fixed {{bug|MC-190}}, which hoppers were allegedly subject to since their introduction. However, a comparison of hopper UV in 13w02a and 14w08a failed to reveal any visible differences, even accounting for the example images on the ticket. More research is needed on this matter.}}
{{History||1.8|snap=?|Hoppers no longer generate [[multiplayer]] lag when idle.}}
{{History|||snap=14w10a|[[File:Hopper (D) JE5.png|32px]] [[File:Hopper (N) JE5.png|32px]] [[File:Hopper (E) JE5.png|32px]] [[File:Hopper (S) JE5.png|32px]] [[File:Hopper (W) JE5.png|32px]] [[File:Missing Model JE2.png|32px]] Hoppers now use block models rather than having a hardcoded shape. This brings multiple changes: the inside texture now rotates with the hopper rather than being constant, the inside planes of hoppers are now shaded/have ambient occlusion, and some minor UV changes have occurred, notably on the smallest cuboid. The directionless hopper also [[Missing model|no longer has a model]].}}
{{History|||snap=14w26a|The directionless hopper has been removed.}}
{{History|||snap=14w31a|Hoppers now no longer use wood [[sound]]s.<ref>{{bug|MC-5991}}</ref>}}
{{History||1.9|snap=15w33c|A hopper now generates as a part of the [[end ship]] in the [[end city|end cities]].}}
{{History|||snap=15w41a|End ships no longer contain a hopper.}}
{{History|||snap=15w43a|[[Loot table]]s have been added; hoppers can now use loot tables.}}
{{History|||snap=15w43c|[[File:Hopper (D) JE6.png|32px]] [[File:Hopper (N) JE6.png|32px]] [[File:Hopper (E) JE6.png|32px]] [[File:Hopper (S) JE6.png|32px]] [[File:Hopper (W) JE6.png|32px]] The UV on the hopper model has changed, resulting in minor differences, particularly to the smallest cuboid. This is likely due to the fix for {{bug|MC-73401}}.}}
{{History|||snap=15w44a|[[File:Hopper (D) JE7.png|32px]] [[File:Hopper (N) JE7.png|32px]] [[File:Hopper (E) JE7.png|32px]] [[File:Hopper (S) JE7.png|32px]] [[File:Hopper (W) JE7.png|32px]] A mapping issue introduced in the previous snapshot for the sides of the large funnel region has been fixed. This may be due to the fix for {{bug|MC-50344}}.}}
{{History||1.9.1|snap=pre1|A hopper can now push into and pull [[item]]s from a blocked [[chest]].}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[block]]'s numeral ID was 154.}}
{{History||1.14|snap=18w43a|[[File:Hopper (D) JE8.png|32px]] [[File:Hopper (N) JE8.png|32px]] [[File:Hopper (E) JE8.png|32px]] [[File:Hopper (S) JE8.png|32px]] [[File:Hopper (W) JE8.png|32px]]<br>[[File:Hopper (item) JE3 BE2.png|32px]] The textures of hoppers have been changed.}}
{{History|||snap=19w03c|Hoppers now use correct cullface arguments, and some redundant faces have also been deleted.}}
{{History||1.19|snap=22w13a|Hoppers no longer drop when breaking a [[minecart with hopper]].}}
{{History||1.19.4|snap=23w07a|Hoppers can now interact with jukeboxes.}}

{{History|pocket alpha}}
{{History||v0.14.0|snap=build 1|[[File:Hopper (D) JE2.png|32px]]{{verify|Is this model correct?}}<br>[[File:Hopper (item) JE2 BE1.png|32px]] Added hoppers. Upward hoppers also exist.}}
{{History||v0.15.0|snap=build 1|Hoppers can now be moved by [[piston]]s.}}
{{History|bedrock}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Hopper (D) BE.png|32px]] [[File:Hopper (N) BE.png|32px]] [[File:Hopper (E) BE.png|32px]] [[File:Hopper (S) BE.png|32px]] [[File:Hopper (W) BE.png|32px]] [[File:Hopper (U) BE.png|32px]]<br>[[File:Hopper (item) JE3 BE2.png|32px]] The textures of hoppers have been changed.}}
{{History||1.19.70|snap=beta 1.19.70.20|Hoppers can now collect items through all blocks that have a lower height than a full block.}}

{{History|console}}
{{History||xbox=TU19|xbone=CU7|ps=1.12|wiiu=Patch 1|switch=1.0.1|[[File:Hopper (D) JE2.png|32px]]{{verify|Is this model correct?}}<br>[[File:Hopper (item) JE2 BE1.png|32px]] Added hoppers.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Hopper (D) JE8.png|32px]]{{verify|Is this model correct?}}<br>[[File:Hopper (item) JE3 BE2.png|32px]] The textures of hoppers have been changed.}}
{{History||ps=1.91|Hoppers can now fill [[composter]]s.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Hopper (D) JE2.png|32px]]{{verify|Is this model correct?}}<br>[[File:Hopper (item) JE2 BE1.png|32px]] Added hoppers.}}
{{History|foot}}

==Issues==
{{Issue list}}

==Trivia==
* A [[wikipedia:Hopper (particulate collection container)|real-world hopper]] is a large, pyramidal or cone-shaped container used in industrial processes to hold particulate matter, like dust, gravel, nuts, seeds, etc., and can then dispense them from the bottom.
* A hopper can transfer 9000 items per hour, or 150 items per minute.

==Gallery==
=== Renders ===
<gallery>
Hopper (N).png
Hopper (E).png
Hopper (S).png
Hopper (W).png
</gallery>
<gallery>
Hopper (N) BE.png
Hopper (E) BE.png
Hopper (S) BE.png
Hopper (W) BE.png
</gallery>

=== Screenshots ===
<gallery>
File:Hopper screenshot 1.png|In snapshot 13w01a, the hopper item uses a 'WIP' sprite, though the item still read "Hopper".
File:13w02a Banner.png|The 13w02a Banner includes a [[minecart with TNT]]  and a hopper.
</gallery>

==References==
{{Reflist}}

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

[[Category:Mechanisms]]
[[Category:Redstone mechanics]]
[[Category:Mechanics]]
[[Category:Storage]]
[[Category:Utility blocks]]
[[Category:Manufactured blocks]]
[[Category:Block entities]]

[[cs:Násypka]]
[[de:Trichter]]
[[el:Hopper]]
[[es:Tolva]]
[[fr:Entonnoir]]
[[it:tramoggia]]
[[ja:ホッパー]]
[[ko:호퍼]]
[[nl:Trechter]]
[[pl:Lej]]
[[pt:Funil]]
[[ru:Загрузочная воронка]]
[[uk:Лійка]]
[[zh:漏斗]]</li></ul>
14w25aAdded Elder Guardians.
14w26aGuardians and Elder Guardians are no longer immune to lava and fire.

Trivia

  • Elder Guardians can be spawned using /summon Guardian ~ ~ ~ {Elder:1, Attributes:[{Name:generic.maxHealth, Base:80}]}.
    • Using only /summon Guardian ~ ~ ~ {Elder:1} will spawn an Elder Guardian with 30 HP, the same HP as a normal Guardian.
  • An Elder Guardian spawner can be placed by inputting into a command block the following command: /setblock x y z mob_spawner 0 replace {EntityId:Guardian,SpawnData:{Elder:1, Attributes: [{Name:generic.maxHealth, Base:80}]}}
    • Note: The coordinate parameters (x y z) must be changed to the desired coordinates, using (~ ~ ~) will replace the command block with the spawner.
      • This makes for a renewable source of Wet Sponges and Sponges.
  • They are the second mob to drop a block upon death, after the sheep (drops wool).

Gallery

Advertisement