MisterFister wrote: Fri Feb 07, 2020 9:57 pm
Your decision, which you have the right to make, has been to forego those conveniences entirely. If your base has a lower actual physical quantity of locations you want to be able to keep track of, that's fine. But...?
I apologize for not responding earlier, i don't remember why, thanks to ssilk linking to this thread from this one :
viewtopic.php?f=6&t=104363&start=20 which is is related , it made me realize/remember.
Time has passed since then and my playing habits have changed a little, i should have answered that i am using the research bar in the train GUI to find a PAX station which is only a partial fix, because that doesn't account for the time i ask a train to temporarily stop somewhere ( not at PAX station), and other cases developped in the other thread that may explain why that since my previous comment on this thread made my position is not so categoric.
For the precise case of PAX station in city blocks, this is where i found too that scrolling in the list of the schedule is annoying ( due to many many stations 100% agree) and i tend to use the research in such case as they would have unique name ( but more often time now i'm using the train limit settings and have many stations name the same).
It is possible to make the PAX station include a train signal turned red by the presence of an item in a chest near the train stop, which would make the passenger train wait at every PAX selected as temporary stop with the current default behavior unless the player pick up and put back an item in a chest, but really most of the time i don't have those PAX station and the train is called to stop in the middle of nowhere, because i developped the habit of using tempory stops for material supply train.
It is also possible to have a fire and forget behavior if you change the condition of the train after you clicked for a temporary stop to something that doesn't trigger, which is something i HAVE to do when i use the research thing to add temporary stop, or click a random rail in the map for it, otherwise my train loop back, because in case of supply trains, they have a "base station" where they load their material, and the default 5sec waiting behavior is making me miss the moment when the train waits for me to pick up material often time.
In the case of "forgetting what i was doing 20 min ago before that biter attack"/ personnal train, it would be, from the idea of a blank schedule, adding temporary stops, with never met conditions, which can be done on rails or train stop, and one could move the new temporary stop in between others, to have a "temporary schedule" similar to a list of "mostly/recently" used stations. This is often how my practice end up being.
The suggestion to be able to configure the default behavior of ctrl click on a per locomotive would/could answer many of those points. I was only explaining "what i do", which may help others because it solve their problem or give ideas,sometimes it helps me too because someone explain to me i was doing it wrong, i haven't changed my mind about the current state being a bit frustrating, i have changed how i organised my playstyle to adapt the current state, the research is a powerful feature,to avoid scrolling a long list of stations in case you have unique name so i'm still using the empty schedule + modification of default condition thing quite often, even for supply train. ( as it also work for temporary stop not at a station ).
I was made to realize in the other thread that my way of modifying the default condition when doing this was unecessarily using too many clicks but even with that newly acquired knowledge the ability to configure the default behavior on a "per locomotive" basis for temporary stops would be the best option for me, as this way only my PAX or dedicated supply train would be set up this way, which would still allow me to hop on any train as my taxi train using temporary stop detour, and/or more generally keep the current forgiving behavior of the system that return to normal if you forget instead of blocking as default.