31 Dec, 2006, Rojan QDel wrote in the 1st comment:
A while ago I started a personal project of mine partly out of curiousity and partly out of my desire to make easier-to-use and more efficient web scripts interfacing with the SWR codebase. The project is built off of SWR:FUSS and is essentially geared towards, in the end, removing the flatfile database system and replacing it with MySQL. I've gotten pretty far, replacing ships, boards, starsystems, planets, notes, and sysdata, and some other things I'm forgetting to list. I was wondering if anyone would be interested in helping me finish the project. I have my own server I host it on so of course you'd get your own shell account. It's open-source and public once I get my sourceforge project created but I would like some help in truly making a version of SWRFUSS fit to run without files at all. The rest of the methods need to be converted as well as refining the current methods of saving to MySQL and making them more efficient. Anyone who's interested please e-mail me at firstname.lastname@example.org or AIM at RojanQDel.
So your plans are to eventually be rid of area files, pfiles, class, race, and other files? Are you planning on simply substituting the database for the function of the flatfiles or are you planning to "query on demand" as the information is needed by the game?
And have you stopped to consider that relying completely on SQL to operate the game will cut out a large chunk of users? I had to address this very problem myself when doing SQL work for AFKMud 2.0 after finding out how many systems still don't have the required libraries and support files to do this. And that was just when I had converted helpfiles.
I'm not trying to discourage you from doing it, just making sure you're aware of what this decision means in the long term.
23 Jan, 2007, Rojan QDel wrote in the 11th comment:
Uploaded it here :) By the way, I'd still love some help in refining the code and working on future releases… And I use sourceforge because it has better version control and tools for tracking bugs, etc.
Oh, so if I edit any of my snippet submissions I can set them to enable bug tracking? That's cool, I just hadn't seen any bug trackings here on the live and hadn't paid attention on the dev to how to use them.
So not something that can just be turned on for all code submissions then? Maybe even convert exiting submission discussions that deal with bug fixes to bug tracker entries? Or would that take too much resources?