Yeah, the biggest hurdle would be the databases. Which is why I am wondering if a centralized database is the way to go. The Co-ordinator maintains a master database of information (monsters, quests, items, etc.) and when a Dev needs to change/add things, he/she does so through the co-ordinator. The Dev sends the required info to the coordinator, the co-ordinator enters the info into the master database then mails a new copy of the changed DB to each dev, thus ensuring each dev is using the latest information. It would be CRITICAL that the developer makes no changes to the databases. (Hence planning ahead in your design would be REALLY important) That way, everyone would be designing with the same databases, and that should (Help me out here CocoaSpud) ensure compatibility with the char files/save games.
The nice thing about this 'World' is that updates would be small. Just packing the changed files and unpacking them in the .dsn directory would be all that is required I think.
Hmmm...Me thinks I'm getting an itch.
Any more thoughts? Ideas? Hiccups?
One other idea I had too...It might be a good idea for a dev to make sure that the player can start from scratch again and be able to still play through everything from the beginning (again, mucho mucho planning). Although, as long as the storyline fits....
That's the other thing...Storyline...Would it be important?