Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-123992

Incorrect Piston Activation Timing

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • None
    • 1.18.20.21 Beta, 1.16.230.52 Beta, 1.16.220, 1.16.210, 1.17.34, 1.18.2 Hotfix
    • Plausible
    • Multiple

      Pistons begin activating 1 gametick after they are powered (setup to show this attached below). Timing like this do not follow the timings of other consumers, such as rails, trapdoors, doors, and fence gates, which activate in the same tick they are powered (setup to show this below).
      To reproduce pistons not firing until 1 gametick after being powered, place 1 sticky piston with a block in front, and two repeaters, one pointing into the piston, and one pointing into the block. When they are powered the redstone dust on the other side does fire (but doesn’t visually update, because it’s a 1 gametick pulse). The 1 gametick pulse shows the piston does not begin activation until 1 gametick after being powered. (Use setup from photo 3)

      Another way to reproduce this is having a sticky piston with a block in front which is cutting a redstone dust line, the dust under the block needs to be powered. Once the piston is activated, the dust begins powering the other side in a producer tick or 1 gametick after the piston is powered. (Use setup from photo 2)

      To see that rails, trapdoors, doors, and fence gates (other consumers) activate in the same tick they are powered place a redstone dust, place a block next to it, and place a repeater on the other side of the block. The repeater powers the dust in a consumer tick first, so the dust has not visually updated yet, but the rail, trapdoor, door, and fence gate all activate in the consumer tick, or the same tick they are powered. (Use setup from photo 1)

        1. 3743EB5D-C2C2-46C2-AA3E-81A1AB0C98C3.png
          1.48 MB
          NinjaPigeonHit
        2. 37F6C31E-E239-4A6F-A1A3-20303AD7440C.png
          862 kB
          NinjaPigeonHit
        3. 8D2E01AB-B267-452D-8AFE-64E44D39FFB1.png
          1000 kB
          NinjaPigeonHit

            NinjaPigeonHit NinjaPigeonHit
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: