Senior Member
Volunteer Data File Author
Join Date: May 2005
Location: Matawan, NJ, USA
Posts: 158
|
Currently trying to figure out something on using a stat for exclusion purposes accross a squad which consists of multiple units.
For example, we have a squad which can have up to 1 special weapon for every ten models. A stat is used to keep track of this. The problem occurs when a "sergeant" type model is added. This sergeant can have the same special weapon, but obviously if he chooses it, it cannot be chosen by the squad. However, by using the stat as an exclusion it only seems to care about the stat in regards to the exclusion limit. Trying to modify the stat, such as by reducing the stat by one if the sergeant takes it can lead to the result where an option error occurs (it reduces the stat by one, and if only one special weapon can be chosen it turns to zero and thus cannot be chosen). I'm sure that a rule would work, but the exclusion idea seems a little more elegant - provided that the stat could be used for the whole squad, instead of a unit by unit basis. |
#1 |
Senior Member
Lone Wolf Staff
Join Date: Dec 2008
Posts: 4,690
|
When you say "squad", do you mean an AB squad? As in, a collection of several top-level units? Or do you just mean a 40k squad, which is 1 unit, that may have child units?
If the latter, you could use an exclusion based on a stat value. Have the parent unit set the stat value to whatever the right number is (1 per 10 models), then have the sergeant subtract 1 from the parent unit's stat value. If the former, it's slightly more complicated. In this case, I'd recommend using an exclusion anyway, and then adding a squad validation rule - I think the rule should be able to use "usage[unit:exclid]" to get the total number of exclusions each unit has, which you can then compare to the model count to see if it's valid. Someone could then pick too many weapons, but they'd see the validation error when they did so. |
#2 |
|
|