Tag: Scrivener

2221: Seeing the Final Product Forming

0221_001

I spent a chunk of time today porting the work I’ve already done on a story from Google Docs online to Scrivener on my Mac. Scrivener is a piece of software I picked up quite a while back and have used sporadically whenever I feel creative; it’s a lovely piece of software to keep written projects of any size manageable and organised.

For the unfamiliar, Scrivener allows you to organise your whole project into a single file, including the chapters and sections/scenes of your book, research material, front matter and general notes. Within the file, you have a tree structure of folders and items, with numerous templates available for various types of project. When you’re all done, you “compile” the project like a computer program, and Scrivener spits the finished product out in the format of your choice, be it double-spaced manuscript for sending to a publisher, attractively laid out pages ready for self-publishing, or various popular eBook formats. You can even export it to a word processor if you so desire, allowing you to format it further using tools beyond that which Scrivener offers.

I was surprised what a feeling of motivation I felt from porting the existing content over to Scrivener, and I attribute this primarily to the fact that what you bung into Scrivener looks remarkably like what the finished product will end up being. In fact, if you compile a project in progress to a PDF just to have a look at how things appear, it’s even more motivating, because you can imagine holding the finished book in your hands. That’s quite exciting.

Just the fact that Scrivener uses some very attractive, convincingly “book-like” default fonts helps with this feeling of seeing the final product coming together, though. Couple that with the fact that Scrivener’s interface is designed to be as clean and distraction-free as possible, and all in all you have a piece of software that is eminently suitable for creative types to realise their written ambitions — even if you barely use a fraction of the functionality the software has to offer, which I suspect is a category I will probably fall into unless I want to get really anal about page headers or something.

Anyway. This is a long-winded way of saying that I have been successfully motivating myself to continue with my creative writing project while I still don’t have any full time work. I’m under no illusions that I’ll be able to make money from this — at least initially — but the story I’m working on at present is a passion project that it will simply be satisfying to see completed at last, and released into the wild. If anyone ends up actually buying it, so much the better, of course, but if nothing else completing a project of this sort will 1) show me that I can do it, and hopefully inspire me to do more that take less than 15 years to complete and 2) stop my mother telling me every so often that I should “write that book”. (She hasn’t done that for a while, to be fair, which probably means it’s due a mention sometime soon… I know you’re reading, Mum, so take this as assurance that I’m doing it.)

So that’s that. Writer? Windows or OSX-equipped? Give Scrivener a go, and you might just be surprised how much you can get done.

#oneaday Day 941: Scrivenings

I’ve been spending a bit more time with Scrivener, a writing tool that I picked up a while back and then didn’t do much with for a little while. Having paid actual money for it, though, I figured it was high time I delved into it and actually started using it for a project rather than it being one of those things that just gathers (virtual) dust as a symbol of past good intentions.

I decided that the project I was going to use it for was a visual novel. Regular readers will know that I find this simple but effective form of interactive storytelling to be a fascinating medium, and I have been toying with the idea of writing one for quite some time, usually falling at the first hurdle when I remember I have little-to-no graphical talent, which somewhat precludes me from incorporating the “visual” bit.

But, I figured, no sense worrying about graphics if there’s nothing for them to visualise. So I decided to actually start writing it, and to use Scrivener to plan it out in advance.

Now, when I write, I must confess that I rarely go through a formal “planning” process. This is probably fairly evident in these daily blog posts, which tend to spew forth directly from my brain and out of my fingers in some sort of hideously unorganised stream of consciousness. But it’s the way I’ve generally worked on more formal pieces over time, too. During A-Levels and university, I never “planned” an essay on a piece of paper beforehand. I never used the “outline” function of Word, I never scrawled things on Post-Its and then moved them around. I just wrote, then tweaked, fiddled and moved things around once I’d written a first draft. It worked for me.

Mostly.

That approach doesn’t work so well with long-form fiction, whether you’re attempting to create a linear narrative for a novel or a non-linear branching narrative for a game or visual novel. I have a number of stalled novel projects on the go simply because I’m not entirely sure where they’re going. In some cases, I have an idea of what the end might be, but it’s the stuff in the middle I haven’t figured out. How to get from the beginning to the end, as it were.

So, as I decided to start work on this visual novel project (which, like an irritating PR agency for a company making an iOS game you don’t give a shit about I’m “not ready to talk about yet”) I also figured that I would give this whole “planning” thing a shot. I recalled seeing the spectacularly comprehensive flowchart for Katawa Shoujo (mild spoilers within), and knew that if I was going to put together even a relatively simple VN project, I would have to figure out some sort of way to keep it organised.

Fortunately, Scrivener has delivered just that brilliantly. In order to plan out the basic sequence of events, I’ve used the “corkboard” facility and its special mode where you can drag around virtual index cards as you please. I’ve written short synopses of each scene on each index card and laid them out in a logical fashion to depict the various routes the player might be able to take through the story. Each index card then corresponds to a separate “subdocument” in the whole Scrivener project, allowing scenes to easily be split up and composed a little bit at a time rather than simply being confronted with a daunting blank page and no idea where to start.

Then there’s pleasing little touches that help with the actual writing process, too. When writing in “Script” mode (which I’m using to compose the VN), simple keyboard shortcuts allow you to easily switch from writing actions to character names to dialog and back again. You can create links to other subdocuments or your research (which you can also store within your Scrivener project). You can split the editor window so you can refer to a piece of source material as you write. And when it’s all done you can “compile” your project ready for publishing as a physical product, ebook or other format.

I’ve barely scratched the surface of the features it offers, but already I can see it becoming an essential part of the writing process. Progress on the VN project is going well so far — I’ve synopsised (huh… according to spellcheck that IS a word) the whole of the first “act” of the game and am now starting on in-depth scripting for each scene. Following this, I’ll work on the various diverging paths through the narrative and hopefully end up with a suitably comprehensive document ready to plug into Ren’Py and then flutter my eyelashes at someone who can draw. Following that, who knows? Perhaps I’ll have a finished game one day.