From: Erik V. <eri...@xs...> - 2012-05-14 15:15:59
|
It turns out that we already have an <Action> tag within <Phase>, with attributes 'name' and 'value' (value is unused). This tag is currently only used for 1880. We could modify or extend that tag, e.g. like <Action name="formStateRR" value="KK;may_start"/>, allowing value to have a sequence of values. Perhaps it is nicer to replace 'value' by more meaningful attributes, such as 'company' for actions that affect a company, and 'step' to specify an action step. Erik > > I propose that the timing of conversions be specified in > > data/1837/Game.xml. > > The <Phase> list would get another new type of entry: > > > > <StateRR name="KK" action="may_start"/> > > <StateRR name="KK" action="must_start"/> > > <StateRR name="KK" action="all_must_merge"/> > > > > Each of these would appear in the phase list to indicate when the > > event occurs for that company. Where there isn't a choice of timing > > (as for the Southern National, which must form AND all its minors must > > merge as soon as the first 4-train is purchased), the earlier steps > > can be skipped; "all_must_merge" will do the whole job in that case. > > Sounds good, but perhaps we can better create a more generic <Action> tag > for such specials. > Something like <Action type="formStateRR" company="KK" > step="may_start"/> etc. > > I remember phase actions have been discussed in the past, but I'll have to > refresh my memory on that subject. |