Take the 2-minute tour ×
Game Development Stack Exchange is a question and answer site for professional and independent game developers. It's 100% free, no registration required.

Let me give some context. Three of my friends and I have a pretty good game idea cooking. It's based off of a prototype I made that's evolving into a cool game mechanic. The mechanic itself is a toy that's fun on its own, but we haven't designed any puzzles around it yet. We have a design document going, and we are answering a lot of questions about what's in the game.

It's become clear early on that everyone (including myself) likes the characters and the story a lot. Considering what our favorite games are, this is unsurprising. A story driven game makes sense to me. I like the emphasis that Paper Mario: The Thousand-Year-Door, Portal 2, and Tomb Raider place on story, and I imagine our game will have a similar feel (lots of dialogue, plot twists, lovable characters). These games, IMO, have very successfully merged gameplay and story, so I know it's possible to do this successfully.

However, one team member raised this point in the design doc:

I am feeling like [fleshing out the story] is our biggest hurdle right now for making more design decisions - like more specific decisions about levels etc. Is this true?

I am uncertain about working on the story extensively before gameplay, and my uneasiness was reinforced when I read this question about story vs. gameplay.

Main Question

My team and I want to design a puzzle-adventure game, such that (in the final version of the game) the puzzles and other gameplay sequences integrate with the story as naturally as possible (the gameplay should, of course, be fun on its own), while the story itself (including plot, characters, events, etc...) does not feel contrived. In light of this goal, in what order should the design of gameplay and story be carried out? And more importantly, what tasks can/should be completed in parallel (by different team members)? Is there anything we need to be wary of during development?

share|improve this question

closed as too broad by Josh Petrie Oct 27 '13 at 16:02

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

    
Please let me know what else I can say/specify to restrict the scope of this question to an acceptable level –  NauticalMile Oct 27 '13 at 19:46
    
Here is an excellent video by Extra Credits explaining (their take) on narrative in games. –  NauticalMile Aug 3 at 14:16

1 Answer 1

up vote 5 down vote accepted

I can't say I've played all puzzle games in existence, let alone all games with puzzles in them. But I only remember one about whose puzzles one could say they were all always placed at the one and only appropriate point in the narrative and that they contributed immensely to it.

What I mean is that when the designers of most games insert puzzles (or rather, "specific gameplay sequences") at certain points in their story, their goal is to challenge the player. And that's it. Maybe because the story requires it at that specific point in the game, maybe because it gives the gameplay rhythm.

Take Half-Life 2, for example, and give me one example of a puzzle (you know, the physics ones) at some point in the game which couldn't have been replaced with another one, due to the story requiring that specific type of gameplay at that specific time. I know that in the latter half of the game, the puzzles require the Gravity Gun and can't be done without it, but the gameplay is pretty much the same: grab->put down, grab->throw.

The same applies to almost all games, where the aim of a given bit of gameplay is always either to give the player a gameplay bonus or to allow them to move on in the story or more rarely, as in Deus Ex: HR or LA: Noire, to reveal more about the depths of ths story.

On the other hand, in Braid, the gameplay and "story" are tightly interwoven. The first chapter is supposed to be "forgiving" and about innocence and so is the gameplay. The chapter with the ring is about finding comfort in the presence of someone dear, all the while knowing that their companionship is a burden (to someone as ambitious and driven as Tim), and the gameplay is a perfect translation of that. The same applies to the other levels and even to the epilogue.

Jon Blow himself said about his game design experience with Braid that it was like sitting in a gold mine and scooping nuggets of gameplay, examining them from all angles (or something along those lines, was it in Indie Game: The Movie?). That's the phase you're currently going through, it looks like.

So I what I would do if I were in your case, where you have a unique idea and you'd rather sit in the gold mine and scoop nuggets than write a story, is do precisely that, do this job of scooping as many gameplay nuggets as you can. Once you have something to say, a message to shout out, then you'll write a story with these two constraints: the message and the gameplay. They will be unrelated enough that the story can accommodate them both.

Take, for example, this painting (the medium) that depicts an old Middle-Eastern king killing his servants, horses and dogs, bringing his world down with him as he is losing a battle and his palace is assaulted (the story). It's about grandiose decadence and egotism (the message).

We could imagine lots of different works of art with the same message. For example, imagine a scene in a movie about a corporate CEO who in the end burns entire bags of bank notes in his condo as the tax administration/feds/IRS/what have you are after him.

You can always write a story that adapts to your medium and message of choice.

Edit to answer the asker's comments: So you have a gameplay you like as well as a story you like. You would like to develop both further, but doing so would mean having to make sacrifices on the gameplay end or on the story end when comes the time to merge it all into an actual game.

One solution could be to work on the story first and use it as a constraint for the gameplay, which would only serve as the medium for it and, in your creative process, would always come second. Another solution, the converse of the first, is possible, where you find as many variations on your gameplay as you can and then see what can be done with it it terms of storytelling, hoping that you can build your original story around these gameplay elements.

All this cranking of constraints into others looks painful.

What I'm suggesting is that you take a good look at your story and try to pinpoint exactly what makes you like it in the first place. What, in its substance, makes you want to tell it. Extract that substance, forget about the details of the story like the setting, the names of the characters, their looks, the duration of the story, forget that it's about human beings (it could be about animals!), forget all of this and look at its substance, its deeper message, somewhat like I did (or tried doing) for the Death of Sardanapal painting linked to above.

Then, I assure you that you will never have the slightest bit of worry regarding cranking the story and the gameplay together. You will find the story that makes use of the gameplay to convey the message. I personally believe that that is what matters the most. So scoop those gameplay nuggets.

By the way, this is not how Jon Blow thinks we should make games, because this disconnects the message from the gameplay. If, like him, you can create an experience that is contained within the gameplay and have the player extract the message himself from that experience, that's also extremely cool.

share|improve this answer
    
+1 for detailed and helpful answer, but I want to clarify something before I accept. Your answer brings a third element into the picture: the message. And you seem to be saying that the story is the means by which the message is communicated while simultaneously giving the gameplay its context. Is this correct? –  NauticalMile Oct 26 '13 at 21:23
    
And, if this is the case, should we be figuring out what our message is while 'digging out nuggets' of gameplay? –  NauticalMile Oct 26 '13 at 21:33
    
Thanks for the +1. Answered as an edit to the question. –  madshogo Oct 27 '13 at 2:08
    
This is great! Thanks for clarifying. I really like the idea of boiling down the story that we already have to understand what it is that we like so much, and I also have the freedom to mine for gameplay nuggets now. I will definitely watch that vid when I have time, and discuss your answer in our next design meeting. –  NauticalMile Oct 27 '13 at 4:01
    
You're welcome! I'd love to hear more about your project though. –  madshogo Oct 27 '13 at 11:46

Not the answer you're looking for? Browse other questions tagged or ask your own question.