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.
Linked issues
is duplicated by 2
relates to 1
Attachments
Comments 18
Confirm for 1.11 release. Tried removing and replacing string on the active tripwire and that does not fix issue. If I break the trip wire hooks and replace it seems to reset. It will work as intended for random amount of time, sometimes days, then get stuck on activated. This is being activated by hostile mobs.
I saw JL2579's video on it. It is still there and it effects many mob forms like the one below. (This is JL2579's Video, not mine)
https://youtu.be/sqZDkiEhu98
I experienced this is 1.16.4 as well. broke and replaced a piece of the string, stayed hot after reconnect. Broke both hooks, same thing. I didn't get the tripwire to work properly until after I broke the entire line and placed it again.
If it happens again, try breaking and replacing each string in the middle one at a time. It's possible that one of the pieces is stuck in an activated state somehow, and that's what's keeping it active. (If it does require all of them to be broken and replaced together, and a single broken one make the whole set break later, that'd also be weird.)
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w43a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.