Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!
Will say it's only a limited number that have changed to "." that I've seen. For example, you won't see any from Brighton to Gatwick with route ".", but I assume that's since you can travel on two routes with those tickets, so the change could introduce extra confusion instead.
Will say it's only a limited number that have changed to "." that I've seen. For example, you won't see any from Brighton to Gatwick with route ".", but I assume that's since you can travel on two routes with those tickets, so the change could introduce extra confusion instead.
This would explain the difference between stations such as Hassocks/Burgess Hill and Brighton, such that a ticket from Brighton can be used via Hove or Lewes for such journey resulting in >1 route available.
I don't think that's the stated intention anywhere. It's certainly not the way it has been implemented, for example Manchester to Romiley would never have changed over if so.
Simplification I'd imagine as people were confused by it and without any text the casual traveller would presume "oh this is valid everywhere between A-B, doesn't say otherwise".
Elsewhere they've tended to put in a place that is on that one route, e.g. MKC to the North West are mostly routed Rugby. That's at least a bit clearer.
Simplification I'd imagine as people were confused by it and without any text the casual traveller would presume "oh this is valid everywhere between A-B, doesn't say otherwise".
I don't think that's the stated intention anywhere. It's certainly not the way it has been implemented, for example Manchester to Romiley would never have changed over if so.
Elsewhere they've tended to put in a place that is on that one route, e.g. MKC to the North West are mostly routed Rugby. That's at least a bit clearer.
Yes, but I what I was saying is that I don't think it's even ostensibly the case. It sounds like that's just one company's interpretation of the removal of Any Permitted routes.
It's very frustrating as I posted at the time the first ones were done, because lots of new ticket machines were programmed to go back to the BR convention of hiding the route entirely if the route was Any Permitted. However, they can't do so if it's just a dot, so a dot now prints where previously nothing did.
== Doublepost prevention - post automatically merged: ==
Indeed, it's actually had that opposite effect to the one intended, because a dot has to be displayed now despite it giving precisely zero information.
Yes, but I what I was saying is that I don't think it's even ostensibly the case. It sounds like that's just one company's interpretation of the removal of Any Permitted routes.
