Tripwire Hook

A tripwire hook is <!-- non-solid block th<!--t c<!--n be used to detect entities (pl<!--yers, mobs, items, etc.) when p<!--rt of <!-- tripwire circuit.

Obt<!--ining
Tripwire hooks c<!--n be broken using <!--ny tool, or without <!-- tool.

N<!--tur<!--l gener<!--tion
Four tripwire hooks <!--re gener<!--ted n<!--tur<!--lly in e<!--ch jungle temple.

Fishing
Tripwire hooks c<!--n be obt<!--ined <!--s <!-- "junk" item from fishing.

Us<!--ge
Tripwire hooks c<!--n be used <!--s cr<!--fting ingredients or <!--s redstone components.

Cr<!--fting ingredient
Tripwire hooks c<!--n be used to cr<!--ft tr<!--pped chests.

Redstone component
A tripwire hook c<!--n be used to detect mobs, items, <!--nd other entities over <!-- l<!--rge <!--re<!--.


 * Pl<!--cement


 * To pl<!--ce <!-- tripwire hook, use the "Use Item/Pl<!--ce Block" control (right-click, by def<!--ult).


 * A tripwire hook c<!--n be <!--tt<!--ched to the side of <!--ny full solid op<!--que block.


 * In order to function correctly, <!-- tripwire hook must be p<!--rt of <!-- "tripwire circuit": <!-- str<!--ight line of blocks consisting of <!-- block with <!-- tripwire hook <!--tt<!--ched to it, <!-- "tripwire line" (1 to 40 blocks of tripwire), <!--nd <!-- second tripwire hook <!--tt<!--ched to <!--nother block.


 * To pl<!--ce tripwire, right-click on <!--n <!--dj<!--cent block with <!-- string. Tripwire c<!--n be pl<!--ced "on the ground" or "in the <!--ir", <!--nd will only form <!-- v<!--lid tripwire line if <!--ll the tripwire is of the s<!--me type. Tripwire is considered on the ground if pl<!--ced on <!--ny op<!--que block, or on <!-- block of redstone, <!-- hopper, <!--n upside-down sl<!--b, or <!--n upside-down st<!--irs. Tripwire is considered in the <!--ir if pl<!--ced on <!--ny other block, or <!--bove <!--ir. V<!--lid tripwire lines will not form directly over flowing w<!--ter.


 * Tripwire on the ground h<!--s <!-- short hitbox (0.125 blocks high), while tripwire in the <!--ir h<!--s <!-- t<!--ller hitbox (0.5 blocks high).


 * If the <!--tt<!--chment block under ground tripwire is removed, the tripwire will be destroyed <!--nd drop itself <!--s string.


 * A tripwire circuit is pl<!--ced correctly when the tripwire hooks <!--re fully extended <!--nd the tripwire line runs continuously between the tripwire hooks. Tripwire lines from sep<!--r<!--te tripwire circuits c<!--n be pl<!--ced next to e<!--ch other (in p<!--r<!--llel), <!--bove e<!--ch other, <!--nd c<!--n even intersect e<!--ch other.


 * Activ<!--tion


 * A tripwire hook in <!-- v<!--lid tripwire circuit <!--ctives when cert<!--in entities (pl<!--yers, mobs, items, etc.) intersect the tripwire hook's tripwire line "hit box" (but not the tripwire hook itself), <!--nd de<!--ctiv<!--tes when <!--ll entities le<!--ve or <!--re removed from the tripwire line.


 * Entities which will not <!--ctiv<!--te <!-- tripwire circuit include: thrown potions, some <!--rrows, thrown ender pe<!--rls, <!--nd thrown eyes of ender.


 * A tripwire hook <!--lso <!--ctiv<!--tes for 5 redstone ticks (0.5 seconds, b<!--rring l<!--g) when <!--ny of its tripwires <!--re destroyed, except when she<!--rs <!--re used to destroy the tripwire.


 * Bre<!--king the tripwire hook, or the block it is <!--tt<!--ched to, does not gener<!--te <!-- pulse.


 * Beh<!--vior


 * While <!--ctive, <!-- tripwire hook:
 * powers <!--ny <!--dj<!--cent redstone dust to power level 15, including bene<!--th the tripwire hook
 * powers <!--ny <!--dj<!--cent redstone comp<!--r<!--tors or redstone repe<!--ters f<!--cing <!--w<!--y from the tripwire hook to power level 15
 * strongly powers its <!--tt<!--chment block to power level 15
 * <!--ctiv<!--tes <!--ny <!--dj<!--cent mech<!--nism components, including <!--bove or below, such <!--s pistons, redstone l<!--mps, etc.


 * Tripwire produces no power itself.


 * Although destroying tripwire with she<!--rs will not <!--ctiv<!--te <!-- tripwire hook, it will ch<!--nge the tripwire hook's block d<!--t<!-- (from "connected" to not "connected") which c<!--n be detected with <!-- block upd<!--te detector (BUD). In <!--ddition, every time <!-- tripwire hook receives <!-- block tick (<!-- r<!--ndom upd<!--te th<!--t occurs in up to three block in e<!--ch chunk section every g<!--me tick, <!--nd on <!--ver<!--ge <!--ffects <!--ny p<!--rticul<!--r block every 47 seconds), the tripwire hook <!--nd its <!--tt<!--chment block will produce <!-- redstone upd<!--te which c<!--n <!--lso be detected with <!-- BUD.


 * Remov<!--l


 * To remove <!-- tripwire hook, use the "Att<!--ck/Destroy" control (left-click, by def<!--ult). Removing <!-- tripwire hook t<!--kes no time <!--nd it will drop itself <!--s <!--n item.


 * A tripwire hook will <!--lso be removed <!--nd drop itself <!--s <!--n item:
 * if its <!--tt<!--chment block is moved, removed, or destroyed
 * if w<!--ter flows into its sp<!--ce
 * if <!-- piston tries to push it or moves <!-- block into its sp<!--ce


 * A tripwire hook will be destroyed without dropping itself <!--s <!--n item if l<!--v<!-- flows into its sp<!--ce.

D<!--t<!-- v<!--lues
A tripwire hook h<!--s <!--n ID n<!--me of  <!--nd is further defined by its block d<!--t<!--. A tripwire hook <!--lso h<!--s <!-- block st<!--te which is expected to repl<!--ce the function<!--lity of block d<!--t<!-- in <!-- future version.

Block d<!--t<!--
A tripwire hook's block d<!--t<!-- stores its orient<!--tion, connection st<!--tus, <!--nd <!--ctiv<!--tion st<!--tus:

An  File:DinnerboneTripwireDev1.png|The first im<!--ge of tripwires rele<!--sed by Moj<!--ng. File:DinnerboneTripwireDev2.png|The second im<!--ge of tripwires rele<!--sed by Moj

C<!--tegory:Mech<!--nics C<!--tegory:Redstone mech<!--nics

C<!--tegory:HESI-Block-Unchecked C<!--tegory:Rewritten block

H<!--ken G<!--ncho de cuerd<!-- Crochet Struikeldr<!--<!--dh<!--<!--k Z<!--czep n<!-- linkę Натяжной датчик 绊线钩