b175

Added an option that’s a bit hard to explain but useful to folks using Classic View or Trait Dialogs a lot to manage traits. You can now select a highlight color (or ‘any color’) in Options (Program Options > Display) that will allow traits with that highlight to remain in the character list regardless of the current category selected. This means that if you select ‘yellow’ and highlight a trait ‘yellow’ then that trait will always appear in the Character list, no matter what category is currently chosen in the category drop-down. This affects only these lists and has no impact on sheets or displays in other parts of GCA.

Added an option to display an LC column on the equipment library list.

If you use the option to format dollar costs or weights in character lists, you can now elect to apply those same formats to library lists.

The Display section on the Options dialog was getting a bit messy. I’ve split that into two: Windows & Boxes and Lists.

* Malf

Calculations have been updated to account for default Malf numbers based on techlvl() when an item should have a Malf but one is not provided, and for some special case values.

When GCA is calculating a trait, it’ll check to see if there is a malf() value for each mode of the item. (No modes, no malfs.)

If there is a malf(), great, it will calculate it.

If there is no malf(), it will then check for a cat() that includes “firearm” or “grenade” or a damtype() that includes “pi” or “inc”. If any of those are true, it will proceed to calculate the malf, using a default malf() based on techlvl().

You can use calcmalf(yes) (actually any value except ‘no’ or ‘false’) on the trait to force calculation of malf for all modes. Figured it should be there, but other options are probably better. If you use calcmalf(no) on the trait, it’s the same as setting malf(0) for every mode–all calced charmalf() values will be empty.

If the mode’s malf() is set to 0, this allows you to bypass all calcs, and the calculated charmalf() will be set to nothing.

If the mode’s malf() is set to 99, this allows you to force calculation of that mode’s malf–the 99 is not used as the base malf, that’ll be set by techlvl(). This is similar to using calcmalf(yes) on the trait itself, but applies just to this mode.

If calculating is a go, GCA calculates it as a simple number adjusted by all applied bonuses.

If not calculating, charmalf() is set to malf(), which may be empty.

I think that covers *most* situations. If something isn’t covered, manually setting the malf() to the appropriate value will cause calcs to happen.

* tagdefs.xml

Updated malf() text