Looking for a BoT version (again...)

[taustinoc]

I know the feeling, Google Drive is behaving badly for me lately to, as in, if I save my Campaign over an existing version, MT through a java.io error and locks the file, which is deleted when google drive shuts down... It seems to be size related, as it does it with 200mb campaign files but not smaller 200kb files. Nor does it do it if I copy via windows...

It is very much a size issue (I've had it, too). Drive locks the file in C:\Users\username\.maptool\tmp (I'm not quite sure how, but that's the file MapTool says it can't access, and Process Explorer says it's locked by Drive), and keeps it locked until you either kill Drive, or reboot. You can save to a different (new) file name, though, without a problem. But as soon as I kill Drive, everything works fine.

With large files, Drive sometimes does . . . bizarre things. It's like it looks at upload speeds since it started syncing, and goes with the slowest speed recorded. So if you do a bunch of other, high bandwidth stuff for even a short time, Drive slows way the hell down on upload speeds, and takes forever to finish. And from what I can tell, once you get the lock error, Drive never releases the file. (I might be wrong on that. I don't have the patience to figure it out.)

I've taken to turning Drive off when I'm working on stuff in MapTool or Visual Basic (where Drive will occasionally just delete the project file, including all previous versions). The problem with that, of course, is remembering to turn it back on when I'm done.

So we must repeat after ourselves. Drop Box (Google Drive) is not a backup solution. (much like Raid is not a backup solution)

Sing it, bro. Both are collaboration tools, even if you're only collaborating with yourself. Neither is suitable for actual backups, though the versioning is useful at times.

[Jagged]

I code in two places and use Git for that, its what its designed to do.

One of the nice things that Git does is a local commit. So you can stage things in a local repository before you do a full commit at the end of your work day.

But having said all that I am not coding in MT Script and don't have the additional hurdle of getting it all into a zip file. So I can understand if it doesn't work for you.

If it was me, I would probably work in one directory and have a separate staging directory where I build from. That's how I normally work. Then Git becomes your storage space too, and you can drop Drop Box etc