Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-101820

Tripwire hooks sometimes stay in active position with no entities triggering them

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Awaiting Response
    • None
    • Minecraft 1.9.2, Minecraft 1.9.3, Minecraft 1.11, Minecraft 1.11.2, Minecraft 17w17b, Minecraft 1.12.2, Minecraft 1.14, 1.15.2, 1.16.4
    • Community Consensus
    • Redstone
    • Important
    • Platform

      The tripwire hook pairs, connected by string, will stay down after a MOB has triggered them and exited the bounding box of the string. This can be confirmed, and replicated, on the shifting floor designs used in farms such as ImpulseSV's ghast farm (a.k.a. The Scream Machine), or Snocrash's wither skeleton farm (a.k.a. Wither Skeleton Sandwich). I can't confirm with any degree of certainty that this bug occurs in other configurations.

      It arises when MOBs fall through the shifting floor, and can take some time to appear, although there is no certain time that needs to pass for the bug to develop. It could occur after only a few seconds. Could it be due to the MOBs exiting the strings bounding box from the bottom of the bounding box, rather than the sides or the top? Perhaps the string object is missing the MOB exiting its bounding box from below and not generating an event message. That is what it feels like when I have observed this happening.

      Moving to a location that unloads the chunks that the tripwire hooks are in, and then reentering those chunks results in the tripwire hooks being 'reset' to their correct, inactive, condition.

      Below is a link to a video that I made to show this bug while it is occurring. I'm sorry about the amateur quality of the video, but I only made the video for this bug report.

      https://youtu.be/XtNCsjreNzM

            Unassigned Unassigned
            Rabidgoalie Michael Steward
            Votes:
            89 Vote for this issue
            Watchers:
            28 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: