>>on the other end of the spectrum, the code for the
>>saving throw tables is unwieldly looking, and an
>>easier defined slimmed down formula would make things
>>more managable to look at, something i have looked
>>at to try and satisfy both sides is to make a very
>>basic addition formula, each class saving throws get
>>assigned two values
>>
>>CLASS_MAGIC_USER
>>
>>SAVING_PARA_INIT 20
>>SAVING_PARA_RATE 1.4
>>
>>SAVING_ROD_INIT 35
>>SAVING_ROD_RATE 1.54
>>
>>then to determine the value of the savig throw you
>>pass it through the formula similar to this simplistic
>>example
>>
>>save = 90 - INIT - ( level * RATE )
>>
>>this would save space in the code, and still be
>>easily managed to change saving throw results,
>>almost all the rates of change for the classes
>>lay within 1 to 2
This is basically what my suggestion was, except that
I used matricies to record the initial value and rate
of decrease instead of #defines.
I made a patch, but the listserv rejected it for
being > 200 lines :P
I suppose I could upload to the ftp site...
Angelfire for your free web-based e-mail. http://www.angelfire.com
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST