How much can I trust my players to remember previous states of the story and not get confused?
In my game, the player may run into deadends in the story, which causes the game to end prematurely. This can range from the player simply getting killed, another important character in the story getting killed or an important event happening or not happening. Sometimes, you might be in chapter 5 and realize you need to do something differently in chapter 2 to progress in the game, otherwise you can't continue to chapter 6.
Thankfully, I have a save system in place that allows the player to easily go back to specific points in the story without having to replay the whole game. If a player, for example, wants to go back to the point in chapter 2, where their character crosses a bridge, they can. When they return there, they also get a quick recap of what happened up until that point. This should allow the player to clearly separate what happened before this point and what they remember to have happened after this point, as what happens afterwards may turn out to be very different depending on what they do differently this time around.
Remembering what happened in other playthroughs is still important. Just because the story plays out differently, doesn't mean that other elements don't exist anymore. That gang you managed to avoid in your current playthrough? Yeah, they are still in the place you avoided going to, they might just get their hands on another unfortunate victim instead, drastically changing what happens in later chapters.
I am unsure if this would cause confusion for the player or get too complicated to keep up with over time. The whole point of the game is to go through many paths and find the right one, while finding out more info from playing all the different paths and putting the pieces together based on knowledge the character shouldn't have at this point, because the game keeps resetting to an earlier state. Could this be too much for the player to keep up with? What can I do to make this a comprehensible experience (such as the recaps I mentioned)?
This post was sourced from https://writers.stackexchange.com/q/36111. It is licensed under CC BY-SA 3.0.
2 answers
My gaming experience is with Bioware games. In those games, choices you make significantly affect the way the game ends. Consequently, it is quite common to play multiple playthroughs to achieve the end you want, or to return to an earlier savepoint and tweak choices - that is, doing manually what you offer as an actual game mechanic (which I think is really interesting).
Bioware offer great stories, and my own gaming style is very story-oriented. However, I do not have the leisure to play every day, or even every week. Consequently, when I rollback to an earlier savepoint, I don't always remember what I've already done, which conversations I've already had, sometimes - what choices I have made on this particular gamethrough.
If you make going back to previous choices an integral part of your game mechanic, you must remember some players would be like me - committed to exploring every possibility, every nook and crevice of the game, but taking a looong time to do it. Remembering everything is not feasible, particularly if you can go changing decisions back and forth - one's got to remember which choice one made this time.
Then you have another kind of players: those who pay only peripheral attention to the story, unless you flash a neon sign that says "this is important" before them. Once they find out something in the past was important, a reminder of what happened would be useful for them too.
Of course, if you highlight the particular choices that are important for gameplay, that makes other choices become boring, irrelevant. Which is boring in terms of storytelling, it reduces your player's commitment to the story. And if your reminders are too blatant, that would become tiresome to players who plough through the whole game in a short time.
A solution I see is expending on the Bioware codex mechanic: all kind of information you find in Bioware games (character bios, letters between NPCs, in-game stories, technical manuals of spaceships etc.) go into an array of text files - codex files, which the player can browse at their leisure. Why not make such a file (text, pictures, whatever) that records briefly everything the player has done this time around, and gets updated with every new choice made? Then, if a player remembers - good for them, this isn't distracting. If the player doesn't remember, they can go and check.
0 comment threads
Maybe you could use some form of rewind technique, summarizing all the (bigger) choices the player didn't do when jumping back to an earlier point. Unfortunately, while that's easy to show when rewinding a movie, narratively I have no idea how to describe that.
Maybe, instead of directly loading a save game, the player could jump back branching point by branching point until they reach the point where they want to change.
Going forward through the game, the player will always get the usual two choices (or however many options each branch has), but when they go back through time, they get presented with a third option to undo their previous choice.
Stepping backwards through each choice would then be a good summary of what they did that, in the new play-through, they haven't done yet. Unfortunately, this only really works if there are very few branching points, and even then sounds like it could get annoying quickly.
Alternatively, if you have a visual representation of save states, you could display a summary of the situation when hovering over a save game (sorted chronologically, and probably grouped by chapter). This has the advantage that it makes jumping back to a long ago point very quick, but still leaves it up to the player to view each branching point.
In addition, you could display a summary of the player actions when skipping an entire chapter, so undoing a choice from way-back becomes more convenient.
As you can see, the solution might lie in UI or game design rather than narrative itself, so you might also consider asking on https://gamedev.stackexchange.com/
This post was sourced from https://writers.stackexchange.com/a/36112. It is licensed under CC BY-SA 3.0.
0 comment threads
0 comment threads