orwell96
e04d84cb4c
Actually allow what manual promises (setting IP on non-assigned signals)
2018-10-17 17:37:03 +02:00
orwell96
8f8f009425
Make signal influence point (~halt point) specifiable
...
Also extend signal api necessarily
2018-10-09 12:07:23 +02:00
orwell96
8df7bcf6b6
Improve route programming:
...
- Formspec for TCBs instead of unhandy chatcommands
- Ability to advance route over the next secction without punching end
- Better visualization
- Ability to route into dead-end sections
2018-10-07 22:21:49 +02:00
orwell96
8e70c070c1
Fix route programming lock-placement
2018-09-28 22:27:08 +02:00
orwell96
d837e7e5e9
Add LuaAutomation interface functions for interlocking routesetting and aspect requesting.
...
This allows to incorporate interlocking to automated systems
2018-08-24 22:39:13 +02:00
orwell96
05cb6090ac
Move passive API to the advtrains core
...
to remove dependency of interlocking on luaautomation
2018-08-16 19:18:03 +02:00
orwell96
5fad61e9c9
Fix various bugs found while testing
2018-08-13 11:27:38 +02:00
orwell96
224d5cbfd3
Add 'interlocking' privilege and add security checks
2018-08-12 17:23:52 +02:00
orwell96
c34794e8a1
Implement routesetting
...
Missing things: signal aspect updating, waiting routes handling, management /info tool
2018-07-21 16:31:00 +02:00
orwell96
5fc5eb9c2a
Change stuff on route programming, begin routesetting
2018-07-17 21:02:01 +02:00
orwell96
e3667b630c
Basic route management from signalling formspec
2018-07-04 19:31:44 +02:00
orwell96
031aab4633
Signal assignment and route programming procedure
2018-07-04 17:48:33 +02:00