As long as the database tracks things with unique identifiers, everything works pretty well. However, some of the new export tables don't have unique numbers in them and thus pose a potential conflict when putting them into someone else's database. DB Sets will warn you when you try to export such data. (The ideal fix for this would be to add unique ids for everything to eTools, but failing that the best solution would be for a community-wide number management scheme.)EricNoah said:Speaking of building stuff, it looks like these items can be exported, but how safe/dangerous is it to import stuff that wasn't "intended" to be exported/imported?
A secondary issue is that normally custom data is identified in a "set" that the author can name, thus keeping custom changes separate from the core rules. But for things without set identifiers, it's up to the users to keep track of what's core material and what's been changed or imported from other places. This can make removal of unwanted material problematical, for instance.
I've tried to leave room for the discussion of issues like these in the help file under construction. If anyone would like to participate in that effort by contributing bits of text (or proofreading), please stop by the MSN forum and volunteer to work on something.