That is a good idea, realityincarnate, but you would still probably need an EVENT_CAST to use it unless we made another default.pl/player.pl type quest file named spells.pl or something to handle all of the custom spell stuff.
Using the database loading spells would make adding an extra field to the spells fairly simple. The scripts AndMetal wrote might need to be adjusted so they don't export that new field though, I don't really know about that.
I was thinking about adding a couple more fields to that table at some point anyway. I would love to have a qglobal name and value field in the spells file. Then, have those fields reference the qglobal table when you scribe spells. If a value is set in the spells_new table new qglobal fields, it would check to see if the player scribing their spells (with a spell scriber script) has the matching qglobals to scribe them. This way, you could easily block certain spells from being autoscribed unless people have earned them. The reason to also have a value field is so you could have it check if the value is >= the value in the qglobals table. So, you could have multiple tiers of spells without needing to have multiple different qglobal names for them. The main reason for that would be for organization purposes.
You could have classes of spells and assign values for each tier you want for that class. An example would be if you wanted shaman to be able to get their RK1 spells without a qglobal, but their RK2 woudl require them to have the "shaman_RK" qglobal of a value of 1 or higher. Then, if they wanted to get the RK3 spells, they would need a value of 2 or greater and so on.
I would really love to get something like that implemented at some point, but I just haven't had any time to do it for quite a while now :P
|