• 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

Unit count symbols

  • Thread starter Thread starter jizbrand at kc.rr.com
  • Start date Start date
J

jizbrand at kc.rr.com

Guest
I know that (#) gives me the model count, and (%) gives the item
count. Is there a symbol that gives me the unit count? I'm trying
to limit the number of units in the roster by the combination of a
fixed stat and a variable stat in the general's profile. Thanks.


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Win a Marvel vs. CapCom 2 Arcade System!
Click Here to Enter...
http://us.click.yahoo.com/uTyA4B/o58CAA/9ZuFAA/IMSolB/TM
---------------------------------------------------------------------~->
 
The information that is accessible to a unit must be local to that unit.
The model and item counts, as well as stats, are specific to the unit. The
unit count is a global value and completely separate. Therefore, there is
no way to reference the total unit count of the roster within a single unit.

The only way I can think of to solve this would be as follows. First, make
sure that the general is in a separate composition group or unit category
from other units (alternately, you could assign a type to all non-general
units). Define an assortment of options that are attached to the general,
where each option uses "usta" or "uexp" to limit itself to the stat
value(s) within the general. Each option uses "type" to assign a unique
type name to the general, based on the stat value(s). The net result is
that exactly one option will be valid for the general, resulting in exactly
one type name be assigned. You can then define a set of "ulmt" or "tlmt"
attributes, each imposing the appropriate unit limits for a different stat
value of the general. Each of these attributes would use the "-istype="
qualifier to limit the applicability of the stat to only be when the
appropriate type is assigned to the general. This way, the stat values of
the general will trigger a specific type to be assigned to the general, and
that type will dictate which of the "ulmt" attributes is applicable. The
"ulmt" attribute will then enforce the proper limitation on the roster.

Hope this helps,
Rob


At 12:42 PM 9/4/2001 +0000, you wrote:
>I know that (#) gives me the model count, and (%) gives the item
>count. Is there a symbol that gives me the unit count? I'm trying
>to limit the number of units in the roster by the combination of a
>fixed stat and a variable stat in the general's profile. Thanks.


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


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Win a Marvel vs. CapCom 2 Arcade System!
Click Here to Enter...
http://us.click.yahoo.com/uTyA4B/o58CAA/9ZuFAA/IMSolB/TM
---------------------------------------------------------------------~->
 
Perfect! So, for the variable stat, at each level I assign the
following: dtyp:Lead?, followed by unit:Lead123 (and so on, with the
numbers going up). Then in the generic race definition (which is
inherited by all races), I put ulmt:type=AllUnits-max@unit=9-
msg=TooBig-istype=Lead12 (and so on, with the numbers going up).

So, since my model already supports the necessary inheritance, it was
about 10 minutes worth of work to ensure that all races are handled
correctly. Thanks a lot (once again)!

--- In armybuilder@y..., Rob Bowes <rob@w...> wrote:
> The information that is accessible to a unit must be local to that
unit.
> The model and item counts, as well as stats, are specific to the
unit. The
> unit count is a global value and completely separate. Therefore,
there is
> no way to reference the total unit count of the roster within a
single unit.
>
> The only way I can think of to solve this would be as follows.
First, make
> sure that the general is in a separate composition group or unit
category
> from other units (alternately, you could assign a type to all non-
general
> units). Define an assortment of options that are attached to the
general,
> where each option uses "usta" or "uexp" to limit itself to the stat
> value(s) within the general. Each option uses "type" to assign a
unique
> type name to the general, based on the stat value(s). The net
result is
> that exactly one option will be valid for the general, resulting in
exactly
> one type name be assigned. You can then define a set of "ulmt"
or "tlmt"
> attributes, each imposing the appropriate unit limits for a
different stat
> value of the general. Each of these attributes would use the "-
istype="
> qualifier to limit the applicability of the stat to only be when
the
> appropriate type is assigned to the general. This way, the stat
values of
> the general will trigger a specific type to be assigned to the
general, and
> that type will dictate which of the "ulmt" attributes is
applicable. The
> "ulmt" attribute will then enforce the proper limitation on the
roster.
>
> Hope this helps,
> Rob
>
>
> At 12:42 PM 9/4/2001 +0000, you wrote:
> >I know that (#) gives me the model count, and (%) gives the item
> >count. Is there a symbol that gives me the unit count? I'm trying
> >to limit the number of units in the roster by the combination of a
> >fixed stat and a variable stat in the general's profile. Thanks.
>
>
> --------------------------------------------------------------------
-------
> Rob Bowes (rob@w...) (650) 726-9689
> Lone Wolf Development
www.wolflair.com


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Win a Marvel vs. CapCom 2 Arcade System!
Click Here to Enter...
http://us.click.yahoo.com/uTyA4B/o58CAA/9ZuFAA/IMSolB/TM
---------------------------------------------------------------------~->
 
Actually, if you use an explicit comparison, you don't even need the "dtyp"
attribute. If you specify on the option "uexp:fixed+var=7", then the option
will ONLY be valid when the two variables add up to exactly "7". You could
then have one with "=8", another with "=9", etc. If you do this, then there
is no need to "dtyp" any types, since those other types won't ever be
defined. :-)

I was hoping you were using inheritance. It definitely makes a HUGE
difference in how easy things usually work. :-) I'm glad that it was a
simple modification to get all this working. :->

Thanks, Rob


At 02:41 AM 9/5/2001 +0000, you wrote:
>Perfect! So, for the variable stat, at each level I assign the
>following: dtyp:Lead?, followed by unit:Lead123 (and so on, with the
>numbers going up). Then in the generic race definition (which is
>inherited by all races), I put ulmt:type=AllUnits-max@unit=9-
>msg=TooBig-istype=Lead12 (and so on, with the numbers going up).
>
>So, since my model already supports the necessary inheritance, it was
>about 10 minutes worth of work to ensure that all races are handled
>correctly. Thanks a lot (once again)!


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


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Win a Marvel vs. CapCom 2 Arcade System!
Click Here to Enter...
http://us.click.yahoo.com/uTyA4B/o58CAA/9ZuFAA/IMSolB/TM
---------------------------------------------------------------------~->
 
You must log in or register to reply here.
Back
Top