Good catch on that..
The problem is that the function is just way to long... We either need to put skill maxes in the database and load the table into memory, or divide this function up into a few seperate ones. If we did that though, we'd have to make modifications to CheckSkillIncrease to figure out which one to call..
__________________
Quitters never win, and winners never quit, but those who never win and never quit are idiots.
|