Plot Database: Various issues and feature requests when working with mod plot databases

[henbagle]

There are numerous weird issues about how mod plot databases work that should be refined to create a consistent experience when working with them. It is not clear how loading and saving works, and when changes get discarded, etc.

Here are several issues to be resolved that could refine this feature:

• Saving and loading only work on the active game. If LE1 database has changes, but you hit save while LE2 is selected, LE2 will save (perhaps saving an empty database) and the tool will mark itself as not needing to save. You can then close the tool and you will not be reminded that you have unsaved changes. When hitting save in the menu bar, all three games should save. Same thing with load.
• Changes are not discarded if you click past the save reminder when you close the tool. This is because the databases stay in memory to provide plot context to other tools. For example: You add a bunch of states to a mod, you close the tool without saving. Those states stay in memory in the toolset to provide context to sequence editor (eg). Upon restart of the toolset, those states are totally gone because you never saved them. This can be frustrating for users. When you close Plot Database without saving, it should ideally reset the database to the state on disk, reverting any changes you have made in the tool.
• Add the ability to save a specific mod by right-clicking on it in plot database. This allows you to save changes to one mod without saving everything. Perhaps add an option to load as well
• Right-click -> Add elements in Plot Database will often have greyed out options based on where in the hierarchy you are. These options should just not be visible instead of being greyed out, as (for example) you will never be able to add a new mod inside an existing mod.
  
• If you exit the toolset with unsaved changes open in the Plot Database, clicking "No" when it asks you if you really want to exit will still close the toolset.
• Basically no documentation on how the Excel import works. I have no idea what state my database needs to be in for import to work properly.
• Plot Database generates hundreds and hundreds of binding errors