Digest Number 43

[armybuilder at egroups.co]

------------------------------------------------------------------------
Old school buds here:
http://click.egroups.com/1/4057/3/_/36190/_/959593864/
------------------------------------------------------------------------

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------

There are 2 messages in this issue.

Topics in this digest:

1. design problem
From: zebuleon@peoplepc.com
2. Re: design problem
From: Rob Bowes <rob@wolflair.com>


________________________________________________________________________
________________________________________________________________________

Message: 1
Date: Mon, 29 May 2000 07:52:32 -0000
From: zebuleon@peoplepc.com
Subject: design problem

I have a problem that I can't seem get to work. Heres the
background.

I have two forces, force A and force B, Force A has a unit that Force
B can use but they get a new skill, Option A, while in force B. Now
I could go through the whole process of writing up the unit in force
B's list but I'm lazy. so this is what I tried but it doesn't work.

Under unit A I went to its External Attributes and put in
"race:fa,fb" now this made it show up for each force which is fine.

Then I put "mustption=opA-race=fb"

Now according to the description of this function I should be able to
go to ArmyBuilder create a rooster for Force B, choose Unit A, and it
should have Option A. But this doesn't happen. I'm not sure if I'm
doing it wrong or not because no errors pop up. Or does this function
not actually do anything.

Any ideas

Zebuleon



________________________________________________________________________
________________________________________________________________________

Message: 2
Date: Mon, 29 May 2000 01:13:08 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: design problem

The "must" attribute is for performing validation. It does NOT have
anything to do with actually giving a unit an option. This can only be done
via linking options to units.

If I understand you're objective, the solution is to attach "opA" to the
unit normally. This will make it appear in both Force A & B. To get it to
only appear in Force B, you can use the "legl:race=fb" attribute on "opA".
This will make it only available to the unit while in Force B.

Hope this helps,
Rob


At 07:52 AM 5/29/00 +0000, you wrote:
>I have a problem that I can't seem get to work. Heres the
>background.
>
>I have two forces, force A and force B, Force A has a unit that Force
>B can use but they get a new skill, Option A, while in force B. Now
>I could go through the whole process of writing up the unit in force
>B's list but I'm lazy. so this is what I tried but it doesn't work.
>
>Under unit A I went to its External Attributes and put in
>"race:fa,fb" now this made it show up for each force which is fine.
>
>Then I put "mustption=opA-race=fb"
>
>Now according to the description of this function I should be able to
>go to ArmyBuilder create a rooster for Force B, choose Unit A, and it
>should have Option A. But this doesn't happen. I'm not sure if I'm
>doing it wrong or not because no errors pop up. Or does this function
>not actually do anything.
>
>Any ideas
>
>Zebuleon


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com


________________________________________________________________________
________________________________________________________________________