Digest Number 907

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get A Free Psychic Reading! Your Online Answer To Life's Important Questions.
http://us.click.yahoo.com/Lj3uPC/Me7...SFAA/IMSolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, email

armybuilder-unsubscribe@yahoogroups.com
------------------------------------------------------------------------

There are 2 messages in this issue.

Topics in this digest:

1. Tetiing for parent troops
From: Versif <petark@ntlworld.com>
2. What constitutes a 'hardware change'?
From: "Hailstop" <hailstop@shaw.ca>


__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 1
Date: Fri, 30 May 2003 15:34:31 +0100
From: Versif <petark@ntlworld.com>
Subject: Tetiing for parent troops

I've been messing around with the daemon hunters file trying to sort out
some validation issues when they are taken as allies. The DH units can't
count towards the compulsory requirements of the parent race. I've
sorted this for HQ, elites and fast (heavy can't be taken so no problem)
but troops is proving more problematic since up to 2 DH troop choices
can be taken.

My inelegant solution for the HQ etc. was:

ulmt:comp=HQ-min@unit=2-msg=omchq-mode=default-istype=omHQ

Essentially if a DH HQ (type omHQ) is detected AB flags up you must take
a parent HQ (message omchq) in this particular mode (primary/default).

So even though the DH HQ satisfies the HQ requirement of a minimum of 1
this test spots whether or not 2 HQ's are taken.

A further test

ulmt:type=omHQ-max@unit=1-msg=Maxhq

makes sure you can't simply take 2 DH HQs since you can only take 1 as
an ally. A tlmt test could be used instead but the effect is much the
same.

Nothing much I can do about validating you don't take 2 allied HQs, one
from DH and 1 from another ally but there has to be a limit somewhere

Some files insist on a parent commander and this also helps.

Problem is that with the ability to take up to 2 DH troops (type
omtroop) the above test simply doesn't work. A partial solution exists
in:

ulmt:comp=Trp-min@unit=3-msg=omctrp-mode=default-istype=omtroop

Here the required units as been upped to 3 since at least 2 parent units
must be taken if a GH troop type is taken.

Works fine for

2 parent troops no DH
3 parent troops with or without DH
2 parent troops and 1+ DH
1 parent troop and 1 DH - validation message

but fails
1 parent troop and 2 DH - should give validation message but doesn't
since the condition Trp-min@uniit=3 has been satisfied.

A further test limits the number of DH troop units to 2.

Anyone know how I can validate the troop types without altering any
existing files and only the DH file that I'm messing with? I did think
of using the augment to add in a generic troop type for the allies but
that would be time consuming and hardly seems worth it.

If it isn't possible I'll leave it to the AB user to sort since they
should of course have their DH codex and be aware of the requirement

Cheers
--
Grotfang, not so humble warlord


__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 2
Date: Sat, 31 May 2003 02:08:54 -0000
From: "Hailstop" <hailstop@shaw.ca>
Subject: What constitutes a 'hardware change'?

My copy of Army Builder seems to have reverted to the unregistered
version. I haven't done anything to my system except for removing a
CD-ROM drive. Is that enough to screw up the system code?





__________________________________________________ ______________________
__________________________________________________ ______________________



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/