• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Question on how to generate stats from a parent unit.

  • Thread starter Thread starter davegilbert at usa.net
  • Start date Start date
D

davegilbert at usa.net

Guest
-------------------------- eGroups Sponsor -------------------------~-~>
GET A NEXTCARD VISA, in 30 seconds! Get rates
as low as 0.0% Intro or 9.99% Ongoing APR and no annual fee!
Apply NOW!
http://click.egroups.com/1/9331/16/_/36190/_/969553543/
---------------------------------------------------------------------_->

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.


To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
-------------------------- eGroups Sponsor -------------------------~-~>
GET A NEXTCARD VISA, in 30 seconds! Get rates
as low as 0.0% Intro APR and no annual fee!
Apply NOW!
http://click.egroups.com/1/9332/16/_/36190/_/969568867/
---------------------------------------------------------------------_->

One fine day in the middle of the night, Dave Gilbert
<davegilbert@usa.net> got up to write:

>
> 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?

Give the child a type of "Something", then give the parent unit an
option with the following attribute:

chld:Something@Stat1+(Stat2)

The brackets may or may not be required, I'm not sure.

>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).

You could have a stat which held the parent's cost, and assign it to the
child as above.

--
'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
 
-------------------------- eGroups Sponsor -------------------------~-~>
Get a NextCard Visa with rates as low as 2.99% Intro APR!
1. Fill in the brief application
2. Get approval decisions in 30 seconds!
http://click.egroups.com/1/9334/16/_/36190/_/969603176/
---------------------------------------------------------------------_->

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@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
-------------------------- eGroups Sponsor -------------------------~-~>
Get a NextCard Visa, in 30 seconds!
1. Fill in the brief application
2. Get rates as low as 2.99% Intro APR with NO annual fee!
http://click.egroups.com/1/9335/16/_/36190/_/969872059/
---------------------------------------------------------------------_->

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


To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
Looks like somebody didn't read the V2.0b Beta Release email that was sent
out a couple of days ago. :-P

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

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
-------------------------- eGroups Sponsor -------------------------~-~>
GET A NEXTCARD VISA, in 30 seconds! Get rates
as low as 0.0% Intro or 9.99% Ongoing APR and no annual fee!
Apply NOW!
http://click.egroups.com/1/9331/16/_/36190/_/969897500/
---------------------------------------------------------------------_->

--- In armybuilder@egroups.com, Rob Bowes <rob@w...> wrote:
> Looks like somebody didn't read the V2.0b Beta Release email that
was sent
> out a couple of days ago. :-P

True. I've been out of it for about a week, and checked this forum
first after returning - sorry.

>
> 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@w...) (650) 726-9689
> Lone Wolf Development
www.wolflair.com


To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
You must log in or register to reply here.
Back
Top