I don't think he's talking about reloading it every time someone tries to access a spell; it will still be loaded only once.
I'd say it's pretty likely they store it in a file similar to what they put on the patcher, perhaps bundled into a data archive.
Here's my thoughts on this:
The reasons for adding it to the database aren't really all that compelling if you ask me. Assuming this went into effect right now.
-You have slightly increased load on SQL server.
-You have slightly increased load times for spells.
-You have additional complexity when it comes to actually getting the spells to the client. (Now instead of modifying the spells directly you have to edit the database and then convert it.)
-You have increased database size.
-You don't really eliminate the need for a spell editor, you just lessen it if you're trying to change something simple. It will still be quite a hassle to heavily modify spells, especially many spells without one.
-You force people who wrote their spell editors to have to rewrite them for both systems, or you can continue to use them and then convert it over to the database but then what's the point.
-You've eliminated the need for a tool to need to write a spell file parser to get spells(which is incredibly simple btw).
-In my opinion you made it harder on new users who now have to try to figure out 'hey there's two systems for spells, wait do I need them both? I can't find the db table I need anywhere help!!'.
Lots of cons, a few pros. I personally just don't think it's a worthwhile idea.
|