*This issue in MC started from 18w10d.
So when lava or water is going to a flowing state, the observer normally detect the change and give a redstone pulse.
This behavior was very VERY useful for Compact Stone Generator and Tick-speed redstone delay circuit.
Now, because of the recent change with the water/lava update, the observer doesn't detect the updates from those.
Here is a quick view of what is happening now:
https://youtu.be/sM7fzp62V0E
*Accidentally left my micro off, no voice sound.
I would really like to see this issue get fixed. Because if a release of 1.13 come out and this is not fixed, many and many many redstone build would be broken.
(By the way, this issue is NOW very related (not duplicate) of the bug report MC-107664)
Linked issues
is duplicated by 2
Comments 7
@Neko. the reported "bug" of MC-109829 didn't got 'fixed' voluntary.
It got 'fixed' though, it more like got buged at the same time of the water update behavior ...
I really feel someone like @Grumm or @Dinnerbone or else should say his word about this.
Yes, some, SOME peoples reported this feature. And it's only because they don't work really much with redstone, that is why they are complaining about the fac it does that.
Do you remember around 1.12, the Random tick update was patched on lava/water (because of the issue that lava/water couldn't be use with water to make Redstone clock but it was rapidly reverted because some lava/water in cave could stay static)
See this part of this video: https://www.youtube.com/watch?v=FVr28VwAOkM&t=124s
(up to 2:46)
So all for saying this doesn't not work has intended now and this must get fix.
By the way, why are you sticking my bug report has related to MC-109829 It's not related.
My bug report is the total oposite of this one*
@unknown originally set MC-109829 to "Postponed", so it was likely going to be fixed. Observers are supposed to detect block state changes, not random ticks. Just because something is useful in redstone does not mean it's a feature.
I just did a quick video, just to show you it doesn't even detect any block state changes (lava/water going to a flowing state)
https://youtu.be/DU192xbPOnM
Observers are supposed to detect block state changes, not random ticks And it's what it was doing before 18w10d.*
The observers was detecting the change from static state to flowing state. Now it doesn't not anymore. (It doesn't not detect even when it's visually going to a side flowing state)
The real issue with MC-109829 was the fact that water/lava kept going to a flowing state/non-flowing state, because the redstone behind the observer kept retriggering the water/lava front the observer.
Here this issue is the fact that it doesn't even detect a single block state changes.
The water and lava changed to flowing_water/flowing_lava when it got any update; this meant that a few lava/water blocks next to each other kept changing each other to the flowing block; this was causing quite a bit of lag. Now the flowing water/lava blocks have been removed and it’s simply if lava/water gets an update it checks if it can flow, if it can’t, nothing happens, no neighbors update.
Observers detected the change to and from the flowing block, which has now been removed, as such there is nothing for the observer to see change aside from the level block state. There is no block state that controls the flowing animation or “am I updating”, as such observers can’t see that.
The random ticking fix still applies as it’d make the water/lava update randomly and flow faster or slower randomly, now that they aren’t ticked, the water/lava always flow with the same speed.
WAI, this was a bug (MC-109829).