Ended up going back and redoing Nagash and the Mortis Engine
unless we go back to numbering the profile types, which i really don't like.
One could put a non-text character to force it to a specific point
But as it’s all one type of “X Wound table” it will at least still be together under X. Only oddities is that I did have several wound tables that were reused. (Zombie Dragons and Terrorgheists)
The perfect is the enemy of the good. Or Good enough.
I might change all of mine :)
Next thing we’ll have “Battalion Validation” To input ...
I'm not seeing it posted
And forgot to merge it...
"Chaos is already done ...." looks at the get ... finds nothing ... Sneaky-sneaky chaos ....
If you qualify for Allegiance X. And also the GA. You can choose to entirely use the GA Allegiance Traits. Does that mean that you're using Allegiance: <grand alliance> or that you're just using the traits? (See: Allegiance: Tomb Kings ... and Battleline for Tomb Queen ... No Allegiance Traits for TK)
Almost makes one want to set up an 'Allegiance: X (GA:<grand alliance>' allegiance
Lemme know when you're going to do the merge, so I can coordinate dropping the Death GA abilities into the gst.
@tekton I know the feeling. Managing Catalogues that have multiple Allegiances (other than just the GA and the default) is nearly headache inducing. I’m a hairbreadth away from just splitting them out (Soulblight, Nighthaunt ... I’m looking at you .... :angry: ) to make catalogue management easier with the Allies forces... hmm ... perhaps there is an easier method
It wouldn’t hide them, just make a list validity warning. :thought_balloon:
Not optimal. :/
If instead of hiding or showing, what if one did modifiers on the Categories?
For example: Nighthaunt
Set a max in roster of -1 by default.
If allegiance 'Derathmages' set Max in Roster to 0
Deathmages
If the units are categorized properly, it should flag that the restriction isn't being met ...