A
armybuilder at yahoogroup
Guest
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 2 messages in this issue.
Topics in this digest:
1. I had an intresting problem.....
From: "khrk2012" <Dean_Kirkpatrick@nas.adp.com>
2. Re: I had an intresting problem.....
From: Colen 'Skrillboy' McAlister <demandred@skrill.org>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Wed, 13 Feb 2002 13:10:20 -0000
From: "khrk2012" <Dean_Kirkpatrick@nas.adp.com>
Subject: I had an intresting problem.....
In a data file i was making it requried a stat be limited by the
points of the army, as in 1 per 150 pts.
I resolved this by defining a new composition group for the stat,
setting the compsition rule.
I then made a hidden child unit that would not be printed out and
this child unit then was used to midify the parents "stat", the
points of the child unit then went to the composition group for that
stat rule.
This solved the problem.
Was there a better or easier way??
Another note is there a way to stop a type. That is the parent unit
requires all child units to be a a type(type:Trooper-child) this
makes all attched units type trooper yet the squad leader if taken
isn't a trooper but an elite, is the a way to make the leader not a
Trooper? Other that defining all the other options individually as
Trooper and then the leader as an elte?
If not it would be great to add something like (type:!Trooper) which
would make this unit not a trooper. Yet all other child units
attached would be would be.
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Wed, 13 Feb 2002 16:23:36 +0000
From: Colen 'Skrillboy' McAlister <demandred@skrill.org>
Subject: Re: I had an intresting problem.....
At 13:10 13/02/2002 +0000, you wrote:
>Another note is there a way to stop a type. That is the parent unit
>requires all child units to be a a type(type:Trooper-child) this
>makes all attched units type trooper yet the squad leader if taken
>isn't a trooper but an elite, is the a way to make the leader not a
>Trooper? Other that defining all the other options individually as
>Trooper and then the leader as an elte?
>
> If not it would be great to add something like (type:!Trooper) which
>would make this unit not a trooper. Yet all other child units
>attached would be would be.
The attribute 'dtyp:Trooper' on the squad leader would delete that type.
--
Colen 'Skrillboy' McAlister, demandred@skrill.org
http://www.skrill.org/, http://www.incompetence-central.co.uk/
1 = 2, for large values of 1.
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 2 messages in this issue.
Topics in this digest:
1. I had an intresting problem.....
From: "khrk2012" <Dean_Kirkpatrick@nas.adp.com>
2. Re: I had an intresting problem.....
From: Colen 'Skrillboy' McAlister <demandred@skrill.org>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Wed, 13 Feb 2002 13:10:20 -0000
From: "khrk2012" <Dean_Kirkpatrick@nas.adp.com>
Subject: I had an intresting problem.....
In a data file i was making it requried a stat be limited by the
points of the army, as in 1 per 150 pts.
I resolved this by defining a new composition group for the stat,
setting the compsition rule.
I then made a hidden child unit that would not be printed out and
this child unit then was used to midify the parents "stat", the
points of the child unit then went to the composition group for that
stat rule.
This solved the problem.
Was there a better or easier way??
Another note is there a way to stop a type. That is the parent unit
requires all child units to be a a type(type:Trooper-child) this
makes all attched units type trooper yet the squad leader if taken
isn't a trooper but an elite, is the a way to make the leader not a
Trooper? Other that defining all the other options individually as
Trooper and then the leader as an elte?
If not it would be great to add something like (type:!Trooper) which
would make this unit not a trooper. Yet all other child units
attached would be would be.
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Wed, 13 Feb 2002 16:23:36 +0000
From: Colen 'Skrillboy' McAlister <demandred@skrill.org>
Subject: Re: I had an intresting problem.....
At 13:10 13/02/2002 +0000, you wrote:
>Another note is there a way to stop a type. That is the parent unit
>requires all child units to be a a type(type:Trooper-child) this
>makes all attched units type trooper yet the squad leader if taken
>isn't a trooper but an elite, is the a way to make the leader not a
>Trooper? Other that defining all the other options individually as
>Trooper and then the leader as an elte?
>
> If not it would be great to add something like (type:!Trooper) which
>would make this unit not a trooper. Yet all other child units
>attached would be would be.
The attribute 'dtyp:Trooper' on the squad leader would delete that type.
--
Colen 'Skrillboy' McAlister, demandred@skrill.org
http://www.skrill.org/, http://www.incompetence-central.co.uk/
1 = 2, for large values of 1.
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/