I'm trying to put together the True20 System, but the Scores won't go into negatives. True20 allows -5 to +5 for a typical starting character. I've tried the "Allow any ability range" House rule and that doesn't work. Would it be possible to add a method to allow the score to be any number?
I'm going to respectfully disagree Andrew Wilson. The support is lacking for that sort of interface and changes, seems like a lot more effort to support a new method than to alter an existing method. Editable Score is where all the values are derived from, it is also what is controlled by DEFINESTAT. I can't limit PC Classes to a BONUS of +5, I can limit their score to a +5. Support for negative values seems to be an easier solution than figuring out how to backwards resolve a Mod to a Score. It also means less newtag requests to get the exact same support that Score already enjoys.
Let us break down the issue: True20 removed the +1/-1 Values for every score increase by 2. Left us with just the bonus. Simple solution is Score now equals bonus, as you never need the full range of the obsolete score. My new range is -5 to +10 as opposed to 0 to 30.
UI Solution = Support Negative Editable Score Values. One Change.
Your suggestion: UI + Code Solution = Score Editable remove + Add ability to edit Mod value directly + Add support to control MOD just like score. Three Changes at a minimum. Looks like we just went through a lot more effort to arrive at the same result. MOD is now treated as score. Someone coming along later will go "Why didn't they just alter the score to go to negative?"
Score has the inbuilt support syntax the system required, doesn't seem like a far-fetched request to support another variant d20 system to change how the score works in the UI by allowing the negative values. My counter question then becomes why? Why is it detrimental to alter UI Editable score to be negative? What underlying issue is going to come to light that requires a different implementation to my request?
Would this discussion be better suited for the PCGen_Experimental list?
I'm not the code team, but this is a bug to me. I placed STATRANGE:-100|100 in the test gamemode and discovered no value below 0 is allowed. Tested attempting -50.
Per Tom - this is a bug. Moved accordingly.
The UI now supports negative ability scores (stats) again. These are controlled by the STATRANGE token (for each stat).
I've also revamped the purchase mode dialog to be a bit more usable, display its buttons correctly and respect the STARTSTATMIN and STARTSTATMAX values to set the boundaries of the allowed purchase mode config.