We've explained the virtues of open development in depth, but it's not obvious how this development strategy should apply to the Overgrowth story. I've already seen brief discussions about this occur in IRC, and given the 92 comment reaction to Aubrey's storyboard post, I think people may have some strong opinions on this issue.
Please feel free not to watch this.
The Problem
The first time you encounter a good story is usually the best time, and until someone builds a machine that can cause strategic lacunar amnesia, we will only experience stories for the first time once. While treating the story like every other part of our development would still be interesting, it could also spoil the magic of the player's first run-through of the finished game. Therefore we might want to consider following options:
Option 1: Wait Until The End
We can hide all the core story elements (campaign levels and story-related art assets) until the whole single-player campaign is finished. Then, when everything is ready, we reveal it all at once.
Option 2: Multiple Installments
We can release story elements in segments (like chapters) along the way so that the polish is there, but we don't have to wait until the very end.
Option 3: Individuals Decide
We could let preorderers individually choose whether or not they want to see story-related content. One danger is that people might not be able to resist checking out the story early, but may then immediately regret doing so (I'm sure there are some people who feel that way about the video embedded above). Another danger is that people who peek at the story early might end up leaking details and ruining the plot for those who have chosen to wait.
Option 4: Nothing Special
We could keep it simple and just throw story assets into the builds like everything else.
What's best?
We still have some work to do before this becomes an immediate issue, and no matter what, we'll continue to include all the latest tech features and modding tools in our builds. But since the story options are mutually exclusive, we thought we should ask for your thoughts on this issue instead of guessing in the dark. What option seems best to you? Is there another approach I haven't mentioned? (permalink)
Track us on ModDB (visit our page)
Please join us here too:
In overgrowth, I think lore is a bit important so you'd need to tell the story while they are playing it. Otherwise you'd make a separate section that documents the lore in overgrowth, and parts are unlocked as you progress through the game, etc.
Lore may be important, but leaking story details casually in updates and pre-release reports creates a hell of a lot of buzz. Then, when the devout follower gets the game, they are able to identify all of their enemies, companions and situations by name and have the thrill of feeling how it all comes together for themselves, even if they already know how it all goes down.
only release **** that is from the tutorial section
I think (like Noise) that option 1 is the safest , but it might get boring not knowing anything you are doing especially if the game is long so Nr 2 seems to be the best one.
(sorry about the reply i must have pressed the wrong button)
Option 1 is the safest and most logical.
hard selection... but i like second option.
There are a lot of hidden cost/benefit situations I can see with the implementation of each of these choices, but I think this is definitely one area where the end user shouldn't 'have it his/her way'. Being able to experience the story in a dis-jointed fashion (or having the choice to) will only serve to cheapen the narrative.
Installments will associate very heavily with episodic for many - would you subscribe to a timeline in which each part would be delivered?
I say dont release any story elements that are crucial, release only those that should be common in the universe, like characters the player should know, some towns or cities that should be known about, basicly anything that should be common knowledge to the characters to create the sense of familiarity, but leave the story out, do not reveal any events or development of the story that will make it predictable, so no spoilers =\
I want to play through and work it out myself. The game would lose a lot of its appeal if the story is revealed without even having to play the game.
Overgrowth would become more like the game adaption of a book, and the ending, twists, characters, and events would all be quite boring to me.
...But that's just me.
You don't have to explain everything...
You can release story related shots/art that really make people curious, rather than spoiling plot developments. Be selective. People can still give feedback on different aspects of it you release 'openly', and it can also whet their appetite for more.
If you're releasing stuff that is a bit of a spoiler though, I would be pretty upset, and it would definitely dilute the gameplay a LOT for me. Unless your story sucks, in which case don't worry about it ;)
Edit: So.. Combination of no. 1 and no. 2 would be my choice
Only talk about the silhouette of the story, the initial basics you will learn when starting to play the game and only show things that won't spoil the further story.
Wait until the end in terms of spoiling the story.
I won't tell a thing until I finish my mod :P