Guest
Posts: n/a
|
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 ------------------------ 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 Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ |
#1 |
Senior Member
Lone Wolf Staff
Join Date: Dec 2008
Posts: 4,690
|
At 03:34 PM 5/30/2003 +0100, you wrote:
>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. I believe you can do this fairly easily using the 'allw' attribute on an option. On every Daemonhunters HQ unit, give them an option with the following attributes: lglx:!race=dh allw:HQ-min+1u (where 'dh' should be whatever the actual daemonhunters race abbreviation is.) That means that when this unit is included, you need 1 extra 'minimum' HQ unit. You should be able to do the same with troops, elites, fast attack, etc. So if you have 2 daemonhunters units included, the minimum allowance for troops would be raised to 4, while the maximum would remain at 6. Hope this helps. -- Colen McAlister (colen@wolflair.com) Lone Wolf Development www.wolflair.com To unsubscribe from this group, email armybuilder-unsubscribe@yahoogroups.com Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ |
#2 |
Guest
Posts: n/a
|
Colen McAlister writes
>I believe you can do this fairly easily using the 'allw' attribute on >an >option. > >On every Daemonhunters HQ unit, give them an option with the following >attributes: > >lglx:!race=dh >allw:HQ-min+1u > >(where 'dh' should be whatever the actual daemonhunters race >abbreviation is.) > >That means that when this unit is included, you need 1 extra 'minimum' >HQ >unit. You should be able to do the same with troops, elites, fast >attack, >etc. So if you have 2 daemonhunters units included, the minimum >allowance >for troops would be raised to 4, while the maximum would remain at 6. Thanks, I came up with a much more cumbersome solution that worked but I'll give this a try since it represents a much neater solution. Cheers -- Versif, Nightgoblin backstabber and all round coward, but nice with it. Kirkby-in-Ashfield, Nottinghamshire - whaddya mean, Robin Hood wasn't a goblin? ------------------------ 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 Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ |
#3 |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Cadian Shock Troops Inquiry | Sycoa | Warhammer 40,000 | 7 | November 17th, 2007 01:32 PM |
Child / Parent options (help!!) | gareth_perkins | Army Builder | 1 | August 7th, 2006 02:08 PM |
Troops upgrades in Warbands, Hochland Rifles, WH in a Flash | BlackCavalier | Warhammer Fantasy 8th Ed. | 5 | March 5th, 2006 09:56 PM |
Items cost being rolled up into parent | woodywalton at hotmail.co | Army Builder | 2 | September 11th, 2001 09:10 PM |
tunnel troops gutter runners data wrong | kappa1 at home.com | Army Builder | 2 | December 4th, 1999 01:40 AM |