A
armybuilder at egroups.co
Guest
-------------------------- eGroups Sponsor -------------------------~-~>
Create your business web site your way now at Bigstep.com.
It's the fast, easy way to get online, to promote your business,
and to sell your products and services. Try Bigstep.com now.
http://click.egroups.com/1/9183/16/_/36190/_/969877072/
---------------------------------------------------------------------_->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 13 messages in this issue.
Topics in this digest:
1. WAB costs
From: "Bern" <bern@pcug.org.au>
2. Re: www.armageddon3.com Units
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
3. Re: Re: IG PDF force
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
4. Re: www.armageddon3.com Units
From: Versif <petark@ntlworld.com>
5. Re: www.armageddon3.com Units
From: "W.C. [Noel VH]" <noelvh@bigfoot.com>
6. Re: www.armageddon3.com Units
From: "W.C. [Noel VH]" <noelvh@bigfoot.com>
7. Re: www.armageddon3.com Units
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
8. Detachment xcmp groups
From: "Jim Kiefer" <mageith@home.com>
9. Re: IG PDF force
From: "Guy McLean" <mclean@filtec.com>
10. Re: Warhammer Epic 40K
From: Rob Bowes <rob@wolflair.com>
11. Re: Detachment xcmp groups
From: Rob Bowes <rob@wolflair.com>
12. Re: Question on how to generate stats from a parent unit.
From: "Dave Gilbert" <davegilbert@usa.net>
13. Re: Re: Question on how to generate stats from a parent unit.
From: Rob Bowes <rob@wolflair.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Sun, 24 Sep 2000 20:51:18 +1000
From: "Bern" <bern@pcug.org.au>
Subject: WAB costs
Good Evening,
I was playing with some Samurai lists and noticed a cuppla things with
the WAB files.
1. Sashimono need cost single attribute set as the 15pp is currently added
per fig, not per regiment.
2. Sam Cav and Inf do not have the increased costs in the latest errata.
3. More generally the costs in various lists include an additional +1pp for
staff slings/x-bows and longbows that came from an early Jervis errata.
This change is not included in the current errata compilation and costs
should be changed back, I expect, to match the WAB/AOA/ list costs.
Just thought I'd warn people of this.
Bern
Reality is a chronic condition,
& one generally ignored by cats.
bern@pcug.org.au
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Sun, 24 Sep 2000 12:10:26 +0100
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
Subject: Re: www.armageddon3.com Units
One fine day in the middle of the night, W.C. [Noel VH]
<noelvh@bigfoot.com> got up to write:
>AB e groups.
Was it the 'ab-files' egroup? There is no group called 'AB'.
--
'Not Colin' McAlister - License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Sun, 24 Sep 2000 12:13:33 +0100
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
Subject: Re: Re: IG PDF force
One fine day in the middle of the night, Guy McLean <mclean@filtec.com>
got up to write:
>The units that may not be used in a PDF are specifically listed on
>page 30 of Codex Armageddon. They are: Ogryns, Ratling Snipers,
>Rough Riders, Deathworld Sentinal Squadrons, Lemun Russ Vanquisher,
>Lemun Russ Exterminator. The only DW unit on this list are
>DW Sentinals.
Hmm... fair enough.
>On the previous page (p.29 of Cdx Armgddn) DW Veterans are
>specifically denoted as not allowed for Steel Legion Mechanized
>Infantry.
>
>Soooooo, I think DW Veterans are allowed in PDF detachments.
Yes, they're allowed. We're talking about Deathworld Snipers here, try
to keep up
--
'Not Colin' McAlister - License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Sun, 24 Sep 2000 12:11:46 +0100
From: Versif <petark@ntlworld.com>
Subject: Re: www.armageddon3.com Units
>Which egroups? Was it ab-files? And it's the standard Ork army list.
Don't forget to select the "Show Armageddon Troops" under "Settings"
Grotfang, not so humble ork warlord.
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Sun, 24 Sep 2000 08:39:38 -0400
From: "W.C. [Noel VH]" <noelvh@bigfoot.com>
Subject: Re: www.armageddon3.com Units
yes
'Not Colin' McAlister & The Skrills wrote:
>
>
[eGroups] My Groups | armybuilder Main Page
>
> One fine day in the middle of the night, W.C. [Noel VH]
> <noelvh@bigfoot.com> got up to write:
>
> >AB e groups.
>
> Was it the 'ab-files' egroup? There is no group called 'AB'.
>
> --
> 'Not Colin' McAlister - License to Skrill
> Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
> -----------------------------+------------------------------------
> "Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Sun, 24 Sep 2000 08:41:56 -0400
From: "W.C. [Noel VH]" <noelvh@bigfoot.com>
Subject: Re: www.armageddon3.com Units
Thank you very much I did not see that. I feel like an ass.
Sorry guys for taking up your time.
Wes.
Versif wrote:
>
>
[eGroups] My Groups | armybuilder Main Page
>
>
>
>
> >Which egroups? Was it ab-files? And it's the standard Ork army list.
>
> Don't forget to select the "Show Armageddon Troops" under "Settings"
>
>
> Grotfang, not so humble ork warlord.
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
________________________________________________________________________
________________________________________________________________________
Message: 7
Date: Sun, 24 Sep 2000 13:51:22 +0100
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
Subject: Re: www.armageddon3.com Units
One fine day in the middle of the night, W.C. [Noel VH]
<noelvh@bigfoot.com> got up to write:
>yes
Then I suggest you download the 'Beta-II' files, which are the latest,
and see what happens with them.
--
'Not Colin' McAlister - License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
________________________________________________________________________
________________________________________________________________________
Message: 8
Date: Sun, 24 Sep 2000 14:33:21 -0000
From: "Jim Kiefer" <mageith@home.com>
Subject: Detachment xcmp groups
I am attempting to program my AB for Ravening Hordes. I am nearly
complete (though the rules change daily, since I am working with
rumors).
I want detachments, which I am using a child unit, to count as a
separate member of Core composition group. I am using xcmp:. If I
make
the detachment a different xcmp group (such as rare) it counts it,
but
as long as the xcmp group of the parent and child are the same its
does not count it. For Raveninng Hordes, the count (not the
percentage) is important.
Thanks,
Jim Kiefer
________________________________________________________________________
________________________________________________________________________
Message: 9
Date: Mon, 25 Sep 2000 00:12:16 -0000
From: "Guy McLean" <mclean@filtec.com>
Subject: Re: IG PDF force
> Yes, they're allowed. We're talking about Deathworld Snipers here,
try
> to keep up
>
Errr, DW Snipers were just an example. All DW squad types (except of
course for the the Sentinals) are allowed. Plus, the standard DW
Vet upgrade for 3pts should apply as well. =)
gm
________________________________________________________________________
________________________________________________________________________
Message: 10
Date: Mon, 25 Sep 2000 00:59:53 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Warhammer Epic 40K
Those should be the Epic files. It is possible that the author of the Epic
files didn't utilize the proper ABExport utility and simply created a
generic ".zip" file. If this is the case, you will have to import the files
the manual way. Details on this method are outlined in the User Manual.
You may also want to send a "nasty-gram" to the author of the files to let
him know he ought to be packaging the files up as a proper AB import file.
Thanks, Rob
At 08:27 AM 9/24/00 +0000, you wrote:
>Tried to use the downloaded files for this, and ran into trouble.
>They are saved as .epi files, which I surmised stood for Epic, but
>they did not load into Army Builder. Am I on the entirely wrong track?
>
>David
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 11
Date: Mon, 25 Sep 2000 00:57:35 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Detachment xcmp groups
Well, this is one of those situations where you can either have it one way
or the other - but not both. For Ravening Hordes, the data files I have
seen also RELY upon having a child unit of the same composition group NOT
count as a separate unit. For example, you can select up to 2 chariots as a
single Special choice. You can also equip them differently from one
another. So the solution is to let the user split a unit of two into a
parent and child, both of which belong to the Special composition group.
This results in a parent and child unit that belong to the SAME composition
group, yet only a single choice is accounted for. There is no way to have
AB work both ways - it has to work one way OR the other.
Most likely, what you are trying to accomplish CAN still be dealt with. One
solution would be to utilize the MODEL count facet of composition groups.
When you count models, ALL models are counted separately, including those
in child units. If this won't work, you can utilize validation rules (such
as "ulmt" or "tlmt"). Between these two methods, you can probably satisfy
any constraint set forth within Ravening Hordes.
If you continue to have problems with this, please outline the specific
situation you are trying to solve and I'll do my best to suggest a workable
solution.
Thanks, Rob
At 02:33 PM 9/24/00 +0000, you wrote:
>I am attempting to program my AB for Ravening Hordes. I am nearly
>complete (though the rules change daily, since I am working with
>rumors).
>
>I want detachments, which I am using a child unit, to count as a
>separate member of Core composition group. I am using xcmp:. If I
>make
>the detachment a different xcmp group (such as rare) it counts it,
>but
>as long as the xcmp group of the parent and child are the same its
>does not count it. For Raveninng Hordes, the count (not the
>percentage) is important.
>
>Thanks,
>Jim Kiefer
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 12
Date: Mon, 25 Sep 2000 08:54:17 -0000
From: "Dave Gilbert" <davegilbert@usa.net>
Subject: Re: Question on how to generate stats from a parent unit.
Thanks for the help guys, but either I can't get the syntax right or
I'm not quite getting across what I want.
I could have up to fifty different parent units, all with differnt
stat lines. Each of them could have essentially the same child unit,
derived from the parent (ravenening hordes champion, if you hadn't
guessed). Rather than have 50 different champion units, and/or 50
different options, I would like to be able to set up 1 child unit and
1 option which I could attach to all units.
The option suggestion works O.K. provided it is coded as
chld:champ@Mv=4, but that would need 1 option per unit.
It does not work if it is coded as chld:champ@Mv=(Mv) or some variant.
What I would like is the ability to code an option such as
chld:champ@Mv=(parent Mv), or chld:champ@At=(parent At)+1.
The cost thing would work as well, but again the option
chld:champ:cst=(parent cst)+10 would be ideal.
Is this possible, or am I wishing for the moon?
--- In armybuilder@egroups.com, Rob Bowes <rob@w...> wrote:
> Colen's suggestions were exactly what I would suggest, with two
additions.
> First, once you pass the child's cost down via a stat, you'll need
to use
> the "cost" attribute on an option of the child unit to utilize that
stat as
> the cost.
>
> Secondly, if the parent unit has a complex set of options that
influence
> its cost and that information needs to be inherited by the child
unit, you
> have two options. Option #1 is to repeat those options on the child
unit
> and use the "mirr" and "only" attributes on the child to properly
reflect
> the option selections for the child. This method is optimal, but it
> requires a fair bit of work. Option #2 is much simpler. Instead of
treating
> the child unit as a separately purchased, complete unit, have the
child
> unit simply reflect the DIFFERENCES from the parent unit. This
method would
> include the child units within the parent unit's model count. That
way, all
> of the options and costing for the child unit would get included in
the
> parent (nice and simply). The child unit would only reflect the
special
> differences for the child, including the extra premium cost
incurred for
> the child unit. This method is MUCH easier to implement, but it's
probably
> not optimal as a long-term solution.
>
> Hope this helps,
> Rob
>
>
> At 04:25 PM 9/21/00 +0000, you wrote:
> > I need to set up an option which will add a child unit.
> > The stats for the child unit will be partially derived from the
> >stats of the parent unit, but there are many different parent units
> >which could have this one child.
> >
> >e.g. the child unit could have a parent unit with a move of 4 or 5
or
> >6.
> >
> >Is there any way of setting up a unit so that the stats are derived
> >from the parent?
> >
> >Secondly is there any way of deriving the unit cost of the child
from
> >the parent? (A child model should cost as much as a parent model,
> >which is variable, plus a few points).
> >
> >Hope someone can help, as this is driving me nuts.
>
>
> --------------------------------------------------------------------
-------
> Rob Bowes (rob@w...) (650) 726-9689
> Lone Wolf Development
www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 13
Date: Mon, 25 Sep 2000 02:03:51 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Re: Question on how to generate stats from a parent unit.
Looks like somebody didn't read the V2.0b Beta Release email that was sent
out a couple of days ago.
You can do EXACTLY what you propose below within V2.0b. The "chld"
attribute allows you to use a formula. The only problem is that V2.0a is
not allowing you to self-reference the stat within the attribute. For
example, you CAN currently say "chld:champ@St=(Mv+2)", but you CAN'T say
"chld:champ@St=(St+2)". The second usage is self-referential, so AB says
you can't do it. However, the self-reference limitation should only apply
to the "stat" and "base" attributes - NOT the "prnt" and "chld" attributes.
This has been fixed in V2.0b.
I recommend that you go back and read the Beta release announcement from a
few days ago on the Beta forum.
Thanks, Rob
At 08:54 AM 9/25/00 +0000, you wrote:
>Thanks for the help guys, but either I can't get the syntax right or
>I'm not quite getting across what I want.
>
>I could have up to fifty different parent units, all with differnt
>stat lines. Each of them could have essentially the same child unit,
>derived from the parent (ravenening hordes champion, if you hadn't
>guessed). Rather than have 50 different champion units, and/or 50
>different options, I would like to be able to set up 1 child unit and
>1 option which I could attach to all units.
>
>The option suggestion works O.K. provided it is coded as
>chld:champ@Mv=4, but that would need 1 option per unit.
>It does not work if it is coded as chld:champ@Mv=(Mv) or some variant.
>What I would like is the ability to code an option such as
>chld:champ@Mv=(parent Mv), or chld:champ@At=(parent At)+1.
>The cost thing would work as well, but again the option
>chld:champ:cst=(parent cst)+10 would be ideal.
>
>Is this possible, or am I wishing for the moon?
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Create your business web site your way now at Bigstep.com.
It's the fast, easy way to get online, to promote your business,
and to sell your products and services. Try Bigstep.com now.
http://click.egroups.com/1/9183/16/_/36190/_/969877072/
---------------------------------------------------------------------_->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 13 messages in this issue.
Topics in this digest:
1. WAB costs
From: "Bern" <bern@pcug.org.au>
2. Re: www.armageddon3.com Units
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
3. Re: Re: IG PDF force
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
4. Re: www.armageddon3.com Units
From: Versif <petark@ntlworld.com>
5. Re: www.armageddon3.com Units
From: "W.C. [Noel VH]" <noelvh@bigfoot.com>
6. Re: www.armageddon3.com Units
From: "W.C. [Noel VH]" <noelvh@bigfoot.com>
7. Re: www.armageddon3.com Units
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
8. Detachment xcmp groups
From: "Jim Kiefer" <mageith@home.com>
9. Re: IG PDF force
From: "Guy McLean" <mclean@filtec.com>
10. Re: Warhammer Epic 40K
From: Rob Bowes <rob@wolflair.com>
11. Re: Detachment xcmp groups
From: Rob Bowes <rob@wolflair.com>
12. Re: Question on how to generate stats from a parent unit.
From: "Dave Gilbert" <davegilbert@usa.net>
13. Re: Re: Question on how to generate stats from a parent unit.
From: Rob Bowes <rob@wolflair.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Sun, 24 Sep 2000 20:51:18 +1000
From: "Bern" <bern@pcug.org.au>
Subject: WAB costs
Good Evening,
I was playing with some Samurai lists and noticed a cuppla things with
the WAB files.
1. Sashimono need cost single attribute set as the 15pp is currently added
per fig, not per regiment.
2. Sam Cav and Inf do not have the increased costs in the latest errata.
3. More generally the costs in various lists include an additional +1pp for
staff slings/x-bows and longbows that came from an early Jervis errata.
This change is not included in the current errata compilation and costs
should be changed back, I expect, to match the WAB/AOA/ list costs.
Just thought I'd warn people of this.
Bern
Reality is a chronic condition,
& one generally ignored by cats.
bern@pcug.org.au
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Sun, 24 Sep 2000 12:10:26 +0100
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
Subject: Re: www.armageddon3.com Units
One fine day in the middle of the night, W.C. [Noel VH]
<noelvh@bigfoot.com> got up to write:
>AB e groups.
Was it the 'ab-files' egroup? There is no group called 'AB'.
--
'Not Colin' McAlister - License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Sun, 24 Sep 2000 12:13:33 +0100
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
Subject: Re: Re: IG PDF force
One fine day in the middle of the night, Guy McLean <mclean@filtec.com>
got up to write:
>The units that may not be used in a PDF are specifically listed on
>page 30 of Codex Armageddon. They are: Ogryns, Ratling Snipers,
>Rough Riders, Deathworld Sentinal Squadrons, Lemun Russ Vanquisher,
>Lemun Russ Exterminator. The only DW unit on this list are
>DW Sentinals.
Hmm... fair enough.
>On the previous page (p.29 of Cdx Armgddn) DW Veterans are
>specifically denoted as not allowed for Steel Legion Mechanized
>Infantry.
>
>Soooooo, I think DW Veterans are allowed in PDF detachments.
Yes, they're allowed. We're talking about Deathworld Snipers here, try
to keep up
--
'Not Colin' McAlister - License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Sun, 24 Sep 2000 12:11:46 +0100
From: Versif <petark@ntlworld.com>
Subject: Re: www.armageddon3.com Units
>Which egroups? Was it ab-files? And it's the standard Ork army list.
Don't forget to select the "Show Armageddon Troops" under "Settings"
Grotfang, not so humble ork warlord.
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Sun, 24 Sep 2000 08:39:38 -0400
From: "W.C. [Noel VH]" <noelvh@bigfoot.com>
Subject: Re: www.armageddon3.com Units
yes
'Not Colin' McAlister & The Skrills wrote:
>
>
[eGroups] My Groups | armybuilder Main Page
>
> One fine day in the middle of the night, W.C. [Noel VH]
> <noelvh@bigfoot.com> got up to write:
>
> >AB e groups.
>
> Was it the 'ab-files' egroup? There is no group called 'AB'.
>
> --
> 'Not Colin' McAlister - License to Skrill
> Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
> -----------------------------+------------------------------------
> "Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Sun, 24 Sep 2000 08:41:56 -0400
From: "W.C. [Noel VH]" <noelvh@bigfoot.com>
Subject: Re: www.armageddon3.com Units
Thank you very much I did not see that. I feel like an ass.
Sorry guys for taking up your time.
Wes.
Versif wrote:
>
>
[eGroups] My Groups | armybuilder Main Page
>
>
>
>
> >Which egroups? Was it ab-files? And it's the standard Ork army list.
>
> Don't forget to select the "Show Armageddon Troops" under "Settings"
>
>
> Grotfang, not so humble ork warlord.
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
________________________________________________________________________
________________________________________________________________________
Message: 7
Date: Sun, 24 Sep 2000 13:51:22 +0100
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
Subject: Re: www.armageddon3.com Units
One fine day in the middle of the night, W.C. [Noel VH]
<noelvh@bigfoot.com> got up to write:
>yes
Then I suggest you download the 'Beta-II' files, which are the latest,
and see what happens with them.
--
'Not Colin' McAlister - License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
________________________________________________________________________
________________________________________________________________________
Message: 8
Date: Sun, 24 Sep 2000 14:33:21 -0000
From: "Jim Kiefer" <mageith@home.com>
Subject: Detachment xcmp groups
I am attempting to program my AB for Ravening Hordes. I am nearly
complete (though the rules change daily, since I am working with
rumors).
I want detachments, which I am using a child unit, to count as a
separate member of Core composition group. I am using xcmp:. If I
make
the detachment a different xcmp group (such as rare) it counts it,
but
as long as the xcmp group of the parent and child are the same its
does not count it. For Raveninng Hordes, the count (not the
percentage) is important.
Thanks,
Jim Kiefer
________________________________________________________________________
________________________________________________________________________
Message: 9
Date: Mon, 25 Sep 2000 00:12:16 -0000
From: "Guy McLean" <mclean@filtec.com>
Subject: Re: IG PDF force
> Yes, they're allowed. We're talking about Deathworld Snipers here,
try
> to keep up
>
Errr, DW Snipers were just an example. All DW squad types (except of
course for the the Sentinals) are allowed. Plus, the standard DW
Vet upgrade for 3pts should apply as well. =)
gm
________________________________________________________________________
________________________________________________________________________
Message: 10
Date: Mon, 25 Sep 2000 00:59:53 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Warhammer Epic 40K
Those should be the Epic files. It is possible that the author of the Epic
files didn't utilize the proper ABExport utility and simply created a
generic ".zip" file. If this is the case, you will have to import the files
the manual way. Details on this method are outlined in the User Manual.
You may also want to send a "nasty-gram" to the author of the files to let
him know he ought to be packaging the files up as a proper AB import file.
Thanks, Rob
At 08:27 AM 9/24/00 +0000, you wrote:
>Tried to use the downloaded files for this, and ran into trouble.
>They are saved as .epi files, which I surmised stood for Epic, but
>they did not load into Army Builder. Am I on the entirely wrong track?
>
>David
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 11
Date: Mon, 25 Sep 2000 00:57:35 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Detachment xcmp groups
Well, this is one of those situations where you can either have it one way
or the other - but not both. For Ravening Hordes, the data files I have
seen also RELY upon having a child unit of the same composition group NOT
count as a separate unit. For example, you can select up to 2 chariots as a
single Special choice. You can also equip them differently from one
another. So the solution is to let the user split a unit of two into a
parent and child, both of which belong to the Special composition group.
This results in a parent and child unit that belong to the SAME composition
group, yet only a single choice is accounted for. There is no way to have
AB work both ways - it has to work one way OR the other.
Most likely, what you are trying to accomplish CAN still be dealt with. One
solution would be to utilize the MODEL count facet of composition groups.
When you count models, ALL models are counted separately, including those
in child units. If this won't work, you can utilize validation rules (such
as "ulmt" or "tlmt"). Between these two methods, you can probably satisfy
any constraint set forth within Ravening Hordes.
If you continue to have problems with this, please outline the specific
situation you are trying to solve and I'll do my best to suggest a workable
solution.
Thanks, Rob
At 02:33 PM 9/24/00 +0000, you wrote:
>I am attempting to program my AB for Ravening Hordes. I am nearly
>complete (though the rules change daily, since I am working with
>rumors).
>
>I want detachments, which I am using a child unit, to count as a
>separate member of Core composition group. I am using xcmp:. If I
>make
>the detachment a different xcmp group (such as rare) it counts it,
>but
>as long as the xcmp group of the parent and child are the same its
>does not count it. For Raveninng Hordes, the count (not the
>percentage) is important.
>
>Thanks,
>Jim Kiefer
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 12
Date: Mon, 25 Sep 2000 08:54:17 -0000
From: "Dave Gilbert" <davegilbert@usa.net>
Subject: Re: Question on how to generate stats from a parent unit.
Thanks for the help guys, but either I can't get the syntax right or
I'm not quite getting across what I want.
I could have up to fifty different parent units, all with differnt
stat lines. Each of them could have essentially the same child unit,
derived from the parent (ravenening hordes champion, if you hadn't
guessed). Rather than have 50 different champion units, and/or 50
different options, I would like to be able to set up 1 child unit and
1 option which I could attach to all units.
The option suggestion works O.K. provided it is coded as
chld:champ@Mv=4, but that would need 1 option per unit.
It does not work if it is coded as chld:champ@Mv=(Mv) or some variant.
What I would like is the ability to code an option such as
chld:champ@Mv=(parent Mv), or chld:champ@At=(parent At)+1.
The cost thing would work as well, but again the option
chld:champ:cst=(parent cst)+10 would be ideal.
Is this possible, or am I wishing for the moon?
--- In armybuilder@egroups.com, Rob Bowes <rob@w...> wrote:
> Colen's suggestions were exactly what I would suggest, with two
additions.
> First, once you pass the child's cost down via a stat, you'll need
to use
> the "cost" attribute on an option of the child unit to utilize that
stat as
> the cost.
>
> Secondly, if the parent unit has a complex set of options that
influence
> its cost and that information needs to be inherited by the child
unit, you
> have two options. Option #1 is to repeat those options on the child
unit
> and use the "mirr" and "only" attributes on the child to properly
reflect
> the option selections for the child. This method is optimal, but it
> requires a fair bit of work. Option #2 is much simpler. Instead of
treating
> the child unit as a separately purchased, complete unit, have the
child
> unit simply reflect the DIFFERENCES from the parent unit. This
method would
> include the child units within the parent unit's model count. That
way, all
> of the options and costing for the child unit would get included in
the
> parent (nice and simply). The child unit would only reflect the
special
> differences for the child, including the extra premium cost
incurred for
> the child unit. This method is MUCH easier to implement, but it's
probably
> not optimal as a long-term solution.
>
> Hope this helps,
> Rob
>
>
> At 04:25 PM 9/21/00 +0000, you wrote:
> > I need to set up an option which will add a child unit.
> > The stats for the child unit will be partially derived from the
> >stats of the parent unit, but there are many different parent units
> >which could have this one child.
> >
> >e.g. the child unit could have a parent unit with a move of 4 or 5
or
> >6.
> >
> >Is there any way of setting up a unit so that the stats are derived
> >from the parent?
> >
> >Secondly is there any way of deriving the unit cost of the child
from
> >the parent? (A child model should cost as much as a parent model,
> >which is variable, plus a few points).
> >
> >Hope someone can help, as this is driving me nuts.
>
>
> --------------------------------------------------------------------
-------
> Rob Bowes (rob@w...) (650) 726-9689
> Lone Wolf Development
www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 13
Date: Mon, 25 Sep 2000 02:03:51 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Re: Question on how to generate stats from a parent unit.
Looks like somebody didn't read the V2.0b Beta Release email that was sent
out a couple of days ago.
You can do EXACTLY what you propose below within V2.0b. The "chld"
attribute allows you to use a formula. The only problem is that V2.0a is
not allowing you to self-reference the stat within the attribute. For
example, you CAN currently say "chld:champ@St=(Mv+2)", but you CAN'T say
"chld:champ@St=(St+2)". The second usage is self-referential, so AB says
you can't do it. However, the self-reference limitation should only apply
to the "stat" and "base" attributes - NOT the "prnt" and "chld" attributes.
This has been fixed in V2.0b.
I recommend that you go back and read the Beta release announcement from a
few days ago on the Beta forum.
Thanks, Rob
At 08:54 AM 9/25/00 +0000, you wrote:
>Thanks for the help guys, but either I can't get the syntax right or
>I'm not quite getting across what I want.
>
>I could have up to fifty different parent units, all with differnt
>stat lines. Each of them could have essentially the same child unit,
>derived from the parent (ravenening hordes champion, if you hadn't
>guessed). Rather than have 50 different champion units, and/or 50
>different options, I would like to be able to set up 1 child unit and
>1 option which I could attach to all units.
>
>The option suggestion works O.K. provided it is coded as
>chld:champ@Mv=4, but that would need 1 option per unit.
>It does not work if it is coded as chld:champ@Mv=(Mv) or some variant.
>What I would like is the ability to code an option such as
>chld:champ@Mv=(parent Mv), or chld:champ@At=(parent At)+1.
>The cost thing would work as well, but again the option
>chld:champ:cst=(parent cst)+10 would be ideal.
>
>Is this possible, or am I wishing for the moon?
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________