The code is the skeleton where I build my meaty narrative.
Thanks for the responses everyone! Always interesting to hear what makes other writers tick. I’m getting more into the flow of ChoiceScript, so I think I will do most of my writing straight into code.
That sounds a lot like me too! I usually really enjoy the planning stage, but then sometimes find I am less inspired in the actual writing, like doing the plan has kind of drained my creativity and excitement for the full text.
So I’m currently trying keeping a vague plan in my head, but writing my ideas straight into the first draft form, rather than putting out a detailed outline first. It’s slower, but I’m enjoying the free form creativity of the process, and find I’m coming up with possibilities that I wouldn’t have considered if I had written a plan first.
Very helpful, thanks so much for the detailed response It’s great that you have found a writing partner who complements your style and way of working, I imagine that must be somewhat rare?
Once I’ve got a first draft done I will be bouncing ideas off some of my writing friends for sure, but co-authoring is a big step further - it must require an art of cooperation and compromise.
Definitely true! Pros and cons either way, I think. But, working with another creative person who goes about writing from a completely different angle has given me a lot of valuable insight and made me more aware of what works or doesn’t in my own personal process. It just helps when you can push each other to be better and not annoy the crap out of each other, too.
You know, Mary, I haven’t ever done it this way, but this sentence has been ringing in my mind all day, and so I figured I would sit down tonight and try building a skeleton. I’m trying to do a technically tricky (for me) thing, and I figured I would see what all the fuss was about.
I expected to hate it. But I sort of like it. Maybe I just like the metaphor, though. But either way, I think I like it.
I haven’t actually finished any of my WiPs yet, but I’m happy to share my system, such as it is.
I’ve discovered that, however good my writing may or may not be, my ability to write is much more advanced than my game design skills. I recently scrapped an incredible amount of words because I had been writing a game with a poor design, and I’m now rebuilding that game from scratch.
So, instead of using a loose plot outline as I’ve done for previous works of fiction, I’ve taken to running a really specific outline for the entire game, including major plot points, pivotal choices, end states, and a rough idea of how we get from the choices to the end states.
My two favourite resources currently for helping to figure this all out are the CoG full game design guidelines, which helped me figured out a lot of the flaws in my game design choices, and also this blog article, which talks about writing plots in general.
I like to use paper for charts and names and that sort of thing, but I like to plot where I’m typing because I can adjust and fix as I go along, or expand.
Once I’m actually coding, I follow this article’s advice (same blog, different article) about writing basically what you’re going to write. Then I do the actual narrative, stats, and coding all together. (For those who’ve asked me how I wrote 120,000 words in a month for my CS Comp entry earlier this year, that was a good part of how.)
And I don’t write scenes in order. One reason is some older advice in a CoG blog article. (I’d be curious to see if that approach is still recommended, too.) I also find my first chapter is more useful at presenting the rest of the game when some of that ‘rest of the game’ is already finished.
My first rule of thumb now, though, is worrying about game design before I think about narrative. With that CS Comp piece, I made the mistake of whirling through without a finished design for the game, hence the current dismantling. There were parts of the game design that weren’t working, no matter how much editing I put into fixing the problems. The current method seems to be a lot more effective thus far. We’ll see!
If you’re worrying about game design over narrative, write an outline using our outline guide. I cannot emphasize enough what an important document the outline is–it is where the beginning of the game design is generated. We don’t approve outlines that don’t show us both a well-designed game and a story that we’re invested in. It’s as much or more a game design document than it is a summary of each chapter or what happens in the game. What happens in the game is design. So. Write out your stats. Work on your end-states, tie those end-states to secondary stats. Then fill in the story chapter by chapter and plug in branches and so forth.
Always flattering to hear that my words are ringing in someone’s mind!
But at the risk of spoiling my aphoristic statement I will expand to say: My game is short and it’s been very hard to write. Poor @jasonstevanhill is almost at the end of his patience. Lucky for him I’m nearly done! But: I have a hard time writing narrative because…well, as much as I’m a writer I’ve always considered myself a poet and essayist, not a fiction writer. Making up a story is hard for me. Very hard. It’s not in my bones, it’s something I’ve had to develop and still am developing. And I want to and I hope to have a COG pitch approved in the next month or two. But, in terms of writing fiction, the only way I can get it done is when I have a skeleton to begin with. I need it in order to move forward. If I can build a skeleton, I can drape it with muscle, then skin, then dress it in fine clothes, etc.
I have begun my first IF game and was curious how do other prefer to write. I have been writing and coding at the same time, but at times I feel as if I bit off more than I can chew.
Do you guys prefer writing first then coding, or perhaps coding while writing?
I have to switch it up. Usually, I do a “soft draft” that’s more… sections of paraphrasing than legit writing like a thick outline, and then I put in the code that directs me from one section to the next, menus, big stuff like that, and then I go through that and actually write, saving stats and smaller variables for the end. That helps me stay organized, anyway.
I have to do them together, or everything gets jumbled in my head.
That makes a lot of sense I tried that with another game I was working on found myself overwhelmed haha exp when there were variables that I didn’t account for in the rough draft
Same, plus being able to see progress of what your doing helps keep motivation up
I’ve got a notebook I keep with me while I’m working and it’s just pages and pages of “go back to line 1305, add variable for X” and “redirect path A to path C.” It looks A Mess, but it helps me so much. And it’s very satisfying to be able to scratch things off that list lol
I tried doing it all at once, like just writing and coding straight down, and it. killed me.
I didn’t think about that! That’s a great idea I have a note book as well but I never thought to use it in that way.
Coding kills me as well, but I feel as though I have come a long way since I first started. How ever due to still being a beginner I feel as if writing while coding actually hinders my writing.
I would much prefer to write and then go back as it just flows better in keeping up with my writing “mood”, but if I don’t code as I write I’d never get around to going back to do it. I’m far too undisciplined as it is.
It does also help me to manage the stats and how the choices change the future of the story in parts that run away from my loose outlines, so I find it necessary for my benefit in that aspect as well.
I do things simultaneously.
Right now I’m actually coding first, then writing the prose, which is much more structured.
But I have sometimes written short parts out before coding as well, and I can definitely see how writing the general story first would be preferable to some people. Especially if they don’t do any kind of outlining and such.
And well, the ones I code for write things, and then I code it. So far that works fine, but it’s only the linear beginnings, so it might get more difficult.
Omg?! Right!! If i don’t code as well I can go on for weeks and or months of just writing!!
It makes me think of writing differently. When I’m “just writing” like short fiction for publications and stuff, I’m thinking solely of content and style. When I’m writing with this, I’m also trying to think about text walls and how far between choices and page breaks and how to utilize extra screens for info that might not actually need to be in the narrative. It’s so different structurally and I think that’s got a lot to do with it, for me anyway, because I find myself feeling like that a lot too. That said, there’s nothing more satisfying than figuring out what’s causing a bug and fixing it it’s so nice.
Yeah I’m running into that issue as well with all the different var I’m trying to implement, it’s all looking like a jumbled mess.
Lend me some of your organization aura!