Wendersnaven.com (a resource for nwn2 builders)

Note: There's a version control option under the Options menu, but at this time I don't know how one would hook into it. This is a poor man's solution that is easy to use.

I like to save multiple version of my modules just in case something happens. It's also nice to be able to test out something crazy, and roll it back to a previous version if you have to.

A simple way to do this with modules in a campaign is choose the "Save As" option, but I'm always afraid I'm going to continue working on a saved version instead of the one in the campaign. Nothing is worse than testing your module than suddenly realizing you've just wasted 20 minutes in the wrong version. A better way I've found is to simply copy the module and change the name. This allows your named (without version numbers) module to be the latest and greatest that shows up in your campaign.

As an example, I use a system where the first number is the release status, and the second number is the version. The release status is "0" for development and "1" for released. If I need to make large changes, I increment it from there, so if I were to totally redo something I'd change it to a "2." So my first module is the name of the module + "_0_001" and every time I increment it I increase that last number by 1. The first released version is "_1_001." As I fix bugs and update for patches, I continue to increment the last number.

Usually, for me a version is a day's of work or a major change that I don't want to screw up. As I progress with more and more versions, I usually burn them off to a disk... or just delete them. ;)

Use whatever system you want, but some sort of version control is a great idea. So is backing up your files.