With us now having the 220, and multiple sections of the wcml, it would make sense to have a headcode hopping feature: Headcode Hopping One example for this would be 1M41, which can be playable across 4 routes in the 220 Voyager across Manchester Airport Commuter, Birmingham to Crewe (B2C), Birmingham Cross City (BXC) and Riviera Line, totalling to just over 2 hours gameplay. While it is easy enough just to search for the headcode, it'd be a nice feature to have the option at the end of a service to continue the journey on another route. Another example of this is the Walsall-Wolverhampton services, playable in game from Aston to New Street (BXC) and New Street to Wolverhampton. NOTE: This feature is not a priority: maybe a part of TSW7? There are tons of bugs and issues that are much more important than new features, so although I'd like this to get implemented at some point, I wouldn't want it to prioritise bug fixes.
This question will arise more and more in the future, as there will be more contiguous routes. It's worth noting that this would be a solution for those who find the routes and services too short in TSW.
This is a very interesting suggestion and sometime I would love to see in game eventually however, what if the routes are set in a different year and thus may not have the same timetable?
I don't know precisely how the British system works, but let's say you have two routes with two different timetables : A to B is set in 2019, but B to C is set in 2025. Your service, in 2019, was scheduled to depart B at 1617, but in 2025 it leaves at 1625... Then there will be an offset : you arrive at B at 1615, unload passengers, loading screen, and then you spawn directly at 1624 on the second route. It can work the other way around too : you arrive at 1615 and you resume at... 1606 (after the loading screen). Better that than nothing I guess... If there is absolutely no coherence at all between the two timetables, then the "continue journey" option could only work for free roam services. That raises another question which is somewhat related : "QuickDrive 2.0"... I've heard numerous voices here claiming they're not interested in long gaming sessions. Fine. But for those who complain about routes lengths, this chaining mecanism is a solution. I don't think merging routes is appropriate (at least as long as the program principle is to load every assets of the route at the beginning of your session).
