Ratios in AB3, any examples?

[shaggai]

I'm trying to set up an option which will only show (or be able to be selected) once for every 5 members of a unit. (Basically Fanatics in a Zealot mob for the 40K Witch Hunters).

I've gone back in the discussions and seen "trat", but I'd like to know if anyone has it in any type of AB3 file so I can see an example of how everything needs to be set up for it to work right.

 

[Warmonger]

I would like to see something for hidden/visible/ratio controlled options like this too. Best I've been able to come up with is a validation rule that will tell you if it's legal after it's all done.

 

[harkan]

if you create a stat for the parent unit and have a postscript that calculates it based upon the ratio required rounded down, i.e. fanatic. Kepp the name short enough so you can refer to it in a runtime call.

Create an exclusion based on 0 to @fanatic. Create the option based on a range of 0 to max number of fanatics within the mob, i.e. if max size is 20 then max range would be 4. Apply the exclusion to the range based option and add a live statement so that if val:runtime.fanatic? > 0 it is live.

Ideally what should then happen is that once the first 5 zealots are add the option then displays with a range limited to 1 due to the exclusion referencing the stat, as more models are added then the exclusion increases.

Chosen use the principle for 1 weapon swap for every 3 models and seems to work OK but would be nice to have an easier solution?

 

[shaggai]

Thanks harkan,

Along with perusing the Chaos file, I managed to get what I wanted to going. Just required a little extra on my part as I have the Fanatic option open up a new link, rather than just add to the basic squad (since the Fanatics have an extra option solely their own).

 

[rob]

At 04:23 PM 5/31/2005 -0400, you wrote:
>Chosen use the principle for 1 weapon swap for every 3 models and seems to
>work OK but would be nice to have an easier solution?

The big limitation within AB2 was that the engine worked beautifully for
80+% of the situations, but authors hit a wall when wanting to do something
a bit more complex that wasn't already anticipated. With AB3, the pendulum
has swung the other direction a bit. With all the flexibility comes the
need to actually do a bit more work sometimes, as compared to AB2.
Ratio-based options are a prime example.

If there are things like this that you run into multiple times, tell us
about them. When we start planning for V3.1, we'll see if there are ways we
can streamline things that occur regularly to simplify things in the
future. Unfortunately, there was no way for us to know what all of those
situations are in advance.

-Rob

---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (408) 927-9880
Lone Wolf Development www.wolflair.com