[MC-157901] When you 1 tick a sticky piston pushing a redstone block, and wire redstone coming from the pushed redstone block into a piston psuhing the redstone block to its original place the redstone will not appear powered but it actually is

Put the summary of the bug you're having here

What I expected to happen was...:
The redstone should appear powered

What actually happened was....
The redstone wasnt powered

Steps to Reproduce:
1. One tick a sticky piston and put a redstone block on its face.
2. Wire redstone from next to where the redstone block will be after its pushed and to another piston that will push the block back.
3.You should see that the redstone will work but it will not seem powered

Linked issues

duplicates 1

MC-8328 Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update 'algorithm') Reopened

Attachments

2019-07-28_20-31-09.mp4

Comments 5

John 2019-07-28T10:47:17Z

I hope this gets fixed because it is affecting some of my redstone builds

RedCMD 2019-10-17T18:59:37Z

The output of this is indeed a 0tick pulse
The reason why you cant see it
is because the server skips sending the correct packets to the client
If you create a lot of network usage, you can see the 0tick pulse as a 1gt pulse (gametick)

John 2019-10-17T20:29:26Z

Ok thanks. Would it still be considered a bug though?

violine1101 2019-10-17T20:59:24Z

MC-8328 is still open, so yes.

RedCMD 2019-10-18T08:34:26Z

Is it still considered a bug?
0tick pulse - no
not being able to see it - sortof, it does turn on and off instantly, so it makes sense that you cant see it