• 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

Making rang: work with variable unit sizes

  • Thread starter Thread starter mobo at adelphia.net
  • Start date Start date
M

mobo at adelphia.net

Guest
Just noticed that my rang: weapons can always be increased to the max range set, even if the unit is not that large. I gave the units rmdr: Should that not control how many of the rang: options they can have?


Thanks,

Keith




[Non-text portions of this message have been removed]


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Free $5 Love Reading
Risk Free!
http://us.click.yahoo.com/3PCXaC/PfREAA/Ey.GAA/IMSolB/TM
---------------------------------------------------------------------~->
 
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> Just noticed that my rang: weapons can always be increased to the
max range set, even if the unit is not that large. I gave the units
rmdr: Should that not control how many of the rang: options they
can have?
>
rmdr: only controls the range of the actual option that is having
the rmdr assigned to... and only if you specify # as the remainder
count...

In the past, this sort of problem has been flagged with a validation
error - something like: "You have more X than you have members in
that unit!"...

You could do something really messy to force the rule...
Use a high priority option to set a stat to the model count (as I
suggested before, stat:MC=(#) (after defining MC to be a hidden stat
in your def file), then have a number of options for
your "selectable count" weapons that equal the number of possible
models in the unit. Each of these options has attributes:
rang:0-x (where x is the model count)
usta:MC=x (where x is the same number as above)
That way the maximum value of the rang: option increases as you
increase the model count for the unit...

Example: If I had a unit size of 5-10 models, I would have 6 almost
identical options (same name, different id) all linked to the unit.
They would have the following attributes:
rang:0-5,usta:MC=5
rang:0-6,usta:MC=6
rang:0-7,usta:MC=7
rang:0-8,usta:MC=8
rang:0-9,usta:MC=9
rang:0-10,usta:MC=10


That way, your rmdr attribute should apply the remainder (up to the
model count presumably) as appropriate...

DISCLAIMER: I haven't tried any of this! :-)

Cheers,
Russell
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Free $5 Love Reading
Risk Free!
http://us.click.yahoo.com/3PCXaC/PfREAA/Ey.GAA/IMSolB/TM
---------------------------------------------------------------------~->
 
Thanks Russell. I may give that a shot. I thought that AB used to tell you
if you had more weapons then guys to carry them. Can it still do that and
how?


Thanks,

Keith


----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 7:41 PM
Subject: [AB] Re: Making rang: work with variable unit sizes


> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > Just noticed that my rang: weapons can always be increased to the
> max range set, even if the unit is not that large. I gave the units
> rmdr: Should that not control how many of the rang: options they
> can have?
> >
> rmdr: only controls the range of the actual option that is having
> the rmdr assigned to... and only if you specify # as the remainder
> count...
>
> In the past, this sort of problem has been flagged with a validation
> error - something like: "You have more X than you have members in
> that unit!"...
>
> You could do something really messy to force the rule...
> Use a high priority option to set a stat to the model count (as I
> suggested before, stat:MC=(#) (after defining MC to be a hidden stat
> in your def file), then have a number of options for
> your "selectable count" weapons that equal the number of possible
> models in the unit. Each of these options has attributes:
> rang:0-x (where x is the model count)
> usta:MC=x (where x is the same number as above)
> That way the maximum value of the rang: option increases as you
> increase the model count for the unit...
>
> Example: If I had a unit size of 5-10 models, I would have 6 almost
> identical options (same name, different id) all linked to the unit.
> They would have the following attributes:
> rang:0-5,usta:MC=5
> rang:0-6,usta:MC=6
> rang:0-7,usta:MC=7
> rang:0-8,usta:MC=8
> rang:0-9,usta:MC=9
> rang:0-10,usta:MC=10
>
>
> That way, your rmdr attribute should apply the remainder (up to the
> model count presumably) as appropriate...
>
> DISCLAIMER: I haven't tried any of this! :-)
>
> Cheers,
> Russell
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Free $5 Love Reading
Risk Free!
http://us.click.yahoo.com/3PCXaC/PfREAA/Ey.GAA/IMSolB/TM
---------------------------------------------------------------------~->
 
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> Thanks Russell. I may give that a shot. I thought that AB used
> to tell you if you had more weapons then guys to carry them. Can
> it still do that and how?
>
You'll need to specify a validation message. You can check out the
ocat: external unit attribute. The help text is quite long, and
there's some stuff near the bottom about using it with rang: options.

Cheers,
Russell.
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Free $5 Love Reading
Risk Free!
http://us.click.yahoo.com/3PCXaC/PfREAA/Ey.GAA/IMSolB/TM
---------------------------------------------------------------------~->
 
Will do thanks.


Thanks,

Keith


----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 9:42 PM
Subject: [AB] Re: Making rang: work with variable unit sizes


> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > Thanks Russell. I may give that a shot. I thought that AB used
> > to tell you if you had more weapons then guys to carry them. Can
> > it still do that and how?
> >
> You'll need to specify a validation message. You can check out the
> ocat: external unit attribute. The help text is quite long, and
> there's some stuff near the bottom about using it with rang: options.
>
> Cheers,
> Russell.
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Free $5 Love Reading
Risk Free!
http://us.click.yahoo.com/3PCXaC/PfREAA/Ey.GAA/IMSolB/TM
---------------------------------------------------------------------~->
 
You must log in or register to reply here.
Back
Top