| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
During rebase, this part of the autocouple feature must have been accidentally lost
|
| |
|
| |
|
|
|
|
| |
interlocking.set_route() was updating the signal aspect, which caused LZB's invalidate_ahead callback to run, although the route isn't yet fully set. Don't look ahead at this point, but instead in the next train step.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
server priv not limited, timetaking for restore_all
|
|
|
|
| |
remove obsolete code
|
| |
|
| |
|
| |
|
|
|
|
| |
event time
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Caused problems when approaching stoprail in manual control
also better for compatibility
|
| |
|
| |
|
| |
|
|
|
|
| |
signalling formspec
|
| |
|
|
|
|
| |
farther than train length in step
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(this caused the lzb approach to be called on nodes that have just received an enter event, which is not intended)
|
| |
|
| |
|
|
|
|
| |
digiline_send(), move on_updated_from_nodedb to advtrains table
|
|
|
|
|
|
| |
distance-based approach or minetest.is_block_active() if available
See also https://github.com/minetest/minetest/pull/10897
|
| |
|
| |
|
| |
|
|
|
|
| |
Previous commit did not fix saving, but is kept because there is a corner case for which it is required (see MT forum)
|
| |
|