SVNKit just needs a valid URI. I think I hardwired the SVN command to only accept svn:// and http(s):// URLs but I imagine a valid file:// repo would work. The concept is a bit weird to me (presumably you're running a SVN server locally, so you could just connect via an svn:// URL) but I suppose it would work if file:// was whitelisted to work with SVNCommand too.
Sorry it took so long to respond. School and real life have gotten in the way.
The short version: I have two instances of KoLmafia on this computer and I only want to edit my scripts once. TortoiseSVN allows me to create a serverless SVN repo but I would need KoLmafia to accept a file:// address for that to work. But since there are other solutions and my use case is pretty fringe, it would probably be a waste of dev time to change this. If I really want to use SVN, I can always use Sourceforge or try to setup something like VisualSVN just for the fun of it.
I'm not sure what benefit there is to having multiple independent installations of KoLmafia unless you are trying to run more than two characters at once.
More than one person playing KoL on the same computer, but wanting to share the scripts that Razorsoup has written. Been there, done that.
Now I'm jealous. No one I've lived wanted to try KoL.
Now I'm jealous. No one I've lived wanted to try KoL.