STR Minimum Suggestion

[rjcurrie]

Perhaps you should look at making choosing the actual STR minimum a value selector box from which you select a STR minimum and the appropriate limitation value is assigned. There is really no reason to choose a range -- weapons always have a specific STR minimum, not a range. This would eliminate the clunky "edit the descriptor to an integer" required to have STR minimum applied.

Actually, a similar argument can be made for selecting the number of charges.

Rod

[Simon]

Doesn't work if we want to keep things compatible with v1 (so that v1 characters can be loaded in with a minimum of changes by the user).

[rjcurrie]

I guess you're right. I just wonder how much the backwards compatibility is worth compared to having the limitation work the way most people would like to see it without an awkward workaround.

Personally, I would rather see v2 load the v1 character and set the STR Min at the bottom (or top) of the range by default and issue an appropriate warning when loading the character. And if the v1 character had the descriptor edited to an integer, it could use that directly.

Rod

[Simon]

I'm not interested in changing things in this case. The Limitation works fine the way it is and is a closer mirror to the definition in FREd (it is also more readily customizable by users who want to adapt it for use in their own custom templates).

I don't think that having the user replace the text "18 or greater" with the actual value for the STR Minimum is terribly cumbersome...nor do I think it is inobvious.

And, as a worst case scenario, if they don't replace the text, they simply don't have the damage with STR displayed on the HKA. It's really not that big of a deal.