Affects Version/s: Minecraft 1.5.1, Minecraft 1.6.4, Minecraft 1.7.1, Minecraft 1.7.2, Minecraft 14w32a, Minecraft 1.8, Minecraft 1.8.1-pre3, Minecraft 1.8.1-pre4, Minecraft 15w42a, Minecraft 1.10.2, Minecraft 16w42a
Fix Version/s: None
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.