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

Redstone torch timings are off by half a tick

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • None
    • 0.13.0
    • None
    • Unconfirmed
    • Windows

      In PC, redstone torches change state when the block they are attached to has a change in signal longer than 1 tick (except for when that change in state is caused by the redstone torch itself, i.e. a short-circuit). In PE however, torches can change state when the block they're attached to has a signal change of 1 tick. The video demonstrates two examples of this in both PE (MCW10) and PC.

      https://www.youtube.com/watch?v=8vNeAsOgeyk

      To fix: torches should ignore any change in signal to their attachment block that is exactly 1 game tick or shorter (50ms or shorter), and only change state when the change in signal is longer than 1 tick. That way, a pulse that is 1.5 ticks or 2 ticks will affect a the torch, but a pulse that is exactly 1 tick or shorter won't, which is how redstone torches in the PC edition work.

      Edit: updated info, since redstone torches in the PC edition ignore any pulse that is 1 game tick or shorter and respond to any pulse longer than 1 tick, not just 1.5 ticks.

            jocopa3 Matt S
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: