I concur with msyblade. But, I just want to mention that supporters on the open-ended over-world thread actually think this would be a HUGE payoff. Here are some comments from some of the supporters:
Msyblade (Creator of Hotel Hades)
Really think this is the beginning of the "Granddaddy of all mods". If executed flawlessly, it could change the entire genre of dungeon crawlers, and heck yeah I wanna be part of that!
Neikun (creator of Neikun's Workshop)
I am for this idea. I just hope I have time to contribute.
akroma222 (creator of Labyrinth of Lies & (24) re-textured/re-coloured MONSTERS + new item drops)
I really like the sound of this
Linking finished dungeons together in a packaged mod has real potential
Mahric (creator of Wine Merchants Basement - so far voted #1 for Dec. 2012)
I like this idea very very much... Please come with creative solutions, since I'd love to see this happen anyway!
Asteroth (Creator of "Corrupted" Wallset & The Rise of Simon)
Yes, I believe some of us are actually going to try to do this. Call it madness, but some times you just gotta try.
Jkos (Creator of the open community project eob1-waterdeep
https://github.com/grimrock/eob1-waterdeep/)
I believe that I don't have the time to contribute to this project but I just wanted to share my thoughts and hopefully help you guys a bit.
McSkivv (veteran beta tester of the Dungeon Editor)
One way or another, this project will reach awesome fruition. It simply has too much potential to be left behind in the hypothetical dustbin of scrapped ideas.
If it isn’t too much work, I’m wondering if it is possible for the .dat files to reference a common library (a separate file or files) for things that need to be shared between .dat files like stats, inventory, spells, party progress, etc. I’m a software engineer and moving things off to libraries to be common for separate projects (or in this case dungeons) really isn’t that hard. So, instead of everything being in one file, the .dat file would reference the common library for things needing to be common between different .dat files. An example of this or an analogy is a web.config file for web applications referencing another file for connection strings, something like the following:
</configSections>
<connectionStrings configSource="ConnectionStrings.config" />
<appSettings>
This web.config file (think of it like the .dat file) is referencing a different file for ConnectionStrings (ConnectionStrings.config) that are needed for connecting to a database. This ConnectionStrings.config file is common between many web applications. I’m hoping the same type method of referencing a common file (for things like inventory and stats) could be done for dungeons. So, think of the dungeons as a web application that references the same file as other web applications (dungeons) for connection strings, but in this analogy the connection string file common between them would be a file for inventory, a file for party stats, spells, etc. This way only 1 file for inventory has to be updated for all dungeons instead of having to update every .dat file to include that Xaafe Chinese Automatic Star launcher that increases the attack power amount of Chinese Stars by 20 points! Now all dungeons have access to it