A
armybuilder at yahoogroup
Guest
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Small business owners...
Tell us what you think!
http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 3 messages in this issue.
Topics in this digest:
1. Re: Feral Orks
From: Versif <petark@ntlworld.com>
2. Wish list
From: khrk2012@yahoo.com
3. Timing and the chld attribute, and smap for costs
From: Mathias Gehl <mgehl@home.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Mon, 30 Jul 2001 12:38:39 +0100
From: Versif <petark@ntlworld.com>
Subject: Re: Feral Orks
In this article Versif <petark@ntlworld.com> wrote
>>The reason that the Nob doesn't get the Cyboars for 5 points is because
>>the 5-pt Cyboar comes from the Options section of the unit - and as we
>>all know from the space marine scout sergeant / sniper rifle debacle
>>some time ago, sergeants / nobz only get things from the Weapons
>>section.
>
>Doh, that's why I play orks, too thick for anything else
Of course the old fungi finally kicked in and I realised that on a
normal boar he can take 'eavy armour for 8 points and avoid the
difficult terrain penalty.
For nobs generally the boar and 'eavy armour combo at 13 points probably
outweighs the "fleet of foot" cyboar at 15 points with a tendency to die
in difficult terrain.
What I don't understand is why the boarboy nob cost 34 points, a
standard nob and all other unit nobs cost 20 points. You've practically
paid for a cyboar, I wonder if it is a typo? Stranger things have
happened, after all they haven't said how far a squiggoth can move so my
interpretation would be 6" which isn't fast for a transport, but it is
fairly tough
Meanwhile I'll invest in 'eavy armour.
Cheers
Grotfang, not so humble ork warlord.
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 31 Jul 2001 02:42:04 -0000
From: khrk2012@yahoo.com
Subject: Wish list
I would like AB to include an ability to put a stat line onto options
and/or items.
I could for see this for making stat line for weapons. Such as
ranges, damage etc. - yes I know you could just write them in the
description but the stats would be - cleaner - and adjustable with
other options.
Yes, I also am aware of the "sset" and just asigning the "unit" as a
weapon, and this is a good second best. But the weapons are then
counted in the unit- Yes I am aware you can use, "coun-no" but there
are some instance when that is inconvienent.
well it is just a thought.
i would also like a ucst attribute for Items.
Just some thoughts if you run out of things to do rob!
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Mon, 30 Jul 2001 22:23:58 -0700
From: Mathias Gehl <mgehl@home.com>
Subject: Timing and the chld attribute, and smap for costs
For my GROPOS files, I would like to control an attribute at one level,
and have that level's children have the attribute at the same level.
In other words, when a platoon is set with a certain attribute at 3, all
of the members (child units) should also have the same attribute at 3.
Unfortunately, I'm not getting the chld option attribute to work. What
order (Option category/priority) should these attributes be in?:
add a platoon (child) to the company (parent)
add a unit(grand-child) to the platoon(child)
a tabl attribute to modify the stat
the options the tabl selects from
an option that calculates a second stat from the first
the chld options that transfer the two modified stats to the grand-children
Or, am I maybe getting something else wrong?
Also, I would like to make this sort of map for the cost of a platoon
vs. an attribute:
1 (Green) = 28pts
2 (Regular = 57pts
3 (Veteran) = 86pts
4 (Elite) = 129pts
(and of course the prices vary wildly between units, so I can't set up
anything universal)
I can of course set up something that will translate a stat into a cost,
and I think that's the way to get this, but I'm not sure how to get that
stat to map.
P.S. to save space on my rosters, I'm considering adding the third tier
(grand-children) via items, so that the user doesn't need to view them
all the time. Will I still be able to adjust their stat values with the
chld attribute?
Thanks, and sorry if it's unclear
Mathias Gehl
mgehl@home.com
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Small business owners...
Tell us what you think!
http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 3 messages in this issue.
Topics in this digest:
1. Re: Feral Orks
From: Versif <petark@ntlworld.com>
2. Wish list
From: khrk2012@yahoo.com
3. Timing and the chld attribute, and smap for costs
From: Mathias Gehl <mgehl@home.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Mon, 30 Jul 2001 12:38:39 +0100
From: Versif <petark@ntlworld.com>
Subject: Re: Feral Orks
In this article Versif <petark@ntlworld.com> wrote
>>The reason that the Nob doesn't get the Cyboars for 5 points is because
>>the 5-pt Cyboar comes from the Options section of the unit - and as we
>>all know from the space marine scout sergeant / sniper rifle debacle
>>some time ago, sergeants / nobz only get things from the Weapons
>>section.
>
>Doh, that's why I play orks, too thick for anything else

Of course the old fungi finally kicked in and I realised that on a
normal boar he can take 'eavy armour for 8 points and avoid the
difficult terrain penalty.
For nobs generally the boar and 'eavy armour combo at 13 points probably
outweighs the "fleet of foot" cyboar at 15 points with a tendency to die
in difficult terrain.
What I don't understand is why the boarboy nob cost 34 points, a
standard nob and all other unit nobs cost 20 points. You've practically
paid for a cyboar, I wonder if it is a typo? Stranger things have
happened, after all they haven't said how far a squiggoth can move so my
interpretation would be 6" which isn't fast for a transport, but it is
fairly tough

Cheers
Grotfang, not so humble ork warlord.
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 31 Jul 2001 02:42:04 -0000
From: khrk2012@yahoo.com
Subject: Wish list
I would like AB to include an ability to put a stat line onto options
and/or items.
I could for see this for making stat line for weapons. Such as
ranges, damage etc. - yes I know you could just write them in the
description but the stats would be - cleaner - and adjustable with
other options.
Yes, I also am aware of the "sset" and just asigning the "unit" as a
weapon, and this is a good second best. But the weapons are then
counted in the unit- Yes I am aware you can use, "coun-no" but there
are some instance when that is inconvienent.
well it is just a thought.
i would also like a ucst attribute for Items.
Just some thoughts if you run out of things to do rob!
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Mon, 30 Jul 2001 22:23:58 -0700
From: Mathias Gehl <mgehl@home.com>
Subject: Timing and the chld attribute, and smap for costs
For my GROPOS files, I would like to control an attribute at one level,
and have that level's children have the attribute at the same level.
In other words, when a platoon is set with a certain attribute at 3, all
of the members (child units) should also have the same attribute at 3.
Unfortunately, I'm not getting the chld option attribute to work. What
order (Option category/priority) should these attributes be in?:
add a platoon (child) to the company (parent)
add a unit(grand-child) to the platoon(child)
a tabl attribute to modify the stat
the options the tabl selects from
an option that calculates a second stat from the first
the chld options that transfer the two modified stats to the grand-children
Or, am I maybe getting something else wrong?
Also, I would like to make this sort of map for the cost of a platoon
vs. an attribute:
1 (Green) = 28pts
2 (Regular = 57pts
3 (Veteran) = 86pts
4 (Elite) = 129pts
(and of course the prices vary wildly between units, so I can't set up
anything universal)
I can of course set up something that will translate a stat into a cost,
and I think that's the way to get this, but I'm not sure how to get that
stat to map.
P.S. to save space on my rosters, I'm considering adding the third tier
(grand-children) via items, so that the user doesn't need to view them
all the time. Will I still be able to adjust their stat values with the
chld attribute?
Thanks, and sorry if it's unclear
Mathias Gehl
mgehl@home.com
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/