This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
usage:nodes:atc_rail [2019-07-02 17:06] 82.67.173.193 added information to wiki article (2/4) |
usage:nodes:atc_rail [2019-11-07 08:58] orwell extend doc(part 1) |
||
---|---|---|---|
Line 108: | Line 108: | ||
* a string, the name of a [[# | * a string, the name of a [[# | ||
- | === POS(x, y, z) === | + | == POS(x, y, z) == |
A shorthand function to designate a Minetest position vector like '' | A shorthand function to designate a Minetest position vector like '' | ||
- | === getstate(pos) | + | === Interacting with switches and other passive components |
- | Gets the state of a passive | + | Switches (turnouts), simple signals and mesecon switches are so-called "passive |
+ | Switch: | ||
+ | " | ||
+ | " | ||
+ | Signal: (simple signals, wall signals) | ||
+ | " | ||
+ | " | ||
+ | Mesecon Switch, Andrew' | ||
+ | " | ||
+ | " | ||
- | === setstate(pos, new_state) === | + | == getstate(pos) == |
- | Sets the state of a passive component at position '' | + | Gets the state of a passive component at position '' |
- | === is_passive(pos) | + | == setstate(pos, |
+ | |||
+ | Sets the state of a passive component at position '' | ||
+ | |||
+ | == is_passive(pos) == | ||
Checks whether there is a passive component at position '' | Checks whether there is a passive component at position '' | ||
- | === interrupt(time, | + | === Interrupts |
- | Causes the LuaAutomation mod to trigger an '' | + | These functions allow to schedule interrupts, a.k.a events to be executed at a later time. They are not available in init code. |
- | This function | + | The time counter and queue handling these interrupts |
- | === interrupt_pos(pos, | + | -- an example for an " |
+ | if event.int then | ||
+ | interrupt(1," | ||
+ | interrupt(1," | ||
+ | -- run 1: {A,B} | ||
+ | -- run 2: {A,B,A,B} | ||
+ | -- run 3: {A, | ||
+ | |||
+ | == interrupt(time, | ||
+ | |||
+ | Causes the LuaAutomation mod to trigger an '' | ||
+ | |||
+ | == interrupt_pos(pos, | ||
Triggers immediately an '' | Triggers immediately an '' | ||
- | **Use with care! This may lead to expotential growth of interrupts.** | + | === Railway Time Scheduler === |
+ | |||
+ | This is a separate schedule queue. In contrast | ||
+ | |||
+ | There are two important considerations to this: | ||
+ | |||
+ | 1. While the interrupt system is always synchronized to minetest step time, the RWT scheduler follows the RWT time flow. In particular, this means that you must be able to handle "time jumps" that occur when RWT is set up to adapt to real time. | ||
+ | 2. The RWT scheduler has a built-in protection against " | ||
+ | |||
+ | == schedule(rwtime, | ||
+ | |||
+ | Triggers a '' | ||
+ | The time value here is an absolute value. | ||
+ | msg can be any data type and is accessible in '' | ||
+ | |||
+ | == schedule_in(rwtime, | ||
+ | |||
+ | Like schedule(), but the passed time is relative. | ||
+ | |||
+ | -- Example: schedule a " | ||
+ | schedule_in(" | ||
+ | |||
+ | === Digiline === | ||
- | === digiline_send(channel, | + | == digiline_send(channel, |
Sends a [[usage: | Sends a [[usage: |