2015-11-20 20:14:50 +01:00
|
|
|
The node detector is a receptor. It changes its state when either any node
|
|
|
|
or a specific node is detected. Right-click it to set a nodename to scan for.
|
2019-08-21 22:52:33 +02:00
|
|
|
It can also receive digiline signals. For example, you can send
|
|
|
|
<code>{distance=4, scanname="default:dirt"}</code>
|
|
|
|
to set distance to 4 and scan for dirt. You can omit either parameter.
|
|
|
|
There is also a command parameter: <code>{command="get"}</code> will respond
|
|
|
|
with the detected nodename and <code>{command="scan"}</code> will respond with
|
|
|
|
a boolean using the distance and nodename of the detector.
|
2015-11-20 20:14:50 +01:00
|
|
|
Nodenames must include the mod they reside in, so for instance default:dirt, not just dirt.
|
2017-03-13 21:13:57 +01:00
|
|
|
The distance parameter specifies how many blocks are between the node detector and the node to detect.
|
2018-12-21 20:10:08 +01:00
|
|
|
Automatic scanning with Mesecons output only works when the detector is in an active block, but Digilines queries always work.
|