[MC-13129] Floating/grounded restriction on tripwire behaves inconsistently.

Let me start out by saying that I understand the intention that tripwire must be entirely floating or entirely grounded. I'm not calling that a bug. However, I believe a specific aspect of the implementation is unduly inconsistent. This has been mentioned before in discussion of MC-13077 (dupe) and MC-570 (WAI), but not clearly explicated as different from the obvious intended behavior.

I am seeing inconsistent behavior when there is a block under a Tripwire Hook, but not the tripwire itself. Specifically, if the tripwire itself is floating:

If there is a block underneath a tripwire hook facing north or east (south or west end of a tripwire line), then the hook will be inactive, just like if the tripwire line itself is partially on the ground and partially suspended. That's fine.

However, if there is a block underneath a tripwire hook facing south or west (north or east end of a tripwire line), then the tripwire will function normally, and in addition the tripwire and hooks will spontaneously toggle between the “connected” and “disconnected” states, with accompanying sound effects.

The above also holds in reverse: a grounded tripwire works even if the south or west-facing hook has no block under it.

For consistency, a block underneath a south or west-facing tripwire hook should also prevent the tripwire line from functioning.

The attached image shows a test rig. The displayed tripwires will spontaneously connect/disconnect a few times a minute — see how some of the hooks are in the disconnected state.

Linked issues

is duplicated by 3

MC-16990 Tripwire functionality is orientation dependent Resolved

MC-37565 Tripwires not working Resolved

MC-63827 Tripwire broken? Resolved

relates to 1

MC-570 floating tripwire doesn't mix with non-floating tripwire - it will just pop off Resolved

Attachments

Comments 17

Tails 2013-04-01T21:08:38Z

Let me quote Dinnerbone:

This is intentional behaviour. Tripwire can be all floating or all grounded, but not a mixture of both. It behaves in subtly different ways depending on its suspension status, so it logically just cannot function while in a mixed state.

Kevin Reid 2013-04-01T23:10:22Z

I'm not disagreeing with Dinnerbone. Dinnerbone is saying that tripwires don't function when at a mixed height. I observe that, in all other cases but this one, that non-functioning is specifically shown in-game by putting the hooks in a “disconnected” state (drawn with a raised-up bent hook). This bug report is a case where the disconnected state does not happen, whereas in all other cases it does:

All of the wire and hooks in air: Functional.
All of the wire and hooks on blocks: Functional.
Some of the wire in the air, some on a block: Disconnected.
All of the wire in air, south hook on block: Disconnected.
All of the wire in air, north hook on block: Functional, glitchy. ← This is the bug.

There are two possible interpretations of Dinnerbone's remark: that tripwires are inconsistent/glitchy if mixed and that tripwires would be inconsistent/glitchy if allowed to be mixed. The fact that mixed wires ordinarily show a disconnected state indicates the latter is the appropriate interpretation, and so this case where the hooks do not become consistently disconnected is a bug.

Tails 2013-04-02T00:15:18Z

Alright reopened.

Ben Carter 2013-06-01T04:52:06Z

MC-16990 was closed as a duplicate of this but I don't see where it's mentioned here that this also happens if the block is placed under the West hook (disconnected) as the South hook (as you mentioned).

Itouch2 2014-04-27T10:55:56Z

Confirmed for 1.7.9 and 14w17a

7 more comments

Itouch2 2014-04-30T10:52:16Z

Confirmed for 14w18a

NekoJonez 2014-07-30T09:24:28Z

I asked my ticket to become a dupe so confirmed for 14w30c

Torabi 2014-08-07T07:23:42Z

The debug menu shows that a tripwire hook with a block under it is suspended:false. This also visually affects the angle of the hook arm. However, if the hook and wire are connected first, and then a block is placed below one of the hooks, it will still remain attached:true. If the block is placed under the north- or east-facing hook, both hooks and all the wire will become attached:false if the tripwire is triggered. This does not occur if the block is placed under hooks facing south or west.

Kevin Reid 2014-10-25T16:05:27Z

Confirmed for 1.8.1-pre3. However, the effects have changed slightly.

Tripwire behavior (when it sends a redstone signal) is still inconsistent as described.
I no longer see the spontaneous toggling or sounds.
NEW: The hooks with blocks under them have glitched models: the metal hook part is separated from the wooden arm.

atomizer 2014-11-10T17:03:29Z

confirmed for 1.8.1-pre4 :/

insomniac_lemon 2015-03-08T21:34:08Z

Kevin, that last part on your newest comment is MC-69834.

Also new in 1.8.3 is that tripwires don't have a 'powered' model (although the state DOES exist) meaning they do not have the previous behavior of being pulled down when activated as they did before they were added to the model system.

atomizer 2015-10-20T16:59:48Z

Still a problem in 15w42a

insomniac_lemon 2015-10-20T17:59:55Z

I still don't even get the point of having a suspended and non-suspended versions. If it's flush with the floor and has enough distance to be set off, if those blocks weren't there it would still be set off.

Actually is seems sort of backwards how it is set up. The floor version doesn't look like it would be pulled enough to be set off, but the suspended version is the one that is moved more up. You could use the suspended version (moved up more) and it looks perfectly fine (try with glass or glowstone). I'm not sure why they complicated things for a miniscule height difference...

SuperBio 2015-10-27T12:36:37Z

Added an image, basic description follows,

There is a Tripwire and a peice of string next to each of these dual BUD Switches. Tripwirehooks with string facing NORTH AND EAST trigger both buds as they should, but Tripwirehooks with string facing WEST OR SOUTH don't trigger one of the BUDs. This idicates that Tripwirehooks facing WEST OR SOUTH do not connect to the peice of string. This is most likely responsible for most of the Tripwirehooks not working when one tripwirehook doesn't have a block under it.

I assume to fix it you make the tripwire recognize string in every direction. I hope it's that simple.

kumasasa 2016-10-22T05:49:32Z

Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time.

SuperBio 2016-10-22T07:37:20Z

Yeah this is still an issue, the device I put in the image tripwirehookfix.jpg still performs exactly the same as it did last year when I uploaded the picture. Edit The picture has had the description wrong for a while now, the text on the left is correct, whereas the text on the right is not.

SunCat 2017-04-02T16:42:42Z

Because "suspended" state of tripwire and tripwire hook was removed, this bug is now irrelevant. Issue that was showed by @unknown is now described in MC-115322