I genuinely enjoy the imagery of an observer getting so briefly excited it momentarily shits itself energy for a tick and immediately regains stoic composure
For those wondering what condition the observer checks, it typically reads the *blockstate* in front of it. A blockstate is a variable containing data on the block at that XYZ position which is used to change how certain blocks behave, how they look, and (you guessed it) to detect changes at a point. When the block in front of an observer is removed, placed, or updated through some behavior or player interaction. The data in the blockstate is changed, which is detected by the observer resulting in it sending a signal behind it. Also, the data within the observer's blockstate is changed when it detects something, which is why you can chain observers.
@@Uranium-jj7leI think that goes back as far as introducing blockstates, there's no way it COULD give a pulse without it unless it just...didn't have blockstates...which is impossible
@@GeeBeeOhThree is correct here. "Powered" is considered a block state property, and it's this property that a lot of redstone blocks check for...redstone power (along with another property for signal strength, for those blocks that use it). All rails use the same state properties, too (the non-cornering being a restricted subset). Crop ages are similar, though there are like six variants (based on the max age value). Gravity blocks falling is--likewise--due to the block turning into an entity (just like TNT). As far as the observer is concerned, the block ceased to exist, just as if it was destroyed. The campfire cooking items being placed and removed *isn't* a blockstate change, even though it involves a visual update. Because there are many kinds of cookable food (and mods can add them), that information isn't encoded in the blockstate (the list of valid states cannot be altered), but rather in the block entity itself as inventory. Those inventory items are then specially rendered by the entity renderer (which basically delegates back to the item renderer, with some transformations so it appears in the desired location and rotation). Chest opening/closing is handled even more differently, though I forget exactly how it works. Some data is stored in the block entity, but its animation state is separate from that iirc. Comparators and the trapped chest outputting a redstone signal is bespoke logic.
1. Redstone ore doesn't power when you place a block against it, only when you right or left click it. This is noticeable when you shift-click a block against it. 2. You forgot the dragon egg. 3. Pistons heads aren't oberved when trying to retract slime over pull limit. 4. When you clip the end of some plants, it is detected.
One major thing observers can't detect is rapid changes, which breaks most age based farms, or fast tick block streams. Other items it can't detect is the creation of the nether portal block (lighting a nether portal), change text color of signs, left clicking a note box (in survival plays it but not detect).
Changing the color of a sign is probably because you're not changing the block itself, but rather it's tile entity, which I guess doesn't create a block update
My two favourite are string when an entity enters or leaves it's hitbox, and note blocks when you change the instrument underneath. I used the string one to make an automatic water dispenser for the riptide enchantment. When you stand in it, it dispenses water at your feet so you can riptide, and then when you leave, it triggers the dispenser again, getting rid of the water. I've never really used the note block one, but it's a neat mechanic which can help you distinguish between blocks in some scenarios, like a block stream. Edit: |-_-|
Genuinely couldn’t believe how small this channel was. Video quality is amazing and it’s clear you put a lot of time and effort into this video!! I’ll be glad to be along the ride do you getting famous because this deserves more recognition!
9:17 it should also detect when the sponge evaporates :) It's not just a furnace recipe, it happens automatically in the Nether. The string thing is really cool, as you don't need a more visible tripwire hook setup to activate it getting walked on. The hard part is now to hide the observer 🤔
I thought about adding that, but it happens so instantly that the observer doesn't have a chance to detect it. It's still on cool down from detecting you placing it.
a common denominator for most of these are blocks and block states, anything that changes a block state (stair shape), or the block entirely (dirt turning to grass), there are some exceptions to this rule
@@noxmore There aren't any exceptions as far as I know, the Observer activates whenever the block in front of it changes state. (Whenever its updateShape() method is called by a block changing in front of it)
I already knew what the observer is used for but I must admit that some of these where new to me (like the scaffolding or the leaves), thank you for this amazing lesson professor |-_-|
I would categorize updates a bit differently, since lots of interactions could be described as "replacing an observed block", like when blocks are turned into moss or (cobble)stone from lava and water interactions, "changing amount" for turtle eggs, sea pickles or candles, or being more concise with grouping all "growable" blocks (crops, trees, bamboo, etc) into one category, but it's a good video nonetheless C:
For sure, that's what's going on behind the scenes with a lot of these. But I wanted to present it in a way that's easiest to understand for most people. Plus, the effect is the same whether you think of a sapling being replaced by a log or it growing. Totally understand where you're coming from tho.
Behind the scenes, I'm almost certain all of these are the BlockState changing. Each of these blocks have multiple possible states they can occupy (for example, a slab block can be lower half, top half, and a double slab). Interestingly, changing a block to an entirely different block and just changing its state are internally very similar, and in both cases the function that Observers listen for is called. If you want to play around with this, you can try using the Debug Stick to manually alter the state of any block and see the combinations for yourself.
Very informative video. The title puts me in mind of a passage from Philip k. Dick's "A Scanner Darkly". "What does a scanner see? he asked himself. I mean, really see? Into the head? Down into the heart? Does a passive infrared scanner like they used to use or a cube-type holo-scanner like they use these days, the latest thing, see into me - into us - clearly or darkly? I hope it does, he thought, see clearly, because I can't any longer these days see into myself."
my theory about the shulker box activating twice is that it is activated once for the actual opening / closing function and once for the visual changing of the block
I think really the box is updating its shape over and over (think of what happens if you stand on one as it is opening) and the observer pulses slowly enough that it happens to only go off twice
Beds: An observer will notice when a bed is occupied or not. It sends an output when a player, a villager, or a villager child sleeps, and when they get out of bed. It will not trigger if the child jumps on the bed, nor if a cat sleeps on it.
Its actually pretty simple. |-_-| detect block state changes, i.e. if you open F3 the things at the lower right when looking at blocks. Block state changes also include blocks changing outright, like converting grass to dirt, because they are 2 distinct blocks.
I have no plans of concocting complicated redstone contraptions myself, but the knowledge of the extent of what the |-_-| can do ought to be somewhat useful 👍
With banner placement, I think the most sane explanation is that the observer "sees" the airblock changing state, such as "placing stuff on the wall" and "placing stuff on the ground".
Etho pointed out another thing that causes observers to fire: fire blocks. In episode 582 of his letsplay around the 14:16 mark, he shows that a newly lit fire causes observers to randomly fire for a couple minutes or so.
I would presume it would make more sense for every block to be a subject and notify any observers next to it. So observer pattern for sure. That's probably why it was named as such honestly.
I just noticed, the observer looks like it’s doing what in Switzerland is known as the Swiss glare, if you see someone do something weird you stare at them like that, and everyone here does it.
Basically the observer can detect whenever a block changes one of its properties For example, scaffolding has a property called "distance", when you change its value, observer detects that; wall changes its shape, observer detects that as well; note block changes its instruments by placing a block below, observer also detects that.
basically, what it's detecting is a change in *block state*. this includes almost anything that changes the appearance of a block, and a few other things. if you can see it change in the "targeted blocK' segment of the f3 menu, the observer can see it too.
I think there might be a few extra things the observer can detect that don’t have an associated block state but I could be wrong But it’s kinda funny that this whole video can be summarised as ‘when it changes block state’ Still a great watch though
@@OvercastWarmth i don't think so, but we're curious if you know any counterexamples? everything in the video is a block state change (this includes changing what the block even is)
Basically everything that causes a block update. This can be the block completely changing to a different one, like when stripping a log, or when its NBT data changes, like fences changing their state or saplings changing their growth state. Everything in this video falls under those two rules. So it would be a lot more interesting to point out any exceptions to those two rules (if there are any).
Block state changes are not actually the same as block updates, they refer to slightly different things. Also, when you said NBT, you were talking about block properties changing. NBT is not detected. Also, Shulker Boxes don't fit.
Basically, it detects any changes to BlockState (e.g., Waterlogging, Signal Strength, Collision, Texture; including completely changing the block) but ignores changes to TileState (e.g., Chest Opening). Comparators do the opposite. Instead of BlockState, it's TileState and vice versa, and instead of state change, it's the current state. Some BlockStates also change alongside TileState, so you may get special cases too. Also, you missed Sponge-Drying (Nether [Java and Bedrock] and Desert [Bedrock]).
I have one small correction! When you break string attached to a tripwire hook, if you use Shears, it doesn't produce a Redstone signal. Therfore, in that case, the observer would only detect one update, not two
That's awesome! It really helped clear up for me what exactly am observer does... Now I just need one for comparators 😆 the block update pattern for the scaffolding is super interesting and pretty, I might wanna try making something with it... Also, here's your observer: [ō_ō]
In bedrock edition observed cannot detect 1. Redstone dust shape changes. 2. Leaves when logs are removed or placed next to them. 3. Note block when powered or depowered. 4. Note block when block changes beneath it. 5. When a plant grows without changes it shape naturally.(Gets detected with bonemeal) Well there were 100 of different things that observer couldn't detect before 1.18 but got fixed after the update.
The chest etc. probably don't trigger the observer because they are "tile entities", so technically not blocks. Although that would mean that shulker boxes shouldn't trigger them either, sooo…
I have thought of an amazing redstone invention. An observer in front of a tnt and when it ignites, the signal goes to a dispenser to cover the area with water so the tnt doesn't damage anything. The signal is doubled and delayed so the water can get rescooped. I'm going to patent this.
Nearly very block can be powered and unpowered and it can detect that, what you seeing with the bell is it being powered and then unpowered by the button, thats why it doesnt detect you hitting it manually. Thats also whats happening with the target block, its not detecting getting hit, its detecting being turned on, which happens to be when it gets hit. Also when the falling blocks fall, its not detecting them landing or falling, its detecting the bock in front of them changing to and from air respectively
for sponges... In case you put a wet sponge in the nether in front of an observer, will it send two signals? One for putting the block and another for it drying out
Honestly this just makes me want to make a lot of random interactions trigger a ding, imagine a little ping every time you turn a page in a lectern book lmao
For everyone saying oh so it just detects block updates. No. It actually doesn't detect block updates. It detects block state changes/the block being placed/removed. There is a difference. From the wiki: "Because observers in Java Edition detect changes in the block state, and not block updates, they can detect a wider range of phenomena than a block update detector (BUD) circuit in Bedrock Edition can detect (as some block state changes don't cause block updates). 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. "
0:28 hey, that’s Dankpods „headphone comparison“ song! I know it’s just from the RUclips creator library, but I can’t not think about the Huh-duh Six-hungeos
Can't you make an observer detect the growth of a cactus by placing the observer above the cactus facing its top face, but with an air block between the top of the cactus and the observer? That way the cactus will grow and then instantly break, which will be detected
Observers detect when the block type or block state changes, but not when the block’s NBT data changes. Rule: If you see the change on the right side of the F3 screen, the observer sees it too.
Well, by what the Observer is, it's actually completely consistent, though unintuitive. The reason is that Chests do not use a block state for the opening animation, but Barrels do use a block state for the open texture. Observers specifically detect block state changes so they only detect Barrels opening.
some of these (like when cobblestone is generated) are because it's a different block being 'placed' in front of the observer. also, the bell one is because of the redstone signal change and not the act of the bell ringing.
also, the one with the log and the leaves is really useful for a bamboo farm, because you can use observers to detect when a bamboo grows tall enough, and use a piston to push a log down onto some leaves, triggering more observers under the leaves to activate a row of target blocks that relay the signal to another row of pistons, knocking down the grown bamboo. super easy to build. oh, and the collection can be a minecart hopper going back and forth underneath and depositing it all to a chest. the target blocks also double as a way to shut down the farm if need be.
Technically you missed one with cactus albeit it falls under the same category as the sponge in nether, it can detect when it grows if placed above where the next piece of cactus will grow up to, and I presume though I’m not 100% sure that if you place it next to that same block that it will also detect it growing but will either overlap or double ping with the block breaking
I genuinely enjoy the imagery of an observer getting so briefly excited it momentarily shits itself energy for a tick and immediately regains stoic composure
At this point, a list of what the observers *can't* detect would be more useful
Minecarts passing by, unfortunately
@@TrialBySquirethey aren't block updates, and you have detector rails for that purposr
@@TrialBySquireno f*cking way
Bedrock Edition observers detect much less than Java.
@@TrialBySquireit can if you use a detector rail
"when it grows" my fav line of this video
When it gross
what i say when she asks "when can we start?"
when does he say that
@@ryguy-qh2qk 5:45 6:51
When he said "when it grows" I felt that too. Who else?
For those wondering what condition the observer checks, it typically reads the *blockstate* in front of it. A blockstate is a variable containing data on the block at that XYZ position which is used to change how certain blocks behave, how they look, and (you guessed it) to detect changes at a point. When the block in front of an observer is removed, placed, or updated through some behavior or player interaction. The data in the blockstate is changed, which is detected by the observer resulting in it sending a signal behind it.
Also, the data within the observer's blockstate is changed when it detects something, which is why you can chain observers.
>Observer checks changes in blockstates
Observer when observing a change, changes its blockstate
Thank you random mojang dev
@@Uranium-jj7leI think that goes back as far as introducing blockstates, there's no way it COULD give a pulse without it unless it just...didn't have blockstates...which is impossible
@@GeeBeeOhThree is correct here. "Powered" is considered a block state property, and it's this property that a lot of redstone blocks check for...redstone power (along with another property for signal strength, for those blocks that use it). All rails use the same state properties, too (the non-cornering being a restricted subset). Crop ages are similar, though there are like six variants (based on the max age value).
Gravity blocks falling is--likewise--due to the block turning into an entity (just like TNT). As far as the observer is concerned, the block ceased to exist, just as if it was destroyed.
The campfire cooking items being placed and removed *isn't* a blockstate change, even though it involves a visual update. Because there are many kinds of cookable food (and mods can add them), that information isn't encoded in the blockstate (the list of valid states cannot be altered), but rather in the block entity itself as inventory. Those inventory items are then specially rendered by the entity renderer (which basically delegates back to the item renderer, with some transformations so it appears in the desired location and rotation).
Chest opening/closing is handled even more differently, though I forget exactly how it works. Some data is stored in the block entity, but its animation state is separate from that iirc. Comparators and the trapped chest outputting a redstone signal is bespoke logic.
1. Redstone ore doesn't power when you place a block against it, only when you right or left click it. This is noticeable when you shift-click a block against it.
2. You forgot the dragon egg.
3. Pistons heads aren't oberved when trying to retract slime over pull limit.
4. When you clip the end of some plants, it is detected.
If you're referring to the dragon egg teleporting, then yes I did overlook that. Also, I did not know that about piston heads, thanks!
@@jazziiRed they are refering to how in Java Edition, certain plants stop growing if shears are used on the tip.
One major thing observers can't detect is rapid changes, which breaks most age based farms, or fast tick block streams. Other items it can't detect is the creation of the nether portal block (lighting a nether portal), change text color of signs, left clicking a note box (in survival plays it but not detect).
Changing the color of a sign is probably because you're not changing the block itself, but rather it's tile entity, which I guess doesn't create a block update
My two favourite are string when an entity enters or leaves it's hitbox, and note blocks when you change the instrument underneath.
I used the string one to make an automatic water dispenser for the riptide enchantment. When you stand in it, it dispenses water at your feet so you can riptide, and then when you leave, it triggers the dispenser again, getting rid of the water.
I've never really used the note block one, but it's a neat mechanic which can help you distinguish between blocks in some scenarios, like a block stream.
Edit: |-_-|
That's a nice little contraption. I like it! |-_-|
Observers are more like [-.-_-.-] i think
|т_т|
Heard of pressure plates?
@@F17A pressure plates have to be placed on full blocks, string is more versatile
Genuinely couldn’t believe how small this channel was. Video quality is amazing and it’s clear you put a lot of time and effort into this video!! I’ll be glad to be along the ride do you getting famous because this deserves more recognition!
Thank you! Glad to have you here :)
I agree
Such a criminally underrated channel, you deserve so much more attention |-_-|
Thank you! |-_-|
so true
@@jazziiRed just take all my subs im not worthy for them like u
true
yes
9:17 it should also detect when the sponge evaporates :) It's not just a furnace recipe, it happens automatically in the Nether.
The string thing is really cool, as you don't need a more visible tripwire hook setup to activate it getting walked on. The hard part is now to hide the observer 🤔
I thought about adding that, but it happens so instantly that the observer doesn't have a chance to detect it. It's still on cool down from detecting you placing it.
@@jazziiRed Could that and the cactus limitation be bypassed by commands?
probably
@@Nulono I think as long as the cactus is not updated. But it should destroy itself when its updated.
@@jazziiRed iirc, sponges dry out slowly in deserts, badlands, and maybe savannas too
Edit: missed the Bedrock only disclaimer on the wiki
6:05 "Just play around with it, it gets excited easily" I caught that ;)
Basically a redstone ore block is just an observer extension right? It observes more than an observer
@@GingerMoony Never thought of it that way, but I guess so yes!
@@GingerMoony nope, only entities
Disclaimer: It cannot see your pain
a common denominator for most of these are blocks and block states, anything that changes a block state (stair shape), or the block entirely (dirt turning to grass), there are some exceptions to this rule
I thought this was the only rule, what are the exceptions?
(also blocks changing entirely count as block state changes internally)
@@noxmore There aren't any exceptions as far as I know, the Observer activates whenever the block in front of it changes state. (Whenever its updateShape() method is called by a block changing in front of it)
@@hyper_lynx yeah that's what i thought as well
I already knew what the observer is used for but I must admit that some of these where new to me (like the scaffolding or the leaves), thank you for this amazing lesson professor |-_-|
You're very welcome |-_-|
I would categorize updates a bit differently, since lots of interactions could be described as "replacing an observed block", like when blocks are turned into moss or (cobble)stone from lava and water interactions, "changing amount" for turtle eggs, sea pickles or candles, or being more concise with grouping all "growable" blocks (crops, trees, bamboo, etc) into one category, but it's a good video nonetheless C:
For sure, that's what's going on behind the scenes with a lot of these. But I wanted to present it in a way that's easiest to understand for most people. Plus, the effect is the same whether you think of a sapling being replaced by a log or it growing. Totally understand where you're coming from tho.
Behind the scenes, I'm almost certain all of these are the BlockState changing. Each of these blocks have multiple possible states they can occupy (for example, a slab block can be lower half, top half, and a double slab).
Interestingly, changing a block to an entirely different block and just changing its state are internally very similar, and in both cases the function that Observers listen for is called.
If you want to play around with this, you can try using the Debug Stick to manually alter the state of any block and see the combinations for yourself.
ok but the vertical walls, leaves and scaffolding ones are EXTREMELY interesting, i could defo see some potential for those
leafstone and scaffolding is useful for compact vertical/twisted lines and walls and powered rails are useful for instant transmission.
Nobody:
Almost every Natural Block: When it grows.
Coral: When it dries up and dies.
Very clear and fun to watch. Great videos!
Thanks!
The observers can activate also when leaves are "charged" by wood. Nice video too!
Observers can observe "block state changes" so any block that you can directly interact with or natural game state changes.
You're gonna be huge someday!
Awesome Job dude... I love everything about this video
Thanks!
Very informative video. The title puts me in mind of a passage from Philip k. Dick's "A Scanner Darkly".
"What does a scanner see? he asked himself. I mean, really see? Into the head? Down into the heart? Does a passive infrared scanner like they used to use or a cube-type holo-scanner like they use these days, the latest thing, see into me - into us - clearly or darkly? I hope it does, he thought, see clearly, because I can't any longer these days see into myself."
my theory about the shulker box activating twice is that it is activated once for the actual opening / closing function and once for the visual changing of the block
I think really the box is updating its shape over and over (think of what happens if you stand on one as it is opening) and the observer pulses slowly enough that it happens to only go off twice
Beds:
An observer will notice when a bed is occupied or not. It sends an output when a player, a villager, or a villager child sleeps, and when they get out of bed. It will not trigger if the child jumps on the bed, nor if a cat sleeps on it.
for those wondering, the music at 4:20 is Mozart symphony number 38 in d major and I believe the 3rd movement
Its actually pretty simple. |-_-| detect block state changes, i.e. if you open F3 the things at the lower right when looking at blocks. Block state changes also include blocks changing outright, like converting grass to dirt, because they are 2 distinct blocks.
Yep, that's the gist
I have no plans of concocting complicated redstone contraptions myself, but the knowledge of the extent of what the |-_-| can do ought to be somewhat useful 👍
90.3% done on your way to 10k, well deserved.
Thank you, I've been struggling to understand how flying machines work for the longest time. I didn't know observers could detect themselves moving. 👍
With banner placement, I think the most sane explanation is that the observer "sees" the airblock changing state, such as "placing stuff on the wall" and "placing stuff on the ground".
Observer is like a proud parent, it gets excited when you grow.
Damn I hope this guy catches on big time. What a quality channel
Etho pointed out another thing that causes observers to fire: fire blocks. In episode 582 of his letsplay around the 14:16 mark, he shows that a newly lit fire causes observers to randomly fire for a couple minutes or so.
Shower Thought: Does the Observer actually observe or is it subscribing and being notified? 🤔
I would presume it would make more sense for every block to be a subject and notify any observers next to it. So observer pattern for sure. That's probably why it was named as such honestly.
you are about to hit 10k , im part of the subbed before 10k club.
also well done for getting this far on yt!
Thank you!
Observer detects when you drop a like, when you leave a comment, when you start watching this video, when you return to this video
I don't see it as judgemental. I see it as extremely focused and determined.
The observer gets very excited when it sees the wood logs stripping.
I just noticed, the observer looks like it’s doing what in Switzerland is known as the Swiss glare, if you see someone do something weird you stare at them like that, and everyone here does it.
Basically the observer can detect whenever a block changes one of its properties
For example, scaffolding has a property called "distance", when you change its value, observer detects that; wall changes its shape, observer detects that as well; note block changes its instruments by placing a block below, observer also detects that.
"Disclaimer, it cannot see your pain" even with context is such an incredibly funny line (8:33)
basically, what it's detecting is a change in *block state*. this includes almost anything that changes the appearance of a block, and a few other things. if you can see it change in the "targeted blocK' segment of the f3 menu, the observer can see it too.
Yes, that is a great way to summarize it.
I think there might be a few extra things the observer can detect that don’t have an associated block state but I could be wrong
But it’s kinda funny that this whole video can be summarised as ‘when it changes block state’
Still a great watch though
@@OvercastWarmth i don't think so, but we're curious if you know any counterexamples? everything in the video is a block state change (this includes changing what the block even is)
@@SunroseStudios Shulker Boxes.
Just found your channel and am already in love. XD
Thanks!
Scaffolding and leaves were the most interesting to me, the rest were fairly straight forward since it's just BUD
I did know about string earlier, it's still super interesting to make a silent pressure plate, but since I already knew about it I didn't mention it
"There's. Nothing in front of you."
"So?"
I love the thumbnail so much lol
Basically everything that causes a block update. This can be the block completely changing to a different one, like when stripping a log, or when its NBT data changes, like fences changing their state or saplings changing their growth state. Everything in this video falls under those two rules. So it would be a lot more interesting to point out any exceptions to those two rules (if there are any).
Block state changes are not actually the same as block updates, they refer to slightly different things. Also, when you said NBT, you were talking about block properties changing. NBT is not detected.
Also, Shulker Boxes don't fit.
The way of editing this has needs more viewers here seriously
Already knew all of these cases, but still enjoyed watching the video. Your voice is nice and comforting :)
#whenitgrows
6:45 that might be useful for explaining why packing wood too close and leaving logs uncut might cause tree farm not work for noobs
Does it detect when you clip a plant with shears? Like when you click on the end of a weeping vine to make it stop growing?
I just checked, and it does. Good catch! You're the first to accurately find something I missed :D
That intro was amazing!
That propagating pattern with the scaffolding blocks could be very useful!
I think it would have been a lot easier to say what the observer can't see
Basically, it detects any changes to BlockState (e.g., Waterlogging, Signal Strength, Collision, Texture; including completely changing the block) but ignores changes to TileState (e.g., Chest Opening).
Comparators do the opposite. Instead of BlockState, it's TileState and vice versa, and instead of state change, it's the current state.
Some BlockStates also change alongside TileState, so you may get special cases too.
Also, you missed Sponge-Drying (Nether [Java and Bedrock] and Desert [Bedrock]).
I have one small correction! When you break string attached to a tripwire hook, if you use Shears, it doesn't produce a Redstone signal. Therfore, in that case, the observer would only detect one update, not two
Basically, any non-continuous block flag changing state or value including the block type. Things that can be found cleanly listed in the F3 menu.
this video is only 18 minutes long and yet it felt longer than a lot of 2 hour long videos i have watched
Thank you so much for this, fantastically edited & presented. Makes me happy that the Minecraft redstone tutorial community is still going strong.
This is such a great minecraft channel！
Your channel is soo cool, i wonder when it *will grow*
That's awesome! It really helped clear up for me what exactly am observer does... Now I just need one for comparators 😆
the block update pattern for the scaffolding is super interesting and pretty, I might wanna try making something with it...
Also, here's your observer: [ō_ō]
Oh wow that's an even better observer face [ō_ō]
In bedrock edition observed cannot detect
1. Redstone dust shape changes.
2. Leaves when logs are removed or placed next to them.
3. Note block when powered or depowered.
4. Note block when block changes beneath it.
5. When a plant grows without changes it shape naturally.(Gets detected with bonemeal)
Well there were 100 of different things that observer couldn't detect before 1.18 but got fixed after the update.
i really love your videos!!! i didn't understand nothing about observers before watching this, but now i will make a watermelon farm!! xD
Glad I could help!
I learned stuff that are off-topic. Such as lighting off the candles, scaffolding changing texture when it has no support, etc.
Good video, can't wait for when it grows.
Alternative title: List of block tick updates
I wonder if this video will inspire some interesting lock mechanisms
An adventure map all about the Observer's birthday
I think I had something important to do, but I think there's nothing more important than watching this video.
The chest etc. probably don't trigger the observer because they are "tile entities", so technically not blocks. Although that would mean that shulker boxes shouldn't trigger them either, sooo…
6:18 I completely forgot about this mechanic and it's just what I need (I think) for something I'm making!
I have thought of an amazing redstone invention. An observer in front of a tnt and when it ignites, the signal goes to a dispenser to cover the area with water so the tnt doesn't damage anything. The signal is doubled and delayed so the water can get rescooped. I'm going to patent this.
The "when it grows" saga has changed me.
I must say This Video is Amazing, but The Thumbnail is *Legendary*
Crazy list. A simple "all block Updates" would probably be the quicker answer though 😂
Nearly very block can be powered and unpowered and it can detect that, what you seeing with the bell is it being powered and then unpowered by the button, thats why it doesnt detect you hitting it manually. Thats also whats happening with the target block, its not detecting getting hit, its detecting being turned on, which happens to be when it gets hit.
Also when the falling blocks fall, its not detecting them landing or falling, its detecting the bock in front of them changing to and from air respectively
“It was so boring I couldn’t stop watching”
for sponges... In case you put a wet sponge in the nether in front of an observer, will it send two signals? One for putting the block and another for it drying out
Honestly this just makes me want to make a lot of random interactions trigger a ding, imagine a little ping every time you turn a page in a lectern book lmao
I was expecting you to go into the source code of the observer and literally tell us what it actually sees, but awesome video dude!
Simple explanation for natural blocks: When something updates in front of it
14:26 what are you doing, step-observer?
So in other words, the block meant to detect block updates, detects block updates. Neat. good video though
It actually doesn't detect block updates. It detects block state changes. There is a difference. The wiki will help.
I unironically liked subscribed and hit the bell
Thanks and welcome aboard!
For everyone saying oh so it just detects block updates.
No.
It actually doesn't detect block updates. It detects block state changes/the block being placed/removed. There is a difference.
From the wiki:
"Because observers in Java Edition detect changes in the block state, and not block updates, they can detect a wider range of phenomena than a block update detector (BUD) circuit in Bedrock Edition can detect (as some block state changes don't cause block updates). 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. "
17:14 It took me SO long to get that joke but I love it!
I dont get it 😢
this is what i watch when i'm bored af and youtube has nothin to offer
0:28 hey, that’s Dankpods „headphone comparison“ song!
I know it’s just from the RUclips creator library, but I can’t not think about the Huh-duh Six-hungeos
9:16 it also notices when the wet sponge dries up in the nether (too quick to matter), or in the savanna and desert on bedrock edition
Can't you make an observer detect the growth of a cactus by placing the observer above the cactus facing its top face, but with an air block between the top of the cactus and the observer? That way the cactus will grow and then instantly break, which will be detected
Observers detect when the block type or block state changes, but not when the block’s NBT data changes.
Rule: If you see the change on the right side of the F3 screen, the observer sees it too.
11:52 this seems like a bug. it doesn't make sense that it can detect barrels opening/closing but not for chests which literally have moving parts
btw, i actually did not know about the mushroom block one. pretty cool
Well, by what the Observer is, it's actually completely consistent, though unintuitive. The reason is that Chests do not use a block state for the opening animation, but Barrels do use a block state for the open texture. Observers specifically detect block state changes so they only detect Barrels opening.
i freaking love your videos
some of these (like when cobblestone is generated) are because it's a different block being 'placed' in front of the observer. also, the bell one is because of the redstone signal change and not the act of the bell ringing.
also, the one with the log and the leaves is really useful for a bamboo farm, because you can use observers to detect when a bamboo grows tall enough, and use a piston to push a log down onto some leaves, triggering more observers under the leaves to activate a row of target blocks that relay the signal to another row of pistons, knocking down the grown bamboo. super easy to build. oh, and the collection can be a minecart hopper going back and forth underneath and depositing it all to a chest. the target blocks also double as a way to shut down the farm if need be.
Great video! Thank you
Technically you missed one with cactus albeit it falls under the same category as the sponge in nether, it can detect when it grows if placed above where the next piece of cactus will grow up to, and I presume though I’m not 100% sure that if you place it next to that same block that it will also detect it growing but will either overlap or double ping with the block breaking
take a shot everytime he says "when it grows"
Most of these could be combined into 2 categories.
Block ID change, Redstone power change
9:17 probably doesn't matter but when it dries in hot biomes and the nether, it detects it
missed title opportunity: "What does an Observer ACTUALLY Observe"