From: Bill R. <ro...@gm...> - 2011-03-17 12:02:19
|
On 2011-03-17, at 19:20 , Erik Vos wrote: > For double-sided trains I would propose something like (for 18VA): > <TrainCertificate name="2/1G" cost="100" quantity="6"> > <Train name="2" majorStops="2"/> > <Train name="1G" majorStops="1"> > <Score towns="yes"/> > </Train> > </TrainCertificate> > Perhaps one or more additional attributes could to be added to denote Mine > and CMD access and scoring details, but actually I think these details are > so game-specific that these might as well be hardcoded. In any case, I > leave that to Stefan Frey to decide and work out. > > In the above case, the price is in the <TrainCertificate> tag, but in 18Scan > it will be in the <Train> tags because there the two trains on one card have > different prices. > (And I would replace the ambiguous 'amount' by the explicit 'quantity' > throughout. Perhaps also 'cost' by 'price'?). As the person working on 1848 (I'm more or less done the XML), I would very much appreciate the ability to define two-sided trains in XML, since 1848 has trains of the form N / N+ where one side is a standard N train, but the other (slightly more expensive) side allows calling at one extra gauge change marker. I agree with the notion that various special features (i.e. the fact that a + train in 1848 may make one extra stop at a gauge change marker) may as well be hardcoded into game-specific code. Bill |