feat: extra placeholders#156
Conversation
|
I like the choice of placeholders, especially the I would suggest a small change in the Like this: Regarding the problem with the A different approach would be necessary, maybe directly retrieving the |
|
there wasnt actually an issue with the i should probably try make it so train-only placeholders can't be used on station displays and vice versa |
- simplify: see MisterJulsen#156 (comment) - idiot-proof: see MisterJulsen#156 (comment)
|
I fixed the issue with the carriages, because I think it would've been confusing if it remains at 0. Otherwise, I really like the new placeholders :) |
On top of the already existing %time% placeholder, this PR adds:
day- the current in-game dayvia- a comma separated list of all stopoversline- the train name or, if defined, the line namecarriages- the amount of carriages this train hasorigin.(where the train started its journey) ORdestination.(where the train will end its journey) ORnext.(the next stop, includes the destination) ORstopN.(the following stops, where N=0 is the next stop, excludes the destination), followed by:station_name- the arrival stationplatform- the arrival platform numberarrival- arrival time in in-game hh:mm formatdeparture- departure time in in-game hh:mm formatarrival_eta- arrival time as an etadeparture_eta- departure time as an etatrainN., followed by:station_name- the arrival stationplatform- the arrival platform numberarrival- arrival time in in-game hh:mm formatdeparture- departure time in in-game hh:mm formatarrival_eta- arrival time as an etadeparture_eta- departure time as an etavia- a comma separated list of all stopoversline- the train name or, if defined, the line nameorigin- where the train started its journeydestination- where the train will end its journeycarriages- the amount of carriages a train hasstopN- the following stops, where N=0 is the next stopTodo: