• 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 size restrictions

  • Thread starter Thread starter sday at dolphin-cs.co.uk
  • Start date Start date
S

sday at dolphin-cs.co.uk

Guest
Hi,

I am attempting to put together a parent/child unit relationship as follows:

Parent unit: normal size is 8:28
Child unit: optional and can contain 1 model for every 2 models of the parent.
For each model in the child unit, the maximum count of the parent unit should be reduced by 1 (so you never exceed a maximum of 28 models in total)

e.g. unit A has 19 models, child unit B has 9 models = 28 models total.
e.g. unit A has 23 models, child unit B has 5 models = 28 models total.

The parent and child units are currently linked via an option (unit:child@var)

I have got the ratio of 2 parent models must exist for 1 child model, but can't work out how to restrict the total size of the parent/child combination to be 28.

Any ideas ?

Cheers,
Simon Day


________________________________________________________________________
This message has been checked for all known viruses, by Star Internet,
delivered through the MessageLabs Virus Control Centre.
For further information visit:
http://www.star.net.uk/stats.asp

--------------------------------------------------------------------<e|-
Go to Maingate.com to improve the quality of military life.
http://click.egroups.com/1/7637/4/_/36190/_/966584355/
--------------------------------------------------------------------|e>-

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
You can't combine "ratp" and "coun", since that's a no-no. So, I would use
"coun" on the child unit to ensure that the parent/child total model count
is enforced. Then I would define a hidden stat. A hidden option attached to
the child unit would increment this stat in the parent based on the model
count (e.g. "prnt:stat+(#)"). Then I would define an "scmp" attribute for
the parent unit that compares the hidden stat to the model count of the
parent unit, reporting a validation error if the proper ratio isn't maintained.

Please note that this proposed solution requires that you use V2.0.

Hope this helps,
Rob


At 08:35 AM 8/18/00 +0100, you wrote:
>Hi,
>
>I am attempting to put together a parent/child unit relationship as follows:
>
>Parent unit: normal size is 8:28
>Child unit: optional and can contain 1 model for every 2 models of the parent.
>For each model in the child unit, the maximum count of the parent unit
>should be reduced by 1 (so you never exceed a maximum of 28 models in total)
>
>e.g. unit A has 19 models, child unit B has 9 models = 28 models total.
>e.g. unit A has 23 models, child unit B has 5 models = 28 models total.
>
>The parent and child units are currently linked via an option (unit:child@var)
>
>I have got the ratio of 2 parent models must exist for 1 child model, but
>can't work out how to restrict the total size of the parent/child
>combination to be 28.
>
>Any ideas ?
>
>Cheers,
>Simon Day


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

--------------------------------------------------------------------<e|-
Go to Maingate.com to improve the quality of military life.
http://click.egroups.com/1/7637/4/_/36190/_/966590321/
--------------------------------------------------------------------|e>-

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
Thanks Rob

I'll give that a try at lunchtime (using Version 2.0) and see how I get on.

Cheers,
Simon Day

> ----------
> From: Rob Bowes[SMTP:rob@wolflair.com]
> Reply To: armybuilder@egroups.com
> Sent: 18 August 2000 10:23
> To: armybuilder@egroups.com
> Subject: Re: [AB] Unit size restrictions
>
> You can't combine "ratp" and "coun", since that's a no-no. So, I would use
> "coun" on the child unit to ensure that the parent/child total model count
> is enforced. Then I would define a hidden stat. A hidden option attached to
> the child unit would increment this stat in the parent based on the model
> count (e.g. "prnt:stat+(#)"). Then I would define an "scmp" attribute for
> the parent unit that compares the hidden stat to the model count of the
> parent unit, reporting a validation error if the proper ratio isn't maintained.
>
> Please note that this proposed solution requires that you use V2.0.
>
> Hope this helps,
> Rob
>
>
> At 08:35 AM 8/18/00 +0100, you wrote:
> >Hi,
> >
> >I am attempting to put together a parent/child unit relationship as follows:
> >
> >Parent unit: normal size is 8:28
> >Child unit: optional and can contain 1 model for every 2 models of the parent.
> >For each model in the child unit, the maximum count of the parent unit
> >should be reduced by 1 (so you never exceed a maximum of 28 models in total)
> >
> >e.g. unit A has 19 models, child unit B has 9 models = 28 models total.
> >e.g. unit A has 23 models, child unit B has 5 models = 28 models total.
> >
> >The parent and child units are currently linked via an option (unit:child@var)
> >
> >I have got the ratio of 2 parent models must exist for 1 child model, but
> >can't work out how to restrict the total size of the parent/child
> >combination to be 28.
> >
> >Any ideas ?
> >
> >Cheers,
> >Simon Day
>
>
> ---------------------------------------------------------------------------
> Rob Bowes (rob@wolflair.com) (650) 726-9689
> Lone Wolf Development www.wolflair.com
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
>
> ________________________________________________________________________
> This message has been checked for all known viruses, by Star Internet,
> delivered through the MessageLabs Virus Control Centre.
> For further information visit:
> http://www.star.net.uk/stats.asp
>

________________________________________________________________________
This message has been checked for all known viruses, by Star Internet,
delivered through the MessageLabs Virus Control Centre.
For further information visit:
http://www.star.net.uk/stats.asp

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
One fine day in the middle of the night, Rob Bowes <rob@wolflair.com>
got up to write:

>You can't combine "ratp" and "coun", since that's a no-no.

You can, but you have to cheat. Take a look at the way Shuriken Cannon
Jetbikes work in the old 40K files.

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

--------------------------------------------------------------------<e|-
Go to Maingate.com for info that improves the quality of Army life.
http://click.egroups.com/1/7636/4/_/36190/_/966634214/
--------------------------------------------------------------------|e>-

To unsubscribe from this group, email

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