[Irreverent]

Considering my databases is one of the most custom out there, I have learned to live with the single-file that CD uses.

What I have done is keep two different files, "Checklists", that I use. One is for code, one is for perl.

I just whipe the tables / file folders, load the quests or tables, then perform the checklist.

so in my database checklist, I have several hundreds of rows of SQL that will modify WHATEVER is in the new database back to where I need it.

For my custom npcs/items I have a different schema, to which in my checklist it has SQL to load those rows into the new database and then alter as nessecary.

That way, its VERY easy for me to keep in sync with ANY reload. I just load the script, hit run...and minutes later I'm running with the cool new db or quests version.

I would reccomend you do the same, because he's busy enough keeping his server running for his rules. If you want to alter it, its really up to oneself to do it. I'd rather not slow down CD so his database gets updated faster...and I can quickly keep in sync.

Plus, if I do something that is EQLive...(like the 85 new fableds I hacked), share it with CD and he'll load it into his database.