So, as I mentioned in my last post, “Book Review Blitz Coming,” I suffered a power outage on Sunday that resulted in me being locked out of the file I was working on (and had been since June). Here’s what happened and how I handled it.
First off, some context. Scrivener is a software tool designed to help writers write texts and stay organized because that’s what a writer does. Its main purpose is to allow writers to write scenes in any order, shuffle them, label them, group them, whatever, so that they don’t have to write in a linear fashion or get lost should they decide that’s a good idea. It’s also a tool that can store research files, including other documents, photos, videos, spreadsheets, web links, etc. so that the writer doesn’t have to scour his hard drive for every bit of info he needs to complete his project. For a program that costs just $40-$45 (depending on your operating system), it’s really handy, as long as you don’t try to store a HUGE amount of info.
So…I’ve been trying to store a huge amount of info, and I discovered on Sunday that that’s a bad use of Scrivener.
I’ve mentioned it here on this blog, and somewhat extensively in my article “Using Scrivener for Game Design,” that I’ve been working on a computer game since 2009 called Entrepreneur: The Beginning. I’ve been adding to it for about five years when I came to the realization that the scripting was just way too messy and inefficient to continue on the path I’ve been working on. I kept working on it for another couple of years, but that was precious time spent on a task that could’ve been completed in less than a day under a different set of rules.
If I can reduce two years’ worth of work into a single day, you can bet I’ll do it.
So, in the summer of 2017, I set out to rewrite the code for Entrepreneur: The Beginning in an effort to make it more efficient and easier to update in the future. I decided to use Scrivener to handle this task, as it’s the best software I have to view things side-by-side and keep real-time backups and comparisons without having to stumble my way through the project.
I didn’t count on the program having trouble handling such a massive load. For reference, your average novel is about 50,000 – 120,000 words, split into anywhere from 20 to 100 chapters. The script for Entrepreneur: The Beginning with all of its originals and rewrites comes out to more than, well, a lots of lots of words and hundreds and hundreds of folders. It looks like it’s safe to say I’ve pushed it beyond its limits sometime in the last month.
Just to be sure Scrivener itself wasn’t broken, I tried loading up a different file, and saw that the file I chose loaded just fine. Then I tried opening my Entrepreneur: The Beginning plotscript file to watch in horror as it not only failed to respond, but actually closed the one I’d just opened. I tried reopening the closed file, just to be sure I didn’t break anything in that process, and found that it opened just fine. I tried reopening the plotscript file again, just to watch it close out all of Scrivener again.
Things were looking pretty dark for my eight months of script rewrites, but I wasn’t about to give up. Not physically, anyway.
I looked up information about document recovery, which yielded differing results, but the one I found most helpful was the one at techtoolsforwriters.com, posted here.
I took the article’s advice. I searched for my folder dedicated to backup files. I found it. I found the most recent five backups in the zip files the article talks about. The most recent was for January 22. (For reference, that’s the one I’m using to scan my word count as I type this article, and I’m still waiting for it to calculate, and I’m beginning to worry it’ll never give me an exact answer, even if it doesn’t include the last three weeks’ worth of work. Again, Scrivener is great, until you break it.)
I was grateful to discover that I hadn’t lost seven months of work, but it was beginning to look like I had lost almost one month’s worth of work. That’s especially troubling when you consider that some of the scripts I’ve revised since January 22 are headaches in digital form that I felt pretty happy to conquer, and would never want to revisit. Yet, it was looking like I might have to.
Thankfully, Scrivener also has a “doc” folder for every project that stores every piece of content in a numbered RTF file, and that folder stays up-to-date. A quick scan of that folder via arranging my search by date revealed that my most recent uncorrupted file was updated a few minutes before the power outage, which meant the only work I actually lost was the script I managed to update while I was busy frying an egg for breakfast.
In other words, I hadn’t really lost any progress, and the work I couldn’t recover from the backup can still be easily copied and pasted into a new backup project, which I’m calling “Entrepreneur Plotscripts V2,” along with a new port that includes only the modified files so that I can keep a project file that’s only half the size of the original.
Am I happy I don’t have to repeat the last eight months or even one month of my life? Well, I’d go back twenty years and make different choices if I could, but that’s another story for another day. Short answer is…well, I don’t think that’s a tough one to figure out, Sherlock.
So, that’s what happened on Sunday, and that’s how I avoided losing eight months of work in Scrivener, and that’s what I’ve learned about Scrivener’s limitations and its backdoor reliability.
Oh, and that word count calculation? Still trying compute. Maybe I’ll cancel the action. It’s not even that important.
Please subscribe to my blog if you want to keep hearing stories like these. You might even learn something.