I dont think that'd be a problem.. changing the table would be easy, even for an existing database. Just make the code robust enough to recognize a null value field so all npc's dont need to be assigned a zero if they dont have a proc attatched.
Optionally, you could modify spells used field, and identify the proc differently, with a <spellid>.<procnumber> id, that way it wouldnt require a database change, but the code where spells are read in would need to be modified minorly to ignore the procs.
Since usedspells is a varchar(70), you shouldnt have anyproblems. Still just be easier though to create the new column though.
|