1. 7
  1.  

  2. 1

    Using a DB for storage sounds like a good plan.

    being prone to data corruption should the mud crash mid-save

    I bet C code that old probably does silly things when saving, like fopen the existing files and overwrite them in place, rather than doing atomic file replacement. (Save to a new temp file, then rename() it over the old file only after it’s fully written out. Then you don’t get half-written save files caused by the process segfaulting in the middle of saving.)