diff options
author | Y. Wang <y5nw@protonmail.com> | 2024-09-04 10:31:18 +0000 |
---|---|---|
committer | orwell <orwell@bleipb.de> | 2024-11-09 21:55:35 +0100 |
commit | 35167fe928e61ecf35c633014972e36c921a1b78 (patch) | |
tree | 11988514094289bbdc0a0a0b2d6514a6c3262db0 /advtrains_luaautomation | |
parent | 9ada994d5b3bd874e537b0bc9641b925058bdf51 (diff) | |
download | advtrains-35167fe928e61ecf35c633014972e36c921a1b78.tar.gz advtrains-35167fe928e61ecf35c633014972e36c921a1b78.tar.bz2 advtrains-35167fe928e61ecf35c633014972e36c921a1b78.zip |
Update LuaATC documentation
* Fix broken link to RWT API documentation.
* w_speed is no longer relevant since the 2021 new-ks update.
Diffstat (limited to 'advtrains_luaautomation')
-rw-r--r-- | advtrains_luaautomation/README.md | 10 |
1 files changed, 2 insertions, 8 deletions
diff --git a/advtrains_luaautomation/README.md b/advtrains_luaautomation/README.md index f98f7a0..f285d0f 100644 --- a/advtrains_luaautomation/README.md +++ b/advtrains_luaautomation/README.md @@ -145,22 +145,16 @@ asp = { -- the character of call_on and dead_end is purely informative call_on = <boolean>, -- Call-on route, expect train in track ahead (not implemented yet) dead_end = <boolean>, -- Route ends on a dead end (e.g. bumper) (not implemented yet) - - w_speed = <integer>, - -- "Warning speed restriction". Supposed for short-term speed - -- restrictions which always override any other restrictions - -- imposed by "speed" fields, until lifted by a value of -1 - -- (Example: german Langsamfahrstellen-Signale) } ``` -As of January 2020, the 'dst', 'call_on' and 'dead_end' fields are not used. +As of September 2024, the 'dst', 'call_on' and 'dead_end' fields are not used. #### Lines The advtrains_line_automation component adds a few contraptions that should make creating timeable systems easier. Part of its functionality is also available in LuaATC: -- `rwt.*` - all Railway Time functions are included as documented in [the wiki](https://advtrains.de/wiki/doku.php?id=dev:lines:rwt) +- `rwt.*` - all Railway Time functions are included as documented in [the wiki](https://advtrains.de/wiki/doku.php?id=dev:api:railway_time_api) - `schedule(rw_time, msg)`, `schedule_in(rw_dtime, msg)` Schedules an event of type {type="schedule", schedule=true, msg=msg} at (resp. after) the specified railway time (which can be in any format). You can only schedule one event this way. (uses the new lines-internal scheduler) |