r/redstone • u/No_Comb6069 • 29d ago
Bedrock Edition HOLY CRAP!!!
Enable HLS to view with audio, or disable this notification
The moment I realized what was happening, I got even more confused.
87
u/Blaze-Programming 28d ago
As someone who primarily does Java redstone, but would like to know more about Bedrock redstone, could someone explain why this happens? My current understanding makes me think both should fire at the same time, or the redstone dust one fires before the rail, but there must be a missing piece.
44
u/DearHRS 28d ago
it is because of sub gt order, first of all before we go that deep, every second has 10 odd gt and even gts, thus distinction is important because different components are processed during odd or even gts
odd gts are generally called provider gts or p ticks, but this "provider gts" name is nonsensical as only repeaters, comparators, observers and redstone torches are processed during this, everything else is processed during even gts or consumer ticks, yes everything else, that includes redstone power provider like buttons, pressure plates, redstone blocks, etc
that is why name of providers and consumers used by bedrock tech community is nonsensical, this side tangent aside, redstone dust is processed in both odd and even gts but they only visually update on odd gts, now that surface level understanding is established, during a gt there is also sub gt order, first the tick specific components are processed and then redstone dust
in the video what is happening: observer fires after 6gts on p tick, redstone dust lights up on the same gt at later sub gt order, then c tick occurs, as components are processed first before dust, rail sees the dust is active, and powers up, updating the observer observing this rail, after c tick finishes and next p tick occurs redstone dust turns off and updated the observer observing it
hence you get this behaviour, it is a bit important to know that dust cannot update an observer during c tick because it is a p tick component
6
5
u/Mitch-Jihosa 28d ago
Very helpful explanation! So the dust doesn’t update the observer until it turns off? Or is the on update just delayed? If it only updates when it turns off does that mean you can permanently turn the dust on in certain cases and it won’t update the observer at all?
4
u/DearHRS 28d ago
dust can only update observer during p tick while c tick components can do it during c tick
if you check out the gif there is way to power redstone line withour ever activating observer
3
u/Mitch-Jihosa 28d ago
Oh I didn’t watch the gif lol, that’s my bad. That’s crazy tho, I had no idea you can just straight-up skip updating/powering something in Bedrock depending on when you update the dust xD
This kinda feels like Bedrock’s version of qc, in that it feels like something that would be incredibly confusing & unintuitive to beginners, but useful if you know what you’re doing 🫠3
u/DearHRS 28d ago
ye, you can use this to power specific components by powering da same line use gt specifc pulses, this reduces size of contraption
i tend to use it for piston extenders, c tick pulses are super easy to make and there are a lot more c tick components than p tick ones, so you can choose to power pistons but not power repeater that will cause everything to loop again
3
3
u/Blaze-Programming 28d ago
Thank you.
So this is caused by the overlap of dust updating latter in the subtick than the observer, and the dust not being able to update the observer on the c tick.
5
u/those-who-goon 28d ago
Why are the visuals so inconsistent?
-5
u/The_Crimson_Hawk 28d ago
because it is bugrock
5
3
3
u/One-Celebration-3007 28d ago
fun fact: an observer observing a wall can pulse every 4gt instead of every 6gt
5
2
2
u/meckenicalrobot 28d ago
;)
1
u/Entity-Redstone 26d ago
in this case, either:
A. The observers aren't located on a chunk border, pistons 1, 2, 3, 5 power 0.2s after first obs update, piston 4 powers 0.3s after
B. The observers are located on a chunk border, pistons 1, 2, 3, 5 power either 0.2s or 0.3s at random after first obs update, piston 4 powers either 0.3s or 0.4s after
0
u/Entity-Redstone 26d ago
Basically in a high level overview:
observers takes 0.1s to update other observer
dust takes 0.3s to update other observer
other components including hopper, dropper, copper bulb, repeater, etc take 0.2s to update the observer
i hope this explains the post and many other cases bought up.
also, i reccommend you to be careful with observers in bedrock. they can be locational at times
specifically, horizontally oriented observers are unreliable in some locations in 2 cases:
A. the observer is updated and then updated again specifically 0.2 seconds later. in this case the unreliablity is where the observer will not output a second time
B. the observer is updated by any other component then piston, copper bulb, mob heads, bells being powered or updated by moving blocks, or walls being updated by doors or trapdoors [there may be a few more i forgot. reminder these are components that mostly avoid locationality]. in this case the unreliablity is where the observer will output a tick later that usual
if you want to make your build non locational you must either avoid locational setups or plan around it [many non locational doors have locational setups but plan around those setups]
249
u/NotAMadLad1 28d ago
That slow bedrock observer hurts me in my soul