piston article's "microtick" section is noncense

[EmiliaThorsen]

the microtick part is to not say less totaly infactual and misses a very large amout of mecanics and behaviours of pistons and 0-ticking

[pwouik]

microtick, more commonly called blockevent delay, is a widely used term in doormaking, it doesn't refer to to a real game mechanic (except in older versions where switching block event queue allowed double blockevent scheduling) but a concept like redstone tick for example
It should be made a little clearer, also related mechanics are in Activation mechanics and should not be duplicated here

[EmiliaThorsen]

"door makers call it that" doesnt make it fact, you can get pistons to activate in specific orders either by having ttp or block event priority, it also misses a lot of things like block dropping and things, as you also mentioned does double be cheduling exist in -1.8, this is something pepole should try to explain.

[pwouik]

the microtick part is not factual or infactual as it just define a concept over the block event queue to help thinking about block event chains(classify pulse circuit, compare blockevent chains...)
It miss some ttp and other stuff order, the point of it is just to chain blockevent without having to keep track of the queue in your head, especially in doormaking where the order often come from dust and you just add a blockevent to ensure the order
it's based on the block event queue mechanics that are quickly explained above