[Mathias]

I'd recommend adding a list expression to the Hindrances table, that tests for a Hide tag. For example:

 
<list><![CDATA[
  !Hide.Hindrance
  ]]></list>

That way, in DL: Noir, every character can have the Poverty hindrance bootstrapped, and those characters who take something else that cancels that automatic hindrance will no longer see it (since the other pick assigned the tag to Poverty that hides it). Here's the thread this is from: http://forums.wolflair.com/showthread.php?t=45651

Oh, a reminder - when adding list expressions that hide things, it's best to add this setting to the table:

alwaysupdate="yes"

Otherwise, even after the tag had been assigned, the pick wouldn't be hidden until the user switched tabs and switched back, or added/deleted something else from that table (Hero Lab tries to save computational cycles by minimizing how often it tests list expressions on tables, but in this case, that's not the behavior you want).

This'll need to be applied to all the things that display hindrances - the Edges tab, the summary panels, the dashboard, the tactical console, the printout, and the statblock (and anywhere else that they're displayed that I forgot about).

Oh, and you may want to make this more generic - Hide.Edge, perhaps, and then have the same list expression on the edges, hindrances, and rewards tables, so that the same behavior is available in all those cases. (Hide.Ability already exists, and means something slightly different - otherwise, I'd have recommended that as the tag to use). If there's a term in Savage Worlds that covers Edges, Hindrances, Rewards, and things that are similar to them, use that term instead.