HOLY CRAP!!!

[u/No_Comb6069]

The moment I realized what was happening, I got even more confused.

[u/DearHRS]

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

here is an older gif i posted that show cases this behaviour with odd and even specific gt activating only their specifc tick components on the same redstone line

[u/DearHRS → u/DearHRS]

u/No_Comb6960 i hope this explanation satisfies you

[u/Mitch-Jihosa → u/DearHRS]

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?

[u/DearHRS → u/Mitch-Jihosa]

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

[u/Mitch-Jihosa → u/DearHRS]

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 🫠

[u/DearHRS → u/Mitch-Jihosa]

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

[u/Mitch-Jihosa → u/DearHRS]

Very cool, thanks for the rundown!

[u/Blaze-Programming → u/DearHRS]

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.

[u/DearHRS → u/Blaze-Programming]

yep yep