Items cost being rolled up into parent

All,

I have one final issue to overcome and my datafiles will be complete!

Here is the scenario:

I have Units of "Type=hero" in my army. Only 50% of an Army's
points may be spent on units(models) of "type=hero" so I have
a "tlmt" attribute set on the race to throw a validation message
when the percentage is exceeded.

I have a comp group called "ice witches" that contains units
of "type=hero" as well as units of other types. I want to be able
to select an item "magic crystal" for any unit or model in comp
group "ice witches". The cost of item "magic crystal" SHOULD COUNT
AGAINST the "ice witch" comp group, but NOT AGAINST the "tlmt"
on "type=hero"; In other words I want the items cost NOT to be
rolled into the cost of the parent unit for purposes of this
specific validation, while not affectings its being processed as
part of the "ice witch" comp group.

I have looked at the "comp" option attribute and have had no success
getting it to work. I have even tried making child units instead of
items to no success. I am sure I am missing something so please
enlighten me.

Thanks for the help.

Woody





------------------------ Yahoo! Groups Sponsor ---------------------~-->
FREE COLLEGE MONEY
CLICK HERE to search
600,000 scholarships!
http://us.click.yahoo.com/47cccB/4m7...SFAA/IMSolB/TM
---------------------------------------------------------------------~->

[rob]

This goes against the fundamental way that AB is designed (i.e. costs are
accumulated into units and units are counted against limits). The only way
I can think of to solve this is to use two separate units....

When an ice witch is added to the roster, create a separate child unit. To
make this clean for the user, you'll have to have the ice witch cost its
normal price. However, to make this trick work, you'll have to attach a
separate hidden option with the witch cost as a rebate (i.e. if an ice
witch costs 50 points, then the option cost must be -50). Attach this
optoin via an "auto" nature. Then assign the standard price of the ice
witch to the child unit. The net result of this is that you have a parent
and child unit, with the net price of the parent unit equal to the proper
sum, but the cost is actually separated between the two units.

The next step is to assign the parent unit to the proper composition group.
Then allow the user to select the magic crystals (and other items) for the
parent unit. The child unit serves only one purpose, which is to total up
the "hero" points properly. The child unit must be assigned to the "N/A"
composition group and its count must be identical to the parent unit (you
can attach it via the "unit" attribute with the "per=1" form). Next you
assign the "hero" type to the child unit, but you DON'T assign this type to
the parent unit. Lastly, you need to assign the "forc" attribute to the
child unit so that it is properly included in validation rules.

The net result of all this is that the child unit accumulates the total
cost of all ice witches into the "hero" limitation. Meanwhile, the parent
unit is what the user mucks with and where the user assigns magic crystals
and anything else that applies towards the composition limit for the ice
witches.

It's a bit convoluted in concept, but it ought to work reasonably cleanly
and be only a minor annoyance for the user (i.e. the extra child unit that
does nothing useful). You can also designate the child unit as
"non-printing" via the "disp" attribute.

Hope this helps,
Rob


At 05:35 AM 9/9/2001 +0000, you wrote:
>All,
>
>I have one final issue to overcome and my datafiles will be complete!
>
>Here is the scenario:
>
>I have Units of "Type=hero" in my army. Only 50% of an Army's
>points may be spent on units(models) of "type=hero" so I have
>a "tlmt" attribute set on the race to throw a validation message
>when the percentage is exceeded.
>
>I have a comp group called "ice witches" that contains units
>of "type=hero" as well as units of other types. I want to be able
>to select an item "magic crystal" for any unit or model in comp
>group "ice witches". The cost of item "magic crystal" SHOULD COUNT
>AGAINST the "ice witch" comp group, but NOT AGAINST the "tlmt"
>on "type=hero"; In other words I want the items cost NOT to be
>rolled into the cost of the parent unit for purposes of this
>specific validation, while not affectings its being processed as
>part of the "ice witch" comp group.
>
>I have looked at the "comp" option attribute and have had no success
>getting it to work. I have even tried making child units instead of
>items to no success. I am sure I am missing something so please
>enlighten me.
>
>Thanks for the help.
>
>Woody


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com


------------------------ Yahoo! Groups Sponsor ---------------------~-->
FREE COLLEGE MONEY
CLICK HERE to search
600,000 scholarships!
http://us.click.yahoo.com/47cccB/4m7...SFAA/IMSolB/TM
---------------------------------------------------------------------~->

Brilliant! too bad I didn't think of it! ;-)


Woody




--- In armybuilder@y..., Rob Bowes <rob@w...> wrote:
> This goes against the fundamental way that AB is designed (i.e.
costs are
> accumulated into units and units are counted against limits). The
only way
> I can think of to solve this is to use two separate units....
>
> When an ice witch is added to the roster, create a separate child
unit. To
> make this clean for the user, you'll have to have the ice witch
cost its
> normal price. However, to make this trick work, you'll have to
attach a
> separate hidden option with the witch cost as a rebate (i.e. if an
ice
> witch costs 50 points, then the option cost must be -50). Attach
this
> optoin via an "auto" nature. Then assign the standard price of the
ice
> witch to the child unit. The net result of this is that you have a
parent
> and child unit, with the net price of the parent unit equal to the
proper
> sum, but the cost is actually separated between the two units.
>
> The next step is to assign the parent unit to the proper
composition group.
> Then allow the user to select the magic crystals (and other items)
for the
> parent unit. The child unit serves only one purpose, which is to
total up
> the "hero" points properly. The child unit must be assigned to
the "N/A"
> composition group and its count must be identical to the parent
unit (you
> can attach it via the "unit" attribute with the "per=1" form).
Next you
> assign the "hero" type to the child unit, but you DON'T assign
this type to
> the parent unit. Lastly, you need to assign the "forc" attribute
to the
> child unit so that it is properly included in validation rules.
>
> The net result of all this is that the child unit accumulates the
total
> cost of all ice witches into the "hero" limitation. Meanwhile, the
parent
> unit is what the user mucks with and where the user assigns magic
crystals
> and anything else that applies towards the composition limit for
the ice
> witches.
>
> It's a bit convoluted in concept, but it ought to work reasonably
cleanly
> and be only a minor annoyance for the user (i.e. the extra child
unit that
> does nothing useful). You can also designate the child unit as
> "non-printing" via the "disp" attribute.
>
> Hope this helps,
> Rob
>
>
> At 05:35 AM 9/9/2001 +0000, you wrote:
> >All,
> >
> >I have one final issue to overcome and my datafiles will be
complete!
> >
> >Here is the scenario:
> >
> >I have Units of "Type=hero" in my army. Only 50% of an Army's
> >points may be spent on units(models) of "type=hero" so I have
> >a "tlmt" attribute set on the race to throw a validation message
> >when the percentage is exceeded.
> >
> >I have a comp group called "ice witches" that contains units
> >of "type=hero" as well as units of other types. I want to be able
> >to select an item "magic crystal" for any unit or model in comp
> >group "ice witches". The cost of item "magic crystal" SHOULD COUNT
> >AGAINST the "ice witch" comp group, but NOT AGAINST the "tlmt"
> >on "type=hero"; In other words I want the items cost NOT to be
> >rolled into the cost of the parent unit for purposes of this
> >specific validation, while not affectings its being processed as
> >part of the "ice witch" comp group.
> >
> >I have looked at the "comp" option attribute and have had no
success
> >getting it to work. I have even tried making child units instead
of
> >items to no success. I am sure I am missing something so please
> >enlighten me.
> >
> >Thanks for the help.
> >
> >Woody
>
>
> -------------------------------------------------------------------
--------
> Rob Bowes (rob@w...) (650) 726-9689
> Lone Wolf Development
www.wolflair.com


------------------------ Yahoo! Groups Sponsor ---------------------~-->
FREE COLLEGE MONEY
CLICK HERE to search
600,000 scholarships!
http://us.click.yahoo.com/47cccB/4m7...SFAA/IMSolB/TM
---------------------------------------------------------------------~->