set hidden to false IF at least one instance in FORCE and all child selections of <regiment unique ID from regiment selection>
you may have to copy/paste the unique ID
then deselect the conditional for it to stick
its a quirk of the data editor where you can specify nearly any unique ID for force conditionals and it'll be valid, but the editor sometimes clears them out when you reselect the conditional (no idea why)
@WindstormSCR I totally understand where you're coming from. I understand and respect your point of view. Please don't misunderstand me -- you have a valid point! -- but I think we're going a bit too far. Why not just hide crappy units? I mean, might as well hide Conscripts and Commissars, because if you're trying to build an optimized list, you're definitely not taking those units <-- that's hyperbole, please take it as such
I'm saying people are treating regiment as docrine selection based on the function of every other catalog in our set, so why bother making it the exception just to satisfy a RAW claim about as anal as BCB's?
I can see setting things as Hidden and setting Hidden to False if correct regiment is selected
But for the Tempestus I'd have to set Hidden as True if Regiment Tempestus is selected....right?
And that's for the vast majority of units in the Codex. :)
I'm not opposed to doing it, I'm really not. I can see the benefits of doing it that way. I've just been made a little gun shy about overstepping curses stupid Index unit entries, again, ad infinitum, ad nauseum
well, I was getting a decent hourly rate for the effort :P
final total for just the build with exterior plates off and the magnet work was 96 hours
that's cleaning, fitting, magnetizing, filling gaps, cleaning up spare adhesive and filler, and sealing all contact points for the exterior plates with some latex-based sealant that could be rubbed/pulled off after painting