Alternately, since the overall trend for all five
cleric saving throws is 3 points every two levels,
we could use an array of base values:
int save_cleric[] = { 60, 70, 65, 80, 75 }
Then in mag_savingthrow, we have something like:
int mag_savingthrow(int type, struct char_data *ch) {
switch ((int)GET_CLASS(ch)) {
case CLERIC:
return (save_cleric[type] - (GET_LEVEL(ch) * 1.5));
case MAGIC_USER:
etc.
}
This preserves the different starting points of each
class, allowing them to have certain strengths and
weakness, but maintains the simplicity of having
just one equation.
---
eglamkowski@angelfire.com
http://www.angelfire.com/nj/eglamkowski/null.html <- Null webring
http://www.angelfire.com/nj/eglamkowski/eia.html <- EiA webring
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