Please add ability to export Scenario data set changes and subsequently merge them back in.

[DarkHorse2]

Currently, it is impossible to independently save or manage changes to any scenario data set.

Any changes made, are easily over-writen on installation of latest patch. Otherwise, you have to go through a painful process of exporting the WiTE2 data set to a collection of .csv files, manually make whatever changes to the .csv files and then import those back in. Currently, there is no merging of any change or delta and it is a very tedious, error-prone process.

This could be addressed by allowing a user the ability to export their local changes to a seperate data file, and the ability to subsequently merge them back into the WiTE2 data files at a later date.

This would be similar to how transactional logging works in most databases.

Another way to think of it is how you can save off changes to the Window's Registry as script (*.reg) files. Subsequently, you can merge them back in the case that a Window's update (or other installer) overwrote what you previously had.

Those Registry script files only contain local changes to a baseline Registry instance and not a snapshot of the entire Registry.

A similar mechanism could easily be implimented against WiTE2s scenario data using XML or JSON.

[Karri]

Just lock generic data.