| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
| |
Still outstanding: trains
|
| |
|
|
| |
The changes to the path system have not yet been integrated...
|
| |
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| |
|
|
|
| |
Caused problems on multiple detector rails in a row, because paths got cleared in-between a train step
Also optimize some code
|
| |
|
|
|
|
| |
off_track
The off-track warning has moved into the info text of wagons
|
| |
|
|
|
|
|
|
|
| |
...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)
|
| |
|
|
| |
... from update_trainpart_properties call
Prohibits flipping of all wagons when extent_h wasn't set
|
| |
|
|
| |
This will be required for advcarts
|
| |
|
|
|
|
|
| |
Bug was caused by the drives_on table of every train and advtrains.all_tracktypes
sharing the same reference, which caused advtrains.all_tracktypes to become the
intersection of all train drives_on's in the world.
However, this did become empty, causing nothing to work anymore.
|
| |
|
|
| |
For some reason, a sign text gets removed by a train when it drives by.
This should fix it.
|
| |
|
|
| |
Animals from mobs weren't damaged because they have the immortal group set.
Instead, we check for the existence of "fleshy".
|
| | |
|
| | |
|
| |
|
|
|
| |
Trains no longer get deleted when there's no rail
Fast item to create subway train
|
| | |
|
| |
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
also fix empty trains hanging around for too long
|
| |
|
|
| |
wagons
|
| |
|
