diff options
Diffstat (limited to 'assets/manual/man/man7advtrains')
4 files changed, 0 insertions, 111 deletions
diff --git a/assets/manual/man/man7advtrains/node_definition.7advtrains.md b/assets/manual/man/man7advtrains/node_definition.7advtrains.md deleted file mode 100644 index db9db08..0000000 --- a/assets/manual/man/man7advtrains/node_definition.7advtrains.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -titles: -- node_definition -section: 7advtrains -manual: 'Advtrains Developer''s Manual' -shortdesc: node definition entries specific to Advtrains -seealso: -- signal_aspects(7advtrains) ---- - -# Description -This page describes various fields in node definition tables that are used by Advtrains. - -# Node Groups -Advtrains uses node groups to identify certain properties of a node. The following node groups are currently read by Advtrains: - -* `advtrains_signal`: When set, this property defines the type of signal this node belongs to. `1` indicates that this node is a static signal, and `2` indicates that this node is a signal with a variable aspect. -* `not_blocking_trains`: When set to 1, trains can move through this node. -* `save_in_at_nodedb`: When set to 1, this node should be saved in the internal node database used by Advtrains. - -# The `advtrains` Field -The `advtrains` field in the node definition may contain the following fields: - -* `get_aspect(pos, node)`: This function should return the signal aspect of the node at the given position. - -* `set_aspect(pos, node, asp)`: This function should set the signal aspect of the node to `asp` if possible. `asp` is not guranteed to be an aspect supported by the node. - -* `supported_aspects`: This table should contain a list of supported signal aspects. diff --git a/assets/manual/man/man7advtrains/rwt.7advtrains.md b/assets/manual/man/man7advtrains/rwt.7advtrains.md deleted file mode 100644 index d1efc80..0000000 --- a/assets/manual/man/man7advtrains/rwt.7advtrains.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -titles: -- rwt -section: 7advtrains -manual: 'Advtrains Developer''s Manual' -shortdesc: Advtrains railway time -seealso: -- rwt_add(3advtrains) -- rwt_copy(3advtrains) -- rwt_last_rpt(3advtrains) -- rwt_now(3advtrains) ---- - -# Description -Advtrains depends on Minetest's "dtime" for most operations, and may slow itself down when necessary to prevent unexpected behavior, such as in a situation with a significant amount of lag. As a result, the internal time used by Advtrains is not synchronized to real-life time due to lag and server restarts. Railway time was therefore introduced as a method of accurately measuring internal time and, with this information, implementing a scheduling system. It can, however, also be set up to keep in sync with real-life time. - -Railway time is counted in cycles, minutes, and seconds, roughly corresponding to their real-life counterparts, with cycles roughly corresponding to hours. For a valid railway time object, it is expected that - -* The "cycles" element is an integer, -* The "minutes" element is an integer between 0 and 59 (inclusive), and -* The "seconds" element is an integer between 0 and 59 (inclusive). - -Railway time may be represented in three formats: - -* As a table with the `c`, `m`, `s` fields holding the cycles, minutes, and seconds, respectively, -* As a string with the cycles, minutes and seconds delimited with a semicolon, -* For zero cycles, as a string with the minutes and seconds delimited with a semicolon, or -* As a number representing the number of seconds since 0;0;0. - -If railway time is represented as a string, each element may have a variable length and do not require padding zeroes, and an element of the string may be empty if it is at the beginning or the end of the string. - -The railway time API is available in the `advtrains.interlocking.rwt` table or, for LuaATC, in the `rwt` table. diff --git a/assets/manual/man/man7advtrains/signal_aspects.7advtrains.md b/assets/manual/man/man7advtrains/signal_aspects.7advtrains.md deleted file mode 100644 index 1cb5d7e..0000000 --- a/assets/manual/man/man7advtrains/signal_aspects.7advtrains.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -titles: -- signal_aspects -section: 7advtrains -manual: 'Advtrains Developer''s Manual' -shortdesc: signal aspect tables for Advtrains -seealso: -- speed(7advtrains) ---- - -# Description -A signal aspect table describes the status of a signal in relation to a train following it. - -A signal aspect table may contain the following fields: - -* `main`: The main aspect of the signal -* `type`: The type of speed restriction imposed by the main aspect -* `dst`: The distant aspect of the signal -* `shunt`: A boolean indicating whether shunting is allowed -* `proceed_as_main`: A boolean indicating whether a train in shunt mode should continue with shunt mode disabled - -The `main` and `dst` fields may contain - -* A non-negative number indicating the current or next speed limit -* -1, indicating that the speed limit is or will be lifted -* `nil`, indicating that the speed limit is or will not be changed diff --git a/assets/manual/man/man7advtrains/speed.7advtrains.md b/assets/manual/man/man7advtrains/speed.7advtrains.md deleted file mode 100644 index 8b3fe1e..0000000 --- a/assets/manual/man/man7advtrains/speed.7advtrains.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -titles: -- speed -section: 7advtrains -manual: 'Advtrains Developer''s Manual' -shortdesc: Advtrains speed limit library -seealso: -- speed_lessp(3advtrains) -- speed_set_restriction(3advtrains) -- signal_aspects(7advtrains) ---- - -# Description -The speed library allows the manipulation of speed limits, which can be represented with - -* A non-negative number, which stands for a regular speed limit in m/s, or -* -1 or `nil`, which lifts the speed restriction - -The use of other values (in particular, nan and infinity) may result in undefined behavior. - -This library is available as `advtrains.speed`. - -# Notes - -The meaning of `nil` for the speed limit library differs from its meaning in signal aspect tables, where `nil` keeps the current speed limit. |