if you have floating trip wire and a hook with a block there under it won't connect with the trip wire and when you place the block when the wire is already placed and you walk on it, it brakes and when you place a block under the trip wire when everything is floating the wire breaks.
i think the wire should connect and work like normal wire and won't break when you place a block under it
here is a link to see it better http://youtu.be/oUUde4Qp5U4
Linked issues
is duplicated by 10
MC-4147
The string behaves differently on Ice
Resolved
MC-6540
Tripwire hooks not connecting with floating string in certain directions
Resolved
MC-8412
Tripwire won't work unless there is a block beneath
Resolved
MC-9046
Tripwires
Resolved
MC-13077
Tripwire disconnecting when a block is placed under the tripwire hook.
Resolved
Attachments
Comments 14
the video is very slow with uploading so it can take a few hours when you can watch it i comment again when its done
Please edit your summary to something more descriptive. "trip wire break" in itself is not really a bug, you may want to change it to something like "floating trip wire doesn't mix with non-floating trip wire - it will just pop off" if you believe that is the bug.
This should be considered a bug. In general, tripwire shouldn't be destroyed when blocks underneath are changed. It kills a lot of the potential and depth of the system. By changing this, we can finally have a detection method on the ground that still works without said ground. For instance, pulling away the floor without the tripwire breaking.
Also I want to point out, you can have a grounded tripwire without a block under one of the hooks. I'm sure it relates to the whole N/S/E/W thing, as only a specific end will work.
Hell, while I'm at it, I think hooks themselves should trigger the mechanism too. But the issue at hand is as OP stated.
This behavior also occurs when the ground is a mix of opaque and transparent blocks. As this behavior is clearly buggy, this report should be marked as "Won't fix" instead of "Works as intended".
I don't get it, what is even the point of 'suspended' states of tripwire/tripwire hook? Why should it matter if a block is under it or not? The suspended version has a model that is higher up on the block..... which logically, seems backwards because the version on the ground seems like it needs more room below for proper activation.
I see no behavior change (what are the "subtle differences" besides hitbox size, and why are they important? I've never heard anyone say that suspended/grounded tripwire was NEEDED for something to work), just remove the 'suspended' state and raise the model/hitbox up on tripwire+tripwire hooks. Bam, no more mixed state.
This is an intentional feature as I understand it. Floating tripwire and block-based tripwire cannot be mixed.