A
armybuilder at egroups.co
Guest
-------------------------- eGroups Sponsor -------------------------~-~>
GET A NEXTCARD VISA, in 30 seconds! Get rates
of 2.9% Intro or 9.9% Ongoing APR* and no annual fee!
Apply NOW!
http://click.egroups.com/1/7872/4/_/36190/_/967547290/
---------------------------------------------------------------------_->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 6 messages in this issue.
Topics in this digest:
1. Re: lglx or itst
From: Rob Bowes <rob@wolflair.com>
2. RE: lglx or itst
From: "Russell Sparkes" <rjs@inorbit.com>
3. Fwd: Re: Ravening Hordes?
From: Phil Groff <philip@psych.utoronto.ca>
4. Re: Data File creation strategy (B5W-FA)
From: Mathias Gehl <mgehl@home.com>
5. Re: Data File creation strategy (B5W-FA)
From: Rob Bowes <rob@wolflair.com>
6. Re: Fwd: Re: Ravening Hordes?
From: Rob Moser <moser@cse.unsw.edu.au>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Mon, 28 Aug 2000 19:21:00 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: lglx or itst
At 12:35 PM 8/29/00 +1100, you wrote:
>There's two ways to do race restriction on an item.
>lglx:race=xx OR itst:race=xx
>
>Is one better than the other? Is there a difference?
The "lglx" attribute is applied immediately when the roster is created. If
an item doesn't satisfy the "lglx" attribute, it's never shown and never
even considered by AB. This is definitely the preferable mechanism for
performance. The "itst" mechanism really makes no sense for a simple
"race=xx" test. Where it's real power comes from is the ability to write
boolean expressions that are based on the race, type, category, and all
sorts of other things. Some items are only available to units of type XX in
a given race, and "itst" makes this possible.
Hope this helps,
Rob
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 29 Aug 2000 13:33:59 +1100
From: "Russell Sparkes" <rjs@inorbit.com>
Subject: RE: lglx or itst
Thanks, that was exactly the answer I was after
> -----Original Message-----
> From: Rob Bowes [mailto:rob@wolflair.com]
> Sent: Tuesday, 29 August 2000 1:21 PM
> To: armybuilder@egroups.com
> Subject: Re: [AB] lglx or itst
>
>
> At 12:35 PM 8/29/00 +1100, you wrote:
> >There's two ways to do race restriction on an item.
> >lglx:race=xx OR itst:race=xx
> >
> >Is one better than the other? Is there a difference?
>
> The "lglx" attribute is applied immediately when the roster
> is created. If
> an item doesn't satisfy the "lglx" attribute, it's never
> shown and never
> even considered by AB. This is definitely the preferable
> mechanism for
> performance. The "itst" mechanism really makes no sense for a simple
> "race=xx" test. Where it's real power comes from is the
> ability to write
> boolean expressions that are based on the race, type,
> category, and all
> sorts of other things. Some items are only available to units
> of type XX in
> a given race, and "itst" makes this possible.
>
> Hope this helps,
> Rob
>
> --------------------------------------------------------------
> -------------
> Rob Bowes (rob@wolflair.com)
> (650) 726-9689
> Lone Wolf Development
> www.wolflair.com
>
> -------------------------- eGroups Sponsor
> -------------------------~-~>
> GET A NEXTCARD VISA, in 30 seconds! Get rates
> of 2.9% Intro or 9.9% Ongoing APR* and no annual fee!
> Apply NOW!
> http://click.egroups.com/1/7872/4/_/36190/_/967515524/
> --------------------------------------------------------------
> -------_->
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
>
>
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Mon, 28 Aug 2000 23:12:44 -0400
From: Phil Groff <philip@psych.utoronto.ca>
Subject: Fwd: Re: Ravening Hordes?
[This message is not in displayable format]
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Mon, 28 Aug 2000 20:38:57 -0700
From: Mathias Gehl <mgehl@home.com>
Subject: Re: Data File creation strategy (B5W-FA)
I would like to be able to accumulate more than one stat for each
leader-follower set (using the -accum modifier). Is this possible?
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Mon, 28 Aug 2000 20:56:17 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Data File creation strategy (B5W-FA)
At 08:38 PM 8/28/00 -0700, you wrote:
>I would like to be able to accumulate more than one stat for each
>leader-follower set (using the -accum modifier). Is this possible?
Each leader/follower set can accumulate only one stat. What are you trying
to accomplish? I'm surprised that you need to accumulate more than one stat
within a single leader/follower set.
Thanks, Rob
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Tue, 29 Aug 2000 14:59:58 +1100 (EST)
From: Rob Moser <moser@cse.unsw.edu.au>
Subject: Re: Fwd: Re: Ravening Hordes?
Done, but don't expect me to necessarily keep this version up to date with
any updates he posts. Its at:
http://www.egroups.com/files/ab-files/WFB/6EDVersion1.ab
You also may want to consider not posting your mail in HTML...
- rob.
Phil Groff quoth:
> <html>
>
> <blockquote type=cite cite>X-eGroups-Return:
<blah>
________________________________________________________________________
________________________________________________________________________
GET A NEXTCARD VISA, in 30 seconds! Get rates
of 2.9% Intro or 9.9% Ongoing APR* and no annual fee!
Apply NOW!
http://click.egroups.com/1/7872/4/_/36190/_/967547290/
---------------------------------------------------------------------_->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 6 messages in this issue.
Topics in this digest:
1. Re: lglx or itst
From: Rob Bowes <rob@wolflair.com>
2. RE: lglx or itst
From: "Russell Sparkes" <rjs@inorbit.com>
3. Fwd: Re: Ravening Hordes?
From: Phil Groff <philip@psych.utoronto.ca>
4. Re: Data File creation strategy (B5W-FA)
From: Mathias Gehl <mgehl@home.com>
5. Re: Data File creation strategy (B5W-FA)
From: Rob Bowes <rob@wolflair.com>
6. Re: Fwd: Re: Ravening Hordes?
From: Rob Moser <moser@cse.unsw.edu.au>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Mon, 28 Aug 2000 19:21:00 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: lglx or itst
At 12:35 PM 8/29/00 +1100, you wrote:
>There's two ways to do race restriction on an item.
>lglx:race=xx OR itst:race=xx
>
>Is one better than the other? Is there a difference?
The "lglx" attribute is applied immediately when the roster is created. If
an item doesn't satisfy the "lglx" attribute, it's never shown and never
even considered by AB. This is definitely the preferable mechanism for
performance. The "itst" mechanism really makes no sense for a simple
"race=xx" test. Where it's real power comes from is the ability to write
boolean expressions that are based on the race, type, category, and all
sorts of other things. Some items are only available to units of type XX in
a given race, and "itst" makes this possible.
Hope this helps,
Rob
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 29 Aug 2000 13:33:59 +1100
From: "Russell Sparkes" <rjs@inorbit.com>
Subject: RE: lglx or itst
Thanks, that was exactly the answer I was after
> -----Original Message-----
> From: Rob Bowes [mailto:rob@wolflair.com]
> Sent: Tuesday, 29 August 2000 1:21 PM
> To: armybuilder@egroups.com
> Subject: Re: [AB] lglx or itst
>
>
> At 12:35 PM 8/29/00 +1100, you wrote:
> >There's two ways to do race restriction on an item.
> >lglx:race=xx OR itst:race=xx
> >
> >Is one better than the other? Is there a difference?
>
> The "lglx" attribute is applied immediately when the roster
> is created. If
> an item doesn't satisfy the "lglx" attribute, it's never
> shown and never
> even considered by AB. This is definitely the preferable
> mechanism for
> performance. The "itst" mechanism really makes no sense for a simple
> "race=xx" test. Where it's real power comes from is the
> ability to write
> boolean expressions that are based on the race, type,
> category, and all
> sorts of other things. Some items are only available to units
> of type XX in
> a given race, and "itst" makes this possible.
>
> Hope this helps,
> Rob
>
> --------------------------------------------------------------
> -------------
> Rob Bowes (rob@wolflair.com)
> (650) 726-9689
> Lone Wolf Development
> www.wolflair.com
>
> -------------------------- eGroups Sponsor
> -------------------------~-~>
> GET A NEXTCARD VISA, in 30 seconds! Get rates
> of 2.9% Intro or 9.9% Ongoing APR* and no annual fee!
> Apply NOW!
> http://click.egroups.com/1/7872/4/_/36190/_/967515524/
> --------------------------------------------------------------
> -------_->
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
>
>
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Mon, 28 Aug 2000 23:12:44 -0400
From: Phil Groff <philip@psych.utoronto.ca>
Subject: Fwd: Re: Ravening Hordes?
[This message is not in displayable format]
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Mon, 28 Aug 2000 20:38:57 -0700
From: Mathias Gehl <mgehl@home.com>
Subject: Re: Data File creation strategy (B5W-FA)
I would like to be able to accumulate more than one stat for each
leader-follower set (using the -accum modifier). Is this possible?
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Mon, 28 Aug 2000 20:56:17 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Data File creation strategy (B5W-FA)
At 08:38 PM 8/28/00 -0700, you wrote:
>I would like to be able to accumulate more than one stat for each
>leader-follower set (using the -accum modifier). Is this possible?
Each leader/follower set can accumulate only one stat. What are you trying
to accomplish? I'm surprised that you need to accumulate more than one stat
within a single leader/follower set.
Thanks, Rob
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Tue, 29 Aug 2000 14:59:58 +1100 (EST)
From: Rob Moser <moser@cse.unsw.edu.au>
Subject: Re: Fwd: Re: Ravening Hordes?
Done, but don't expect me to necessarily keep this version up to date with
any updates he posts. Its at:
http://www.egroups.com/files/ab-files/WFB/6EDVersion1.ab
You also may want to consider not posting your mail in HTML...
- rob.
Phil Groff quoth:
> <html>
>
> <blockquote type=cite cite>X-eGroups-Return:
<blah>
________________________________________________________________________
________________________________________________________________________