By using the randomisation command, the route can then randomly
pick a train out of the few. Though this only apply when one has
all the trains, if not, they'll display a "missing" train
thingy.
I have seen the command in the NSL route before, but commented
out. But my suggestion for this, is to
A) Integrate all the 3 trains into a single pack. (It may cause
issues between developers)
B) Auto detect if there is such train or not (Technically is it
even feasible?) -- Meaning, it will detect if there is a C651 (For
example), if the player does not have, then the 20% of the chances
of getting a C651 will be distributed to C151 or C751B
proportional.
C) In order to do the above (either) 2, all train
developers and route developers should have come to a standard of
Train folders structure, which I had suggested on Development
Standards thread earlier.
D) As SBS7322B mentioned, C751B is a train project, not a route
one which needs more frequent updates, and thus a website for each
train seemed overkill. So, my suggestion is to host the route +
trains in a route website as standardization. And the default
trains used and hosted in each route's site is C151 --> CGL ,
C651 --> NSL & C751B --> EWL EB / WB (Exclude CGL), with
considerations to each developers' issue.
PS: Isnt Joey did mentioned he would like to attempt C651 motor
sounds or sort of, he might be one of the next co-developer in C651
project, so this allocation seemed reasonable. (At least to me,
:P)