Kamajii Posted April 21, 2010 Share Posted April 21, 2010 As I've started to branch out into more than one mod project, I've been curious. How do others manage more than one mod project at a time with your toolset? Do you just keep all your edits active in the same toolset in one lump sum? Do you keep separate database backups per each project, restoring the a database for each specific project? Maintaining a builder-to-builder export for each of the project resources? If you branch out into more than one modification, its easy for things to get chaotic especially when your own mods start conflicting. Link to comment Share on other sites More sharing options...
Kamajii Posted May 1, 2010 Author Share Posted May 1, 2010 So.. Nobody has more than one mod that they keep the source files backed up so that they can freely work on other mods? Just release and forget? Link to comment Share on other sites More sharing options...
hdhd Posted May 1, 2010 Share Posted May 1, 2010 Mostly, I do only changes to scripts therefore I can simply backup the nss file. For bigger projects I always make b2b packages and reset the database after making any core file changes. I only work on one project at a time so it is "release and forget" :biggrin: Of course if anyone finds a bug or has any good suggestions I'll load it again in the builder and make the changes. I never have more than one module in the toolset. I'm not sure if other modules (that shouldn't be loaded) are loaded even if I had disabled them in the add-in screen thus I always reset the database and open a batch script to delete all folders that had been created by the toolset. Now I can be sure that if a problem occurs that it can't be from my other test module or perhaps from the not-deleted toolsetexport folder. Link to comment Share on other sites More sharing options...
Recommended Posts