mesecons/mesecons_detector/doc/nodedetector/description.html

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.
It can also receive digiline signals. You can either send "GET" and it will
respond with the detected nodename or you can send any other string and it will
set this string as the node to scan for.
Nodenames must include the mod they reside in, so for instance default:dirt, not just dirt.
The distance parameter specifies how many blocks are between the node detector and the node to detect.
Automatic scanning with Mesecons output only works when the detector is in an active block, but Digilines queries always work.
Major change: Documentation is now included with mesecons, the website just extracts the documentation in a more readable format This makes development of new features easier, as documentation can automatically be updated on the website without modifying the website's code! Every mod that has nodes in the mesecons modpack has a "doc" folder that contains subfolders with recipe, description and preview of the block. The website will discover which documentation is available by reading the documentation.json file. 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.`
			`It can also receive digiline signals. You can either send "GET" and it will`
			`respond with the detected nodename or you can send any other string and it will`
			`set this string as the node to scan for.`
			`Nodenames must include the mod they reside in, so for instance default:dirt, not just dirt.`
Improve object and node detectors * Support detection of multiple players in object detector * Add distance parameter to node detector * Fix area protection 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.`
Document inactive block behaviour (#447) 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.`