Passing value between two seperate units

[harkan]

Am just trying to finalise the 40K Chaos for AB 3, is it possible to
pass a value between two seperate units on a roster, i.e. Unit A is
selected and then sets a value, unit B is then selected and one of
it's stats changes to match the roster level value? As an example,
in 40K, you add a greater daemon with str 8, you then designate an
aspiring champion from a seperate unit as a daemon vessel who
receives the str 8

cheers for any assistance u can give

 

[Garfunkel]

--- harkanironfist <harkanironfist@hotmail.com> a écrit :
>
>
>
> Am just trying to finalise the 40K Chaos for AB 3, is it possible to
> pass a value between two seperate units on a roster, i.e. Unit A is
> selected and then sets a value, unit B is then selected and one of
> it's stats changes to match the roster level value? As an example,
> in 40K, you add a greater daemon with str 8, you then designate an
> aspiring champion from a seperate unit as a daemon vessel who
> receives the str 8
>
> cheers for any assistance u can give


you may use tags :

Assign a global tag to your greater daemon
Create an option for your aspiring champion which modify its str to 8
depending on the presence of the global tag.
If the aspiring champion need to be unique for a agiven Greater deamon
(I dont know this rule) just add a tag to him and create a rule which
verify there is not too much aspiring champion with the upgrade.



Gafunkel






Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

 

[harkan]

Thanks, however the other prob I have is:

unit A costs X points
unit B costs Y points

both can be designated as general, however only the more expensive
unit can be the general. I tried adding a global tag and then using
script to add it to the roster the number of times equivalent to cost:

i,e, X points = X tags

and then comparing these values but you cant assign global tags via
script. So I'm not quite sure how to tackle this part of it?

--- In armybuilder@yahoogroups.com, Fred <frederic_de_bovee@y...>
wrote:
> --- harkanironfist <harkanironfist@h...> a écrit :
> >
> >
> >
> > Am just trying to finalise the 40K Chaos for AB 3, is it possible
to
> > pass a value between two seperate units on a roster, i.e. Unit A
is
> > selected and then sets a value, unit B is then selected and one
of
> > it's stats changes to match the roster level value? As an
example,
> > in 40K, you add a greater daemon with str 8, you then designate
an
> > aspiring champion from a seperate unit as a daemon vessel who
> > receives the str 8
> >
> > cheers for any assistance u can give
>
>
> you may use tags :
>
> Assign a global tag to your greater daemon
> Create an option for your aspiring champion which modify its str to
8
> depending on the presence of the global tag.
> If the aspiring champion need to be unique for a agiven Greater
deamon
> (I dont know this rule) just add a tag to him and create a rule
which
> verify there is not too much aspiring champion with the upgrade.
>
>
>
> Gafunkel
>
>
>
>
>
>
> Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour
vos mails !
> Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

 

[Colen]

At 11:17 AM 2/4/2005 +0100, you wrote:

> --- harkanironfist <harkanironfist@hotmail.com> a écrit :
> >
> >
> >
> > Am just trying to finalise the 40K Chaos for AB 3, is it possible to
> > pass a value between two seperate units on a roster, i.e. Unit A is
> > selected and then sets a value, unit B is then selected and one of
> > it's stats changes to match the roster level value? As an example,
> > in 40K, you add a greater daemon with str 8, you then designate an
> > aspiring champion from a seperate unit as a daemon vessel who
> > receives the str 8
> >
> > cheers for any assistance u can give
>
>
>you may use tags :
>
>Assign a global tag to your greater daemon
>Create an option for your aspiring champion which modify its str to 8
>depending on the presence of the global tag.
>If the aspiring champion need to be unique for a agiven Greater deamon
>(I dont know this rule) just add a tag to him and create a rule which
>verify there is not too much aspiring champion with the upgrade.


As an alternative, you could use accrued tags instead of global tags. If
the champion takes the 'Strength of a Bloodthirster' option, add a tag.
Give every bloodthister another tag. Then make a validation rule that
compares the number of bloodthirsters to the number of champions with the
'strength of a bloodthirster' option - if you have the same number, you're
fine, otherwise there's an error.



--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com

 

[Colen]

At 12:22 PM 2/4/2005 +0000, you wrote:



>Thanks, however the other prob I have is:
>
>unit A costs X points
>unit B costs Y points
>
>both can be designated as general, however only the more expensive
>unit can be the general. I tried adding a global tag and then using
>script to add it to the roster the number of times equivalent to cost:
>
>i,e, X points = X tags
>
>and then comparing these values but you cant assign global tags via
>script. So I'm not quite sure how to tackle this part of it?


That's probably not a good idea - if your general cost 500 points, you'd
have 500 tags, which is a lot.


I can think of a couple of ways you could do this, both involving a hidden
statcalc. Here's one:

First, make a statcalc with a tally expression that selects the highest
points cost. An expression like this:

if (cost[total] > @value) then
@value = cost[total]
endif

should work (in conjunction with a test expression that restricts the stat
to only characters, or whatever criteria you want). You'll now have a
statcalc with the highest points cost of any character.

Now make a rule that only applies to the general. If his points cost is
less than the value of this stat, he can't be a general and so the rule
should fail.


Hope this helps,


--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com

 

[rob]

Whenever possible, use accrued tags instead of global tags. Think of global
tags as "in case of emergency, break glass..."

The performance of accrued tags is better than global tags, and global tags
incur some SIGNIFICANT nasty issues that can force AB to re-evaluate things
heavily to sort out all the proper dependencies. This can cause your data
files to run very slowly under some circumstances if you haven't designed
your files carefully. In contrast, accrued tags have none of these
liabilities, so you can use them freely.

-Rob

At 05:34 PM 2/4/2005 -0800, you wrote:
> >Assign a global tag to your greater daemon
> >Create an option for your aspiring champion which modify its str to 8
> >depending on the presence of the global tag.
> >If the aspiring champion need to be unique for a agiven Greater deamon
> >(I dont know this rule) just add a tag to him and create a rule which
> >verify there is not too much aspiring champion with the upgrade.
>
>
>As an alternative, you could use accrued tags instead of global tags. If
>the champion takes the 'Strength of a Bloodthirster' option, add a tag.
>Give every bloodthister another tag. Then make a validation rule that
>compares the number of bloodthirsters to the number of champions with the
>'strength of a bloodthirster' option - if you have the same number, you're
>fine, otherwise there's an error.


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 588-8252
Lone Wolf Development www.wolflair.com