| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The copy tool copies a train to a global clipboard. It copies
the Line number, Routing code, inside text and outside text.
It copies the kinds of wagons in the train and whether they
are flipped around.
Pasting with the copy tool will conditionally flip the train
such that 'your front' of the train, rather than the absolute
front of the train, is what is output. The new train is
oriented to travel forward with the placing player's view.
Conditons are:
- Multi-unit/push-pull train (= has locomotives on both ends):
Never flipped
- Locomotive-hauled train (= has one end with a locomotive):
Flipped so that the locomotive is always at the front. If the
locomotive points long hood forward, it will still point long
hood forward.
- Rake of wagons (= has no locomotives on ends):
Flipped according to which end of the train the player copies
from. If the player is towards the back (wagon out of train
divded by total wagons > 0.5), then the back becomes the new
front. If the player is towards the front, no change.
|
| |
|
| |
|
|
|
|
|
| |
This new save system exists to split up the save file into several
smaller ones, to bypass lua limitations.
|
|
|
|
| |
This should prevent yet another train service disaster.
|
| |
|
| |
|
| |
|
|
|
|
| |
For signal, need to think of a callback system for signals and moving atlatc queue to core?
|
| |
|
|
|
|
| |
Used for ARS and stop points
|
|
|
|
| |
those rely on
|
|
|
|
|
|
| |
basis for "stop rails"
Stop rails ATM use the aforementioned things to add a pointwise "2" speed restriction. Seems to work.
|
|
|
|
| |
documentation on privileges
|
|
|
|
| |
(Master downgrade protection)
|
|
|
|
| |
and fix permissions on that
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
- 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
|
| |
|
|
|
|
| |
to remove dependency of interlocking on luaautomation
|
| |
|
|
|
|
| |
Now, only the signal aspect setting is still missing
|
| |
|
| |
|
| |
|
|
|
|
| |
if it already exists.
|
| |
|
| |
|
| |
|
|
|
|
| |
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
|