What Ali said. Version Control is disabled by default, but can be enabled in 5 minutes work.

You can use it across a VPN in a group as well, I tested this, the only reason MERP is not using it is because VC is over-zealous in marking ESM files as "updated", very often forcing everyone to copy the network version to their local system even when there is no real update (I suspect this happens any time someone "Checks Out" a form). This is not a problem in a LAN because copying 250-300 MB is a matter of seconds. Over the internet it takes far too long (for big mods like MERP at least).

Right now MERP uses TortoiseSVN for easy distribution and automatic updates of our main build (ESM's + resources). Everyone sends their ESP files + resources to the main merger (currently that is me) who uses VC to merge the ESP's into the ESM's and then adds those (+ new resources) as a new revision to TortoiseSVN. All Developers only need to press SVN Update and wait a few minutes, and they have the latest version of MERP.

It works quite smoothly so far.

Post limit.