| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
| |
lookup functions
|
| | |
|
| |
|
|
|
|
|
|
| |
wagons
The occupation system as it is now will change. For each position, I will save the index in the train's path,
and implement a callback system. I need this because the occupation window system will not be enough to cover all use cases
(e.g. to make a train stop with it's center or back at a certain position, I need 3 different brake distances, which doesn't fit into the scheme)
|
| |
|
|
| |
There's something wrong with the new paths, next time build a path validity checker to trace the issue
|
| |
|
|
| |
The changes to the path system have not yet been integrated...
|
| |\ |
|
| | |
| |
| |
| | |
See privilege_guide.txt for information
|
| |\| |
|
| | |
| |
| |
| | |
(also fix the output of /at_sync_ndb)
|
| |/ |
|
| |
|
|
| |
It is not necessary to reload the save files, because there already is a function to invalidate train routes e.g. when turnouts are switched
|
| |
|
|
|
|
|
|
| |
Features:
- couple/decouple trains from a driver stand
- new couple lock system (owner based, overridable by 'train_remove' privilege)
- all train operators can now change the inside/outside text, allows for multilines
Accessible via right-click menu or by pressing Sneak+Jump keys
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
...to support an arbitrary number of connections for rails, which leads to these new features:
- switches now get recognized by the trackworker correctly
- ability to add real rail crosses
During this, I also rewrote the rail registering system and the conway function (important part of path prediction)
Note, developers: the track preset format changed, you might need to rewrite them according to the presets in tracks.lua if you wrote your own
(possibly breaks advcarts)
|
| | |
|
| |
|
|
| |
This will be required for advcarts
|
| |
|
|
| |
those) by custom atround() function
|
| |
|
|
|
|
| |
If a train moved towards another train, and the other train's step was executed after the first one's, the trains did eventually not collide.
Fix by moving the enter_node and collision check to step_b
Also change some couple behavior
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
