I don't know what method is actually being used in the 40K files, but I
believe there ARE good middle ground solutions that I had suggested many
months ago on our Beta team forum. There may be a reason why these
approaches won't work, but I don't recall ever hearing one mentioned, so I
think they will work smoothly.
The first method is a very lightweight solution, but I think it will work
for the Witch Hunters. If not, consider the next one. This method requires
that you setup a separate set of race records for the Witch Hunters. Each
of these might be designated ids such as "wh_xxx", where the "xxx"
indicates the ally. Then you can have this race record explicitly define
the additional "race.xxx" tag that the allied race normally auto-defines.
By doing this, the selection of the allied race will enable all units for
that allied race at the race level. Then the current method with the
extension files for the various units will allow you to customize which
units are limited via their individial member expressions. The net result
of this technique is that you turn on the allied races very simply via the
ALLIES mechanism, and the current use of extension files keep everything
cleanly decoupled from a maintenance standpoint.
The second method requires the use of a simple, generalized change to all
blocks of units. This method was actually posted a few months back on this
group, so I've included the URL of the thread below:
http://support.wolflair.com/index.ph...ewtopic&t=4152
This thread will be found in the Army Builder support group. It is dated
January 31, 2005.
Hope this helps,
Rob
At 04:47 AM 5/29/2005 -0400, you wrote:
>I'm working on the Witch Hunter files for the AB3_40k files and wanted to
>see if there was a middle ground for the usage of allies.
>
>The nice way would be to have the allies selected using the Ally button,
>and the selecting allies from that screen. However in the case of the
>witch hunters, only certain units can be taken. In order to accomplish
>this properly, the ally file would have to have ruleset allowances or
>exclusions in their member tab. This means alot of extra modification to
>that other list, not to mention another thing to keep track of for all the
>maintainers.
>
>The current way that it's handled at the moment is through the use of an
>extension file. This does handle the situation, but has the ally units
>showing in the general list instead of something selectable. So while it
>does work, it doesn't "look" good since if you do not want to use allies,
>they're there anyway for you to look at, cluttering up the view.
>
>Is there someway that the allies can be selectable through the button like
>they are supposed to, but be handled though the extension file?
>
>Thanks for any info.
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (408) 927-9880
Lone Wolf Development
www.wolflair.com