As this appears to have reared its head again on the Brum to Crewe route, as the title states when this occurs it should not automatically end the run for the player train. DTG need to code an algorithm that removes the offending train (plus any later child components) and resets the signalling. If need be pop up a prompt advising the player what’s happened and ask if they want to continue due to potential unpredictable behaviour later in the run, but as 9 times out of 10 the SPAD might be behind the player or not directly affecting their path no reason not to carry on.
I was doing a run on wcmls the other night when I see a class 350 following a few feet behind another 350. I don't know how that wasn't a spad.
I'm not against the player SPAD ending the game as if you did that IRL you would be taken off the train, if not straight away certainly at the first point where the train could be recessed and passengers accommodated elsewhere. But an AI incident remote from the player certainly should not.
