From: Erik V. <eri...@xs...> - 2010-09-22 22:07:47
|
I have added almost the whole of the 1825 map: units 2 and 3 and the regional kits R1-3. The map has holes where yet unimplemented preprinted tiles exist. The units and kits can be selected via the Options menu. To avoid the need to create separate entries in LocalisedText.properties for each possible choice, I have extended the option parameter concept to enable separate options with the same name but different parameter values (so far option parameters could only be used for localisation of a single option with that name). So now we have in 1825/Map.xml: <IfOption name="Include" parm="Unit3" value="yes"> (unit 3 hexes) </IfOption> <IfOption name="Include" parm="Unit2" value="yes"> (Unit 2 hexes) </IfOption> <IfOption name="Include" parm="Unit1" value="yes"> (Unit 1 hexes) <IfOption name="Include" parm="R1" value="yes"> (Kit R1 hexes) </IfOption> <IfOption name="Include" parm="R2" value="yes"> (Kit R2 hexes) </IfOption> <IfOption name="Include" parm="R3" value="yes"> (Kit R3 hexes) </IfOption> </IfOption> Note the nesting: the kits R1-3 require Unit 1 to be selected. The map now also correctly displays 'strange' hex names like AA99 (Penzance in R2). I have *not* applied this concept yet to any other components: layable tiles, trains, companies etc. I will create all missing tiles; for now I suppose I can leave the rest of the configuration to Phil. For the tile and train quantities we will need a new facility to add up (+) numbers. For instance: <Tile id="6" quantity="2"> <IfOption name="Include" parm="Unit1" value="yes"> <Attributes quantity="+2"/> </IfOption> <IfOption name="Include" parm="Unit2" value="yes"> <Attributes quantity="+2"/> </IfOption> (etc.) <Upgrade id="12,13,14,15"></Upgrade> </Tile> The configuration of money and certificate limits may get complicated; perhaps we'll have to devise new tricks, or hardcode things (such as the limits in 1856). In any case, some of the 1825 XML files will become unusually bulky... Erik. |