aboutsummaryrefslogtreecommitdiff
path: root/advtrains_luaautomation/passive_api.txt
diff options
context:
space:
mode:
Diffstat (limited to 'advtrains_luaautomation/passive_api.txt')
-rw-r--r--advtrains_luaautomation/passive_api.txt24
1 files changed, 0 insertions, 24 deletions
diff --git a/advtrains_luaautomation/passive_api.txt b/advtrains_luaautomation/passive_api.txt
deleted file mode 100644
index 5ae1df4..0000000
--- a/advtrains_luaautomation/passive_api.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-Lua Automation - Passive Component API
-
-Passive components are nodes that do not have code running in them. However, active components can query these and request actions from them. Examples:
-Switches
-Signals
-Displays
-Mesecon Transmitter
-Those passive components can also be used inside interlocking systems.
-
-All passive components have a table called 'advtrains' in their node definition and have the group 'save_in_at_nodedb' set, so they work in unloaded chunks.
-Example for a switch:
-advtrains = {
- getstate = function(pos, node)
- return "st"
- end,
- -- OR
- getstate = "st",
-
- setstate = function(pos, node, newstate)
- if newstate=="cr" then
- advtrains.ndb.swap_node(pos, <corresponding switch alt>)
- end
- end
-} \ No newline at end of file