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

Tripwire hooks delay activation and deactivation for 0.5 seconds, and hooks connected to tripwire to the South (+Z) or West (-X) disconnect during the delay

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • 1.20.30.24 Preview
    • 1.20.30.21 Preview, 1.20.30.20 Preview
    • None
    • Confirmed
    • Multiple
    • 1086851

      Detail provided by GoldenHelmet

      In the current release tripwire hooks activate immediately when tripwire connected to them is tripped, and they deactivate 1 redstone tick after the tripwire is un-tripped. That is, when an entity AABB overlaps the tripwire collision box the tripwire hooks visually move down in the same tick and they power the block they are attached to in the next redstone tick. When an entity AABB no longer touches the tripwire the hooks visually move up in the next redstone tick and stop outputting power in the redstone tick after that.

      In the 1.20.30.20 Preview tripwire hooks delay activating or deactivating for 0.5 seconds after the tripwire connected to them is either tripped or un-tripped. During this time, hooks that are connected to tripwire at their South (+Z) or West (-X) sides disconnect from the tripwire. The disconnection is a visual update (the hooks visually move high up as if no tripwire is present), a server-side block update (the disconnect and subsequent reconnection can be detected by an observer), and a redstone update (the hooks do not ouptut redstone power while disconnected). With regard to tripped tripwire, when the disconnected hooks reconnect after the delay, they only go to the activated (down) position and output redstone power if the entity AABB is still touching the tripwire at that time.

      Steps to reproduce

      1. Build the directional testing module as shown.
      2. Move into and out of the tripwire in the center while watching the hooks. Try this both slowly and quickly.
      3. Move into and out of the tripwire in the center while watching the redstone dust. Try this both slowly and quickly.
      4. Run or fly through the tripwire.

      Expected results

      Within each test, each hook and each redstone dust line updates in the same way as the others. The updates occur immediately (or as close to immediately as possible, i.e. with delays of no more than 1 redstone tick or 0.1 seconds between) after tripping or un-tripping the tripwire.

      Observed results

      Generally, activation and deactivation of the hooks and redstone lines is delayed for 0.5 seconds after tripping or un-tripping the tripwire. During the 0.5 second delay the hooks to the North (-Z) or East (+X) of the tripwire (i.e. the hooks attached to tripwire at their South or West) disconnect from the tripwire visually and do not power their blocks and redstone dust while disconnected.

      Summary of broken mechanics discovered so far:

      1. doesn't send signal across chunk borders
      2. delay before output signal is way too high (approx seven redstone ticks)
      3. doesn't trigger when run (or flown) through

       

      Original impetus for this ticket

      It seems that when a tripwire is triggered by an entity that also partially passes through the hitbox of one of the hooks, the block behind the hook will not output a redstone signal.

      Might need to make this a separate ticket, but possibly related, the tripwire seems to be triggering much earlier than it used to, at least in the case where a snow golem is right in front of the tripewire before it fires its triggering snow ball.

      I've attached the following

      • video showing the asymmetric redstone signals
      • video showing workaround for for broken timings
      • video from non-preview version 1.20.12 showing expected symmetric firing and timing

        1. ApproxSevenRedstoneTickDelay.mp4
          6.50 MB
          Ninjadankinate2
        2. AsymmetricTripwire.mp4
          5.01 MB
          Ninjadankinate2
        3. BrokenTripwire.mcworld
          320 kB
          Ninjadankinate2
        4. BrokenTripwireTimingWorkaround.mp4
          4.86 MB
          Ninjadankinate2
        5. ChunkBorders.png
          1.96 MB
          Ninjadankinate2
        6. Directional tripwire hook test setup.png
          492 kB
          [Mod] GoldenHelmet
        7. ExpectedBehavior.mp4
          3.64 MB
          Ninjadankinate2
        8. TripwireNoLikeFast.mp4
          8.77 MB
          Ninjadankinate2
        9. WorkingInCurrentRelease(non-preview).mcworld
          317 kB
          Ninjadankinate2

            Ninjadankinate2 Ninjadankinate2
            Votes:
            5 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: