|
We're utilizing a Database backend for the store of just about all our mud information (excepting of some code constants that really shouldn't be in it).
Essentially we did it for organization purposes, decreased coding time of save/loads, and for the dynamic nature it lends to our system. Restricted remote access to the system allows for the creation of non-in-game OLC creation building to be done through a separate program, which can access the database for things such as lists of mob and item, templates room types ect. It can also be used to access information about the game quickly and easily for posting on a website, and could be updated instantly upon a chance in the information (pending a refresh of the window of course) (game statistics, help files, ect).
For a large server application which we thought should be as dynamic as possible, it seemed to be the best option. And we're not without help when it comes to needing to do things that a file system could do (distribute the information in the database via file, or back up the system). All that is, obviously, very easily done.
|