Some redstone components (rails,redstone torch,comparators,lever and buttons as far as I know) send duplicated block updates that cause unnecessary lag
This is because they have an onRemove method that is called when the state change (call to setBlock) that are responsible of the update order and then send other block updates after the setBlock call that are pointless (and not the same order as the first ones in the case of rails)
- relates to
-
MC-81098 Redstone dust updates cause lag
- Reopened