sharir1701 | [Explanation] Redstone Update Order (The Elusive HashSet) - Very Advanced/Niche Redstone Mechanics @Sharir1701 | Uploaded 9 years ago | Updated 3 hours ago
Hey guys! Sharir1701 here and today I present my findings about redstone update order, very precisely. This can explain every single locational redstone quirk (spare one, working on it :P). Enjoy and let me know!

ilmango's Update Order Video: youtube.com/watch?v=1V9M8OIjjlM
Precise Redstone Timings: youtube.com/watch?v=cFoGmiySikA
Redstone Debug (+tickSpeed) Mod: youtube.com/watch?v=iP-YDUmJJEQ
Redstone Dust Update "Bug": youtube.com/watch?v=T3bST3JGgas

Dust Summary:
HashCode: (chunk coords) (X+Z-Y)%16
Bucket Count: 16
HashSet Order:
(Hash self=0) self, Xp, Zp, Yn, Xn, Zn, Yp
(Hash self=[1-14]) Xn, Zn, Yp, self, Xp, Zp, Yn
(Hash self=15) Xp, Zp, Yn, Xn, Zn, Yp, self
NotifyNeighbor Order: Xn, Xp, Yn, Yp, Zn, Zp
(Notation: AXISdir)

TileTick Priority Summary:
Repeaters:
if updated self, -1
else if unpowered_repeater/(any) comparator directly in front, -3
else if self=powered_repeater, -2
else, -1
Comparators:
if unpowered_repeater/(any) comparator directly in front, -1
else, 0
Torches:
Always 0

My channel: youtube.com/user/sharir1701