There are a few routes in game that have request stops. (Arosa & Maintelbahn are first to mind). It would be nice if we had a system for it that works. (Even if it's not actually random, but pre scripted, but the player has no knowledge the 1st time on that service). For me, this is more important than guard mode etc
I'm not sure this would be practical to use in timetable mode, especially with the AI. Pre-scripted may be possible but it would have to appear on the objective list so i'm not sure the use? Perhaps this could be brought to life in a scenario however.
Yeah I was thinking about this. The best possible way right now would be to script it, but also set a Go Via marker like 1km before the stop, and then you would only be able to see relatively close to a station whether you should stop or not. Unless you open the timetable of course
It was mentioned by Lukas in the Maintalbahn livestream (in german, don't know if you can understand) that request stops are not possible for them to do currently in the Editor. "Warum keine Bedarfshalte?" is the timestamp for this question/chapter in the video (Bedarfshalte = request stops). So, unfortunately this can't be implemented yet.
I know it may be hard, but something worth trying on. Maybe at the start they could do a few scenarios where they don't tell the player.
Yeah, this is probably the only way to implement it as I see it, too. A few scenarios with custom stops and the player does not exactly know where the stops are at each scenario. Not really requested nor random stops, but it could work just with a little bit of imagination and mind trickery. Ahh, another situation in life, where forgetting is actually appreciated. I got to understand now, something like this is what you had in mind from the beginning. Well, then my first post is a bit of redundant. But maybe still relevant that they do not aim for a new technique like that on the official way.
I personally prefer guard mode too, but let's look at each feature request separately and don't make this thread a "I prefer this over that" discussion. This really does not fit the purpose of a pure and blank feature suggestion. But aside of that, they struggle with both features at the moment, so a higher priority for one of those is not even really there yet. Matt replied to my thread of two weeks ago where I asked why guard mode (with ticket inspection) is a feature unique to Glossop Line, and as things turned out, only to one specific scenario. He said that they're up to implement this or a similar feature for future DLCs but A. I think this can take a while still and B. might only be for certain unique scenarios (like we discuss here basically with request stops). The cool thing at the end of the discussion is that, in comparison to a guard mode which only DTG really can implement into the game, request stop scenarios are something what potentially the community with the public PC Editor easily could do. Just by going after that thinking, all it takes for request stop scenarios (like we discussed above) to take is one or some ambitous users who are ready to do a few of such on their own. This makes the probabilty for request stops a lot higher than we will ever see a guard mode in regular timetable services.
