? about construction kit v2

Sorry if this has been done to death before but I am new to building
files for Armybuilder and have a question on the best way to
accomplish my goal.

I am building a file for Sassanid Persians using the Warrior Rules
from Four Horsemen Ent. For the most part things are going well
except for a reocurring issue. I have few numeric stats to deal
with in Warrior. What I do have is various "states" such as regular
v. irregular, or Extra Heavy Cav v. Super Heavy Cav. I keep running
into situations where a unit can be one of two states and an option
I want to give is priced differently depending on what state the
unit is in.

Example:

Unit A can be Extra Heavy CAv or Super heavey cav. (EHC or SHC).
This unit can then be given an option like "used to camels" for 2
pts if EHC or 3 pts if SHC.

What I have done is to build the lowest level state, EHC as the
base, assigning EHC to a stat using the attr: command. Then I build
an option "upgrade to SHC" for the cost of the pt differential. The
stat is changed using the stxt: option. Now if I want to add
the "camel proof" option ideally I would have a statement such as IF
state=EHC THEN cost=2 and IF state=SHC THEN cost=3. On top of this
I need to be able to work within a min/max rule for this unit. In
this case it might be no more than 12 elements of this type of
cavalry whether they are EHC or SHC or used to camels.

I have not been able to figure out any option which duplicates this
logic. What I have settle on is a series of multiple options which
use the hide and show options to provide the necessary choices but
that results in alot of options showing in Armybuilder that have to
be explained.

Is there a better option for this?

Thanks in advance

Joe

[Colen]

At 03:32 AM 3/19/2005 +0000, you wrote:


>Sorry if this has been done to death before but I am new to building
>files for Armybuilder and have a question on the best way to
>accomplish my goal.
>
>I am building a file for Sassanid Persians using the Warrior Rules
>from Four Horsemen Ent. For the most part things are going well
>except for a reocurring issue. I have few numeric stats to deal
>with in Warrior. What I do have is various "states" such as regular
>v. irregular, or Extra Heavy Cav v. Super Heavy Cav. I keep running
>into situations where a unit can be one of two states and an option
>I want to give is priced differently depending on what state the
>unit is in.
>
>Example:
>
>Unit A can be Extra Heavy CAv or Super heavey cav. (EHC or SHC).
>This unit can then be given an option like "used to camels" for 2
>pts if EHC or 3 pts if SHC.
>
>What I have done is to build the lowest level state, EHC as the
>base, assigning EHC to a stat using the attr: command. Then I build
>an option "upgrade to SHC" for the cost of the pt differential. The
>stat is changed using the stxt: option. Now if I want to add
>the "camel proof" option ideally I would have a statement such as IF
>state=EHC THEN cost=2 and IF state=SHC THEN cost=3. On top of this
>I need to be able to work within a min/max rule for this unit. In
>this case it might be no more than 12 elements of this type of
>cavalry whether they are EHC or SHC or used to camels.
>
>I have not been able to figure out any option which duplicates this
>logic. What I have settle on is a series of multiple options which
>use the hide and show options to provide the necessary choices but
>that results in alot of options showing in Armybuilder that have to
>be explained.
>
>Is there a better option for this?


Firstly, have you considered switching to Army Builder 3 to write your data
files? AB3 is much more flexible and powerful for AB2, and should make
writing them easier (Especially in situations like this).


For army builder 2, I think you'd need to have two "Used to camels"
options, one priced at 2, the other at 3. You'd assign a type to the unit
based on whether it was EHC or SHC. The option with a cost of 2 would have
the attribute "utyp:EHC" and the other would have an attribute "utyp:SHC".


Hope this helps,



--
Colen McAlister (colen@wolflair.com)
Chief Engineer, Lone Wolf Development
http://www.wolflair.com/