best practice making story changes to official products + benifitting from updates?

[Aridhro]

I constantly change the story files of my DotMM product, because I translate them to my native language (dutch).
I also change tokens and modify encounters, quests, ...
But when Smiteworks releases an update, I need to "revert changes", what would results in massive loss of my preperations.
My solution: copy the changed story/encounters/... and put them in a new folder.
Has someone come up with a better solution?
Can I export my changes en import them after I updated and reverted the module?

[LordEntrails]

Use a development campaign. Though not directly addressed in the link on my signature you'll get some ideas there. Create a development campaign, load your dungeons of the Mad Mage into it, copy the story entries and all the other entries that you were going to change, then export that as a new module and load that and depending upon what how much you changed the original module in your play Campaign. Then when the product updates you don't have any changes that you have to revert

[Zacchaeus]

Any changes made to DotMM or indeed any product are very likely to be minor ones and a list of what has changed is noted on the weekly Tuesday updates if there are any. It is therefore very unlikely that you would ever need to revert changes to the entire module. If you look at the changes made you can find the bits in the module that have changed and if you happen to have edited that you can right click and revert the change to only that thing.

[Aridhro]

Ok, I had it wrong and thought the updates only apply when revert changes. Is this correct?: Unchanged story entries are always updated, even if not reverting any changes. The button only exists for changed stories, encounters, ...

[Trenloe]

Ok, I had it wrong and thought the updates only apply when revert changes. Is this correct?: Unchanged story entries are always updated, even if not reverting any changes. The button only exists for changed stories, encounters, ...

Unchanged entries are not stored in the campaign data (moduledb directory) they are read straight from the module. So if the module is updated, then unchanged data is essentially updated too.

[Aridhro]

Thank you all for your support.