The bug
Breaking a tripwire [attached:true] with shears replaces the block with tripwire[attached:false].
This then updates, re-attaching itself to the tripwire blocks on either side,meaning the tripwire remains.
This behavior only seems to take place when first attempting to break is with shears. After this first failed attempt, breaking the tripwire with anything seems to continually reproduce the bug.
Tripwire will break normally if first attempted with fist.
Steps to reproduce
Set up a tripwire strung between two tripwire hooks, like shown in the image
.
Attempt to break the tripwire with a fist. It should pop off normally.
Replace the tripwire, and try to break with shears, using a fast click. The tripwire will briefly change state to
[attached:false], but quickly reconnects with an audible sound. Note the disarmed tag is now[disarmed:true],as shown in the second image.Repeat trying to break the tripwire with shears or a fist, using short clicks. The attached tag flickers between true and false, but the disarmed tag remains true throughout.
Hold down left click to quickly break the tripwire twice in a row. This has the affect of breaking the
[attatched:false]wire, and properly breaking, dropping the item.
Linked issues
is duplicated by 5
MC-153238
Strings gets detached, then attaches again to tripwire hooks when cut with shears.
Resolved
MC-178647
Destroying tripwire (connected to tripwire-hooks) with shears doesn't destroy the tripwire
Resolved
MC-208199
tripwire string doesnt break with shears in creative or survival sometimes.
Resolved
MC-209278
Breaking a String as Part of a Trip Wire With Shears Doesn't Beak It.
Resolved
MC-274830
Issues with disarming activated tripwires
Resolved
Attachments
Comments 15
This bug is being abused for String duping machine
Many people now rely on this to get unlimited string
In Minecraft 1.21, it is possible to take advantage of Crafter auto-compositing, allowing for unlimited Wool machines
Hopefully it will be fixed soon, and it has been delayed, which is not a good thing
Over time, this Bug will become a part of the gameplay and will evolve into something like 'Sand duping,TNT duping,Carpet duping,Rail duping'
The future will become irreparable
This is intended behavior, the string is supposed to stay attached in the 'disarmed' state, where walking over that disarmed string will not give any redstone signal. It is a feature coded in by Notch. The string is supposed to break after the second time, or the first time with anything that isn't shears. This has been mistaken as a bug.
Affects 14w25a, 1.8-pre2, 17w47a.
If you triggered and sheared a tripwire block, it became "inverted"; when it was triggered, the hooks were deactivated instead of being activated. This was useful for switches, clocks, etc.
Now an extra PP update is still detected when breaking connected tripwire with shears. This is attributed to the transformation into the disarmed state, indicating that it should be intended to become disarmed, not broken.
It is possible to enable disarming without allowing string duplication using water. I suggest changing the requirement for the tripwire hook setting states of a tripwire block from nothing (14w25a to 1.8-pre2, 17w47a to 1.21.1) / non-air (1.8-pre3 to 17w46a, 24w33a to 24w35a) / tripwire components (24w36a) to non-water. Therefore water will flush tripwire away correctly, while all the techniques like inverted tripwire and lava tripwire clocks are back. Duplication will be possible using explosion or withers, but explosion is useless as you cannot ensure tripwire blocks are blown up in the correct order, and taking control of a wither is not easy. So these will not do harm to balance like those using water.
Confirmed for 1.13.1.