Q: Which is harder, game writing with a team or solo-writing novels?

I actually got this question on Twitter, but I thought it deserved more than 140 characters. Although if you're into the tl/dr version then here you go.

So which is harder? Writing a game or a novel? Writing solo or on a team?

Game vs. Novel
First, you should know that I've never written for a non-Torment game, and Torment has lots (and lots and lots) of words. It's entirely possible there are games for which writing is a piece of cake. I wouldn't know what that's like.

What's difficult about game writing is the lack of control. In a novel, the characters do exactly what I tell them to (my characters do, anyway). But in a game, the player can do anything he wants (within the rules of the game). So a character I intended to be major might die before he gets a single line, and the writing has to handle both options equally well. So a dialogue that would be 150 words in a novel becomes an enormous branching, interlocking tree.

Novel writing has its own challenges, of course. For one thing, it's more than just dialogue. A lot more. A Torment game has more descriptive prose than most, but it still doesn't come close to what you need in a novel. The novelist has to let the reader into the protagonist's head, to feel what she's feeling. In a game, that's done for you -- the player's already in their own head -- but in a novel, that connection is a lot of work.

(As an example of how much work... By far, the biggest critique note on my Ninjas novel was, "Not enough description and emotion." It took me two months to revise that critique away, increasing the size of the novel by more than ten percent -- 10,000 new words almost exclusively adding description and emotion!)

Solo vs. Team
The best part of working on a team is that I don't have to write all the words. Torment has several writers working part- and full-time, so most mornings I wake up to finished conversations that I never wrote. It's like having an infestation of word fairies!

The hard part of working on a team is trying to agree on everything. We have strict conventions and pipelines to get everything to an equivalent level of quality with minimum fuss. When I'm in a writing role, I need to follow those conventions and get the approval of (usually) at least two other leads.

Even in my role as a lead, there are sometimes disagreements on how we should handle certain things -- anything from what the jargon of a town should be to the voice of a player companion to whether we should use one dash or two in place of an em-dash. Fortunately, we have a pretty great team, with a high level of professionalism and a low ego average, so even difficult decisions are rarely Difficult.

And really, the decision-making as a team is a lot of the fun. When I'm writing a novel, I have to make my own decisions, second guess myself, and be my harshest critic. My novel has no awesome story meetings with people I enjoy and respect (it's just me). And it is really, really hard to be objective about anything you make yourself.

Which do I like better? I like them both. A LOT. Honestly, if I had to choose only one of them, I'd probably rebel and just keep trying to do everything.

Oh wait, that's what I'm doing.

------------------------------------------

Got a question? Ask me anything.



2 comments:

Cap'n Heine said...

I've been pondering a similar situation with programming with a team at work and on my own project by myself at home. One is definitely not better than the other, they both have their perks. What's really nice is when they work together like when some new trick you discovered while programming at home saves you time and energy at work or vice versa.

Adam Heine said...

I like programming on a team of professionals, especially when the work is intelligently modular.

In college, though, I hated programming on a team. There was one two-quarter class wherein we programmed our own compiler -- notoriously the most difficult project in the CS program. The first quarter I had a partner. Everything I didn't code myself was late and buggy. Somehow I managed a B.

The second quarter I worked alone. The professor almost wouldn't let me. "This is the hardest course in the entire program," he told me. "Are you sure you don't want a partner."

"Trust me," I said. "It's better this way."

I finished everything ahead of time and got an A :-P