Army size

[Garfunkel]

Hi all,

I am curently writing AB files for confrontation, and I have a pb
with the army size :

For a defined size of 100pts, an army with no more than
100+0.5*(smallest fig cost)
satisfy the cost restriction.

How can I validate this kind of army ?

Garfunkel



To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com

[rob]

OK, I'm not sure I understand this, so please confirm whether the following
is correct (and clarify if I'm wrong). If the specified maximum army size
can be up to X, then the actual maximum army size allowed can exceed X by
up to half the cost of the lowest model in the army. Is that correct? This
sounds extremely bizarre to me, so I just want to make sure. :-)

If this is correct, then there is no way to 100% automatically handle this.
However, there is a 95% solution that requires a bit of help from the user.
The solution is to create a hidden stat that is assigned the point cost for
the model. You then create an option that allows the user to designate a
model as the lowest in the roster. This option is attached to each unit via
"cost" and assigns the unit the "Lowest" type. Then you use "tlmt" to make
sure that this option is assigned exactly once in the roster (one "tlmt" to
require 1 instance and another to limit it to one) AND you use "sgbl" to
ensure that the unit given the option is always the lowest in the roster.
The option must also assign a point cost of "-cost/2" and use the
"cost:single" attribute so that it reduces the cost by the excess allowed.

The net result of this is not ideal, but it definitely will work. The
problem is that the allowed overage is actually applied as a cost
adjustment for the unit. This means that the displayed cost of the roster
is X (the overage allowance) points LESS than its actual size. For example,
if a roster containing a (lowest cost) model of 10 points is created with a
total cost of 100 points exactly, the actual point cost displayed will be
95 points (the lowest cost unit will have the 5 points credited
automatically). You would then use a fixed maximum roster size of X points
(e.g. 100) and ANY overage is considered illegal, because you've already
been given credit back for the maximum allowed overage.

There is no way to dynamically change the point limits of a roster
dynamically based on the contents of the roster. I've never heard of a game
with this type of mechanic until now, so there's no provision for this
within AB (it's also a pretty weird rule IMHO). The only thing that you can
do via the contents of the roster is adjust the ACTUAL cost of things that
you are charged. That's how the above technique works and I hope it proves
useful to you. :-)

Thanks, Rob


At 10:16 AM 1/15/01 +0000, you wrote:
>Hi all,
>
>I am curently writing AB files for confrontation, and I have a pb
>with the army size :
>
>For a defined size of 100pts, an army with no more than
>100+0.5*(smallest fig cost)
>satisfy the cost restriction.
>
>How can I validate this kind of army ?
>
>Garfunkel


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


To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com

[Garfunkel]

--- Rob Bowes <rob@wolflair.com> a écrit*: > OK, I'm not sure I
understand this, so please confirm whether the
> following
> is correct (and clarify if I'm wrong). If the specified maximum army
> size
> can be up to X, then the actual maximum army size allowed can exceed
> X by
> up to half the cost of the lowest model in the army. Is that correct?
> This
> sounds extremely bizarre to me, so I just want to make sure. :-)
>
You are right

> If this is correct, then there is no way to 100% automatically handle

SNIPP

> The option must also assign a point cost of "-cost/2" and use the
> "cost:single" attribute so that it reduces the cost by the excess
> allowed.
It is a quite good solution

> The net result of this is not ideal, but it definitely will work. The
> problem is that the allowed overage is actually applied as a cost
> adjustment for the unit. This means that the displayed cost of the
> roster
> is X (the overage allowance) points LESS than its actual size. For
> example,
> if a roster containing a (lowest cost) model of 10 points is created
> with a
> total cost of 100 points exactly, the actual point cost displayed
> will be
> 95 points (the lowest cost unit will have the 5 points credited
> automatically). You would then use a fixed maximum roster size of X
> points
> (e.g. 100) and ANY overage is considered illegal, because you've
> already
> been given credit back for the maximum allowed overage.

In fact, the option will be applied near the end of the creation of the
army. Most of the time, it will left 12-15 points to use when it become
important to know exactely how many points does it left to complete the
rooster.

> There is no way to dynamically change the point limits of a roster
> dynamically based on the contents of the roster. I've never heard of
> a game
> with this type of mechanic until now, so there's no provision for
> this
> within AB (it's also a pretty weird rule IMHO).

Confrontation is a game which use 10-20 figs, and you can design armies
with 4 points minimum a soldier, to 24 point minimum, so it is very
difficult to fix an exact limit for all.

Thank you for your help

Garfunkel

PS : The complete datas for Confrontation will be availlable soon !!!

__________________________________________________ _________
Do You Yahoo!? -- Pour dialoguer en direct avec vos amis,
Yahoo! Messenger : http://fr.messenger.yahoo.com

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com