Piston Retraction Generates PT (Pending Ticks), Causing Game Lag, Redstone Signal Disruption, and Potential Permanent Map Corruption

When a piston retracts, it generates Pending Ticks (PT), which can lead to severe performance issues, redstone signal disruption, and even permanent damage to the game world. In Minecraft, if a single chunk accumulates more than 100 PT in 1 game tick, redstone signals within that chunk are delayed until the next game tick. However, the additional PT generated by pistons exacerbates this issue, making the game more prone to corruption.

The problem becomes particularly noticeable in scenarios involving large-scale redstone contraptions. For example, when over 400 pistons are activated simultaneously using high-frequency comparators, the chunk can easily exceed the PT limit. This results in delayed or disrupted redstone signals, and if the pistons remain active for an extended period, it can lead to permanent corruption of the affected chunk.

How to Reproduce:

1. Create a redstone contraption in a chunk that includes a chain of observers and over 600 pistons.

2. Use high-frequency comparators to activate more than 400 pistons simultaneously.

3. Use the command /time query gametime to measure the game ticks and observe the redstone signal output of the observer chain. This helps determine the chunk's redstone behavior.

4. Activate the pistons using the high-frequency comparators.

5. Observe the redstone signal output from the command block.

Observe the issue:

• After activating the pistons, you will notice that the command block's output signal becomes disrupted or delayed.

• If the pistons remain active for a prolonged period, the chunk may become permanently corrupted, rendering the redstone system unusable.

Expected Results:

• Pistons should not generate PT during retraction.

• Redstone signals from observers should not be affected by piston activation.

• The game should maintain stable performance even when a large number of pistons are activated simultaneously.

• No chunk corruption should occur, regardless of the number of pistons or the duration of their activation.