From Minecraft Wiki
Jump to: navigation, search





Blast resistance






Yes (64)





Data values

JE: dec: 218 hex: DA bin: 11011010
BE: dec: 251 hex: FB bin: 11111011



Duncan Geere Mojang avatar.png The observer is placed just like a piston - the direction that it's facing matters. An observer isn't quite omniscient, y'see - it has an arrow on the top that points in the direction of the block that it's observing. That can actually include another observer, so if you set two up pointing at each other then they'll endlessly beep on and off.
Duncan Geere[1]

An observer is a block that emits a redstone signal when an adjacent block is updated.

Obtaining[edit | edit source]

An observer requires a pickaxe to be mined. When mined without a pickaxe, it will drop nothing.

Hardness 3.5
Breaking time[note 1]
Hand 17.5
Wooden 2.65
Stone 1.35
Iron 0.9
Diamond 0.7
Golden 0.45
  1. Times are for unenchanted tools in seconds.

Crafting[edit | edit source]

Ingredients Crafting recipe
Cobblestone +
Redstone +
Nether Quartz

Usage[edit | edit source]

An observer is placed similarly to a piston, and will observe the block that it is placed against. The texture of the detecting side is that of an 'observing' face. As observers can detect the state of other observers, placing two adjacent observers, each watching the other, can make a fast and compact redstone clock.

Behavior[edit | edit source]

In Java Edition, an observer will detect changes in its target's block ID or data value, or the breaking or placing of a block (i.e. changes in its basic block state, but not its extended/actual block state). This means that changes like the age of crops will be detected, since they are part of the basic block state that is converted to metadata when the world is saved; however, changes such as the shape of a fence will not be detected, since those are part of the extended block state, which is not saved when the world is saved.

In Bedrock Edition, an observer acts as a block update detector, and detects anything that causes a block update in that edition.

Note that what causes a block update and how they propagate is very different between Java Edition and Bedrock Edition. As a result, each can detect some kinds of changes that the other can't. See the table below for a comparison.

When it detects something, the observer emits a redstone pulse of strong power at level 15 for 2 game ticks (1 redstone tick). The pulse can power redstone dust, a redstone comparator, a redstone repeaters, or any mechanism component located at its opposite end.

In the Java Edition, the pulse is emitted with a delay of 1 redstone tick. In Bedrock Edition, it is supposed to be delayed by 1 tick as well, but is actually delayed 2 redstone ticks due to MCPE-15793, a bug causing redstone delays to be incorrect when components are activated by world changes (which, in the case of the observer in MCPE, is the only way it can be activated), as opposed to pure redstone components ticking.

It also counts as a block change/block state change/block update when the observer itself is moved by a piston. When this happens, an observer emits a pulse after being pushed or pulled, but not beforehand.

Observers behave as a transparent block even though they block light. This means they cannot be powered by an external power source, nor power themselves with their own output.

Because observers in Java Edition detect changes in the basic block state, and not block updates, they can detect a wider range of phenomena than a block update detector (BUD) circuit in Java Edition can detect (as some block state changes don't cause block updates). However, they do not detect client-side blockstate changes that do not change the block data value, such as a fence reshaping or redstone dust rerouting. Observers in Bedrock Edition do detect block updates (but not block state changes), and so they detect the exact same things that any other BUD would detect in that edition.

Limitations[edit | edit source]

Block state change: Detected in Bedrock Edition Detected in Java/Console Editions

Locking / unlocking a redstone repeater

Changes to the data value of fire that signifies flammable surfaces surrounding fire

Changes in the shape of walls, fences, iron bars, glass panes, stairs, tripwire, redstone dust, vines, melon stem or pumpkin stem

A grass, mycelium, dirt, coarse dirt, or podzol block becoming snowy or not snowy

Changes to inventory of any blocks that comparators measure as containers

Activating / deactivating a beacon

Playing a note block

Opening and closing shulker boxes, chests & ender chests

Success of a command block

Teleporting something by the end gateway
Yes No

Adding / removing contents from a flower pot
Yes No

The opening/closing of the top part of a door by hand, as opposed to by redstone power.
Yes No

Powering / depowering of activator rails
Yes Yes

Inverting / deinverting a daylight sensor
Yes Yes

Activation of a dropper or dispenser
No Yes

Activation / deactivation of redstone torch
Yes Yes

Activation / deactivation of redstone ore
No Yes

A piston (not the head) extending or contracting
Yes Yes

Locking / unlocking a hopper
No Yes

Spread of grass to dirt, or decay of grass into dirt
No Yes

Growth of nether wart, forced growth of cocoa pods by bone meal, or growth of vines into empty space
Yes Yes

Aging of saplings, sugar canes or fire
No Yes

Farmland going through its hydration stages
No Yes

Moving potions and other items to / from a brewing stand
No Yes

Activation / deactivation of a dragon head
Yes No
All other block / block state changes Yes

Data values[edit | edit source]

Block data[edit | edit source]

See also: Data values and Bedrock Edition data values
DV Description
0 Facing down
1 Facing up
2 Facing south
3 Facing north
4 Facing east
5 Facing west

Block state[edit | edit source]

See also: Block states
Name Value Description

The direction the observer is observing. The same direction the player faces, when placing the block.

True while the observer is observing a change and emitting a pulse.

History[edit | edit source]

Official release
1.11 16w39a Added observer block. When first added, the observers acted as a block update detector, and would emit pulses that lasted 1 game tick (0.5 redstone ticks) and had a signal strength of 1. The observer could also power blocks (like a repeater). It also had no delay between detecting a block update and emitting a pulse, meaning that observers were essentially instant. They were also placed with the observing, or input, side facing the player.
Observer 16w39a.png Note: the "arrow" texture on the top/bottom of the observer was pointing the wrong direction (towards the input, rather than the output). This was not noticed by most people, though, since the observer in Pocket Edition had (and as of 1.0.0 still has) a texture bug where the top & side textures would not rotate properly (except the output/input sides), causing the arrow texture to always point in the same direction.
16w41a Observers were changed to emit 4 game tick (2 redstone tick) pulses[6], and their signal strength was changed to 15.[7][8]
Observers *appear* to no longer strongly power blocks, and now only emit activation power, like a block of redstone. (And this may have been the intended behavior for this snapshot.) However, in reality, they still strongly power blocks, but the blocks adjacent to those blocks aren't given block updates, causing weird and buggy behavior.[2]
Observers are now placed with the output facing the player.[3][4]
Fixed a bug where observers would redirect redstone dust from all 4 directions.[5] (They are only supposed to redirect dust from their output side.)
16w42a The devs attempted to make observers no longer detect block updates happening to air blocks, in order to make observer behavior more predictable.[9] In the process they broke redstone mechanics a bit, so that the block update bug from the previous snapshot now affected repeaters & comparators, too.[10]
16w43a Observer 16w43a.png Fixed the rotation of the "arrow" texture so it would point in the right direction.
General redstone mechanics work as they did before 16w42a, with the exception of the change named below.
Observers now output strong power like in 16w39a, except that they, as well as repeaters & comparators, no longer provide block updates to transparent blocks or air.
16w44a The block update changes relating to redstone from 16w42a & 16w43a were fully reverted.
Observer behavior was overhauled/redefined. The observer changed from a block update detector to a block state change detector. Observers were changed to detect when the block it was observing changed, its basic block state changed, or the block was placed/destroyed. (Note that it does not detect changes in the extended block state, AKA changes that are not saved when the world is unloaded, such as the shape of a fence, or whether or not a repeater is locked.) This change made observer behavior much more predictable, as unexpected/invisible block updates would no longer trigger observers.[11]
Observers were changed to emit a 2 game tick (1 redstone tick) pulse when activated.[12]
Observers no longer output power instantly.[13]
1.11-pre1 Observer.png Changed front (detecting side) texture to be an 'observing face'. The "arrow" texture on the top/bottom of the observer was also modified.
The redstone output side now blinks red when it outputs power.
Pocket Edition Alpha
0.15.0 May 2, 2016Jeb tweeted that Daniel Wustenhoff is a working on a BUD block.[15]
Tommaso Checchi tweeted his "rejected graphics" for the block.[14]
build 1 Observer PE.png Added observer block.
0.15.3 Observers are now placed like a piston and not a log.
Bedrock Edition
1.2 build 1 Observer BE.png Updated textures to match Java Edition.
Observer blocks can now detect many more block changes.
Increased the strength of the redstone pulse outputted by Observer blocks and they no longer pulse twice when observing a retracting piston.
Opening and closing the command block screen will no longer activate an observer block
Legacy Console Edition
TU54CU441.52Patch 24Patch 4Added observers.

Issues[edit | edit source]

Issues relating to “Observer” are maintained on the issue tracker. Report issues there.

Trivia[edit | edit source]

  • When moved by a piston, an observer sends a 2 game tick (1 redstone tick) pulse after being moved, which makes it useful for slime block flying machines.
  • The current Observer texture was created because Jeb kept confusing which side was front/back. He said it was inspired by the "rejected texture" created by Tommaso Checchi.[16][17]

Gallery[edit | edit source]

See also[edit | edit source]

References[edit | edit source]