It's a cute little feature, I like it. Little touches like that are always appreciated in some routes.
Worth noting that whoever put these in probably had nothing to do with developing routes or fixing bugs.
It doesn't affect anything and probably was quick to implement. But they have different teams for everything so one person doesn't do everything
I mean they must have had something to do with developing routes as they wouldn’t understand how to put them in otherwise. though I agree it wouldn’t have made a difference to bug fixing, are people really going to call for routes to be flattened down to the point of baron for bug time? I know I won’t, if you argue for thing A to be removed you can say the same for thing B and how long will it be before we would lose entire stations or similar or more, cause someone thinks it could fix an issue which probably hadn’t been noticed at the point said things were created… edit: my call for bug fixing is mostly to do with after dlc release care and actively not rushing development that it causes over rate of accidental bugs. flattening the game down or taking dlc development time doesn’t have any connection to bug fixing in my view, so I don’t see why we as players/customers would ever want less of a product and call it better.
Uhm yes flattening the game down and taking more dlc development time absolutely helps with bug fixing - it's a time heavy process because it involves a lot of analyzing, modifying, and testing in various areas (especially for games). Flattening out 1. makes a lot of time free that can be used for bug hunting, fixing and testing, 2. prevents accidental, unwanted problems that interfere with both areas of development (which in turn lengthens total development time, increases stress and complexity of processes in both areas, and also increases the change and risk of concreted bugs (basically, unfixable and unchangeable bugs, glitches, which have been worked around/masked/ignored/additionally re-created/etc. in areas that need it working, and so on - which then additionally in turn can make changes, additions like features nearly impossible to impossible, and also make working things broken, more complex and unstable, with also nearly impossible to impossible solutions to them, all without requiring a complete rebase and restructuring of either larger parts of the project or even the whole project as it is - aka lava flow in software dev terms) and so on and I could continue. By the way, you can't make devs do two tasks at once in the same amount of time.
Yes dlc making is a time heavy process but flattening down a route quality doesn’t help bugs. if you are expecting a dlc to take a long time, you would give yourself more time for such things. Most bugs will come up afterwards so then that has nothing to do with development but the same basic after care.
I feel the time would have been better spent doing things like making sure tree branches don't enter the cab when driving past like they do on BML and SEHS
or they could plan for that along with other bugs and not have to cut back on other route features to stick to said self imposed time constraints…
Would be cool if they had implemented a way that this actually has a sense to do. If not implemented by a guard or any AI who controls tickets (which would take way too much ressources for that features - I know) then maybe just to be able to get into the loco with it. However, and this always is my logical aspect about this, isn't an employee or train driver of the operator company free of charge or at least get a reduced price for the tickets? I mean in training lessons, it would be very mean to force the trainees to purchase to ride with the train, wouldn't it?
