Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[StrongAxe]

Has anyone worked up a method of version controlling their saves?  I was looking at doing this using svn on a shared machine, as a way of also sharing my saves between computers.

Psuedo Code:

Code: [Select]

cd ~/df/data/
If .svn does not exist Then
   svn checkout <REPO_URL> (force overwrite)
   svn add saves (ignore failure)
Else
   svn update
End If
../DwarfFort.exe
Subversion Commit

Does anyone see a problem with this, or a way it could be made better?  I'd have already implemented it if it weren't for the Windows 7 (x64) / Subversion bug.

[Ampersand]

Actually seems like a rather brilliant solution. Although, maybe a bit overdoing it. I assume you're passing up packing them in properly timestampped .rar or .zip files for conveniences sake. In which case my suggestion is to not script it out. Update and commit to your svn folder manually every time. You don't want to be in a position where the script doesn't properly execute due to some network problem only to find out later. It's not even hard to do with shell extensions.

Alternately, you can use Dropbox instead, at least until the bug is fixed.

[Urist McDepravity]

Go with mercurial or git, you will have whole repository locally, so will not have troubles with pulling/pushing to svn server all the time.
Also, this idea seems brilliant, i'll try it myself with git. Its easy to add watchdog for file edits, so it will auto-commit upon any new edit.
Only problem is proper commit names. Best solution would be to grab complete year-month-day info from the game, but that needs some memory hacking.

[Fastred]

I recently began trying Bazaar (a python based VCS) to handle my saves.  I got tired of continually futzing around with compressing and naming my savegame region folder.  Not to mention that if I wanted to rollback I had to futz around more with deleting the savegame folder and extracting the correct compressed version.  Now I can just save the game, bring up the VCS window, commit the savegame (with a comment if I wish) and go right back into the game.  Rolling back if I want to test something out or I screw something up badly is a lot easier too.

[StrongAxe]

Go with mercurial or git, you will have whole repository locally, so will not have troubles with pulling/pushing to svn server all the time.

I thought about that, but for me sharing the saves is as important as having them version controlled.  I suppose I could still do an hg push. 

I love this Mercurial tutorial btw.

[StrongAxe]

Progress: Got my repo checked out on my machine and the process is working manually.  Note that the initial pull/push for a region is huge as you need to save tons and tons of world data, but a save commit for gameplay is fairly small, at least in fortress mode.

Next step: The script.