Gamasutra: The Art & Business of Making Gamesspacer
View All     RSS
October 25, 2014
arrowPress Releases
October 25, 2014
PR Newswire
View All
View All     Submit Event





If you enjoy reading this site, you might also want to check out these UBM Tech sites:


 
The Importance Of Being Earnest (About Villains)
by Adam Bishop on 03/17/12 04:21:00 pm   Featured Blogs

The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.

 

This post is going to be about the antagonists and endings for a number of games.  Consider this opening remark a big SPOILER ALERT for any game I mention in the text that follows.  If you haven't completed a game that you see me begin discussing and you think you may want to play it in the future, you may want to stop reading at that point.

I began thinking about this issue upon completing Mass Effect 3 a few days ago.  Like many who have finished it, I found the ending to be frustrating and unsatisfying.  I thought about why the ending was so frustrating and about other games that had ended similarly and been similarly frustrating, as well as games that had ended differently and been satisfying.  Ultimately what frustrated me most about the ending was what frustrated a lot of other people - that the game essentially invents a new protaganist in the final few minutes, completely changing the thrust of the entire three games worth of plot up until that point (though are are a small number of ambiguous hints earlier in the game).

Getting It Right
One of my favourite games is the original Metal Gear Solid.  I've thought a lot about what makes that game so enjoyable, and one of the things that the game does is how effective it is at creating an antagonist that you're as interested in as the protagonist.  It introduces you to the antagonist (Liquid Snake) very early on, and then proceeds to create a number of instances where the player character (Solid Snake) interacts with Liquid, either by confronting him directly, by overhearing his conversations, or by discussing his actions with other characters in the game.  The game builds toward a fantastic couple of sequences between Solid and Liquid at the end that serve as both physical and philosophical battles between them.

I think the Solid/Liquid duel works on a number of levels, one of which is that as characters they create an interesting series of conflicts.  That Liquid is every bit as memorable as Solid is a big part of this.  But more than that, the main reason it works is because it provides players with a clear motivation.  "Liquid is an intelligent but devious man and he must be stopped before he launches nuclear weapons" is compelling and coherent.  The player is able to proceed through the game knowing what Solid ought to be doing and why (the why is very important), and when they finally defeat Liquid, there is a sense of release for having seen your task through to the finish.

Other games do this successfully as well.  Final Fantasy VII, another of my favourite games, introduces you to primary antagonist Sephiroth roughly 10% of the way through the story and continues to highlight the struggle between him and your party right up until the final one-on-one battle between him and Cloud.  When you beat Final Fantasy 7, you feel like you've reached the end of an important journey, having completed what you set out to complete.

Interestingly, the original Mass Effect does an excellent job of this too, and that's one of the primary reasons that it's my favourite game in the series from a narrative perspective.  Even though the game does eventually reveal that the "real" threat is Sovereign and the other Reapers, it continues to use original antagonist Saren right up until the very end.  The Reapers are set up as a larger foe for Shepard to continue to fight over the course of the next two games, but the first game is the self-contained story of the fight between Saren and the Normandy crew.  When you defeat Saren, you have a sense of closure on what you've done in the game.

Getting It Wrong
The ending to Mass Effect 3 feels like a slap in the face, by comparison.  You spend the entire second game learning about the Reapers, and you spend the entire third game preparing a team to fight them.  I spent a little over 30 hours completing Mass Effect 3, and so I think I can fairly say that I spent 30 hours completing a variety of tasks under the impression that I was playing a game about ending a war with the Reapers.  But then, with about 5 minutes left in the game, a super-intelligent AI which was controlling the other super-intelligent AIs shows up, and tells me that ending the war has nothing to do with any of the tasks I've completed up to that point, has nothing to do with the battles being raged across the galaxy that I've taken part in.  Instead, it tells me that all I really need to do is make a philosophical decision about whether or not transhumanism is the direction that the species ought to evolve in.

Wait, what?  Let me state this more plainly, in order to tie it in with my examples above: what the AI tells me is that I was never really fighting the Reapers to begin with.  This is a violation of the trust that the game establishes between the player and the developer.  It says that all of the time I've put into the game so far has been based on a false premise, a premise the developer knew was false.  The issue isn't whether or not the ending is "happy" or "sad", but whether or not it treats the effort that the player has put into getting there as valuable.  If the player is told that they're progressing toward a certain goal, and that goal is not only rendered unachievable but irrelevant, right at the very last moment, then the player can very easily feel like the time they've put in so far was a waste.  The developer isn't just affecting the player's perception of the narrative, they're affecting the player's perception of the value of the real-world time that they put in to reaching that point.

I can think of another game that was heavily criticised when it was still new for doing something similar (though not at quite as late a stage of the game), and that game is Final Fantasy VIII.  In FFVIII, the player is introduced to the sorceress Edea early on.  They chase after Edea until they reach the end of the first disc (out of four, though the final disc has very little plot content on it), and then a large battle occurs in which the player loses to Edea and the primary protagonist, Squall, is seriously injured.  The player then discovers, potentially dozens of hours into the game, that the real enemy is a sorceress from the future named Ultimecia who has been controlling the sorceress Edea.  The player never sees or hears from Ultimecia until the very final series of battles at the end of the game.

Sound familiar?  The similarities between the two games are striking.  A super powerful force (an AI or a sorceress) appears to be your primary enemy.  You then discover that the real enemy is another AI/sorceress, controlling the one you thought you were supposed to be fighting, who has a goal that is quite a bit different from the goal of the original AI/sorceress and who is defeated by very different means.  Both games have been heavily criticised for the same reason - rather than being clever or compelling plot twists, the player feels like the rug has been pulled out from underneath them and their previous actions rendered largely irrelevant.

There's a distinction that I want to make clear here, because I think that it's important.  I have no issue with characters lying to me within a game.  In fact, I think Mass Effect 3 would have been a lot more interesting if it wasn't always so clear what all of the characters were thinking.  What I do have a problem with is the developer lying to me, and that's what I discovered had been happenning at the end of Mass Effect 3.

I think the differences between the ways in which the first group of games (Metal Gear Solid, Final Fantasy VII, and Mass Effect 1) and the second group (Final Fantasy VIII and Mass Effect 3) treat their antagonists can be instructive when trying to decide how best to design narrative arcs and player motivations.  Creating an antagonist (or antagonists) that the player can connect with and allowing the player to ultimately feel as though they've overcome the odds and defeated that antagonist will result in a much more satisfying conclusion to the player's experience.  This is certainly true, at least, for games centred around action and adventure that deal with violent threats of a global (or larger) nature, though I acknowledge that it may not necessarily be true for more subdued games (like Heavy Rain). 


Related Jobs

Digital Extremes
Digital Extremes — LONDON, Ontario, Canada
[10.24.14]

UI ARTIST/DESIGNER
University of Central Florida, School of Visual Arts and Design
University of Central Florida, School of Visual Arts and Design — Orlando, Florida, United States
[10.24.14]

Assistant Professor in Digital Media (Game Design)
The College of New Jersey
The College of New Jersey — Ewing, New Jersey, United States
[10.24.14]

Assistant Professor - Interactive Multi Media - Tenure Track
Bohemia Interactive Simulations
Bohemia Interactive Simulations — Prague, Czech Republic
[10.24.14]

Game Designer






Comments


Robert Boyd
profile image
I haven't played Mass Effect 3 yet, but there's one theory on the endings that I think makes them pretty awesome and makes them fit the general themes of the game - http://www.gamefront.com/mass-effect-3-ending-analyzing-the-indoc
trination-theory/

[User Banned]
profile image
This user violated Gamasutra’s Comment Guidelines and has been banned.

Adam Bishop
profile image
I've come across that theory, but even if it were true (and I don't think that it is), I'd still stand by everything that I said above. It would still be the developers pulling the rug out from under the player at the last possible moment for the sake of an "Aha! We got you!" moment that devalues the work the player has put into reaching that moment.

Matt Waldron
profile image
"I have no issue with characters lying to me within a game...[w]hat I do have a problem with is the developer lying to me..."

Adam, I completely understand what you are driving at here, and even though I would not have used quite this phrasing myself (albeit I haven't come up with a particularly excellent alternative), I think you make an excellent point that speaks generally to the rules of good story-construction.

While games do indeed represent a unique story-telling medium, and therefore carry many of their own unique nuances and methodologies, there are certain basic rules of storytelling that are universal—the one that has most prominently drawn your ire is that of leading the audience in a particular direction for a majority of the story and then changing the direction massively at the end in a way that is disharmonious and leaves the audience member to try to find a new footing (his previous having been suddenly stripped away) for the final small percentage of the tale that remains.

That is not to say the 'twist' ending is inherently bad; indeed, with respect to longer games with intricate plotlines some sort of major, unexpected development is an outstanding device for a storyteller: it gives the story variety, it adds scope by showing that there is more than meets the eye, and it allows the introduction of potentially excellent and interesting new characters to keep things lively and ever-changing. The concept of the 'reveal' is not new to games, particularly RPGs, but it is very difficult to do right.

In staying with your formula, allow me to offer two contrasting examples of a 'twist' involving the reveal of the 'true' villain: Final Fantasy IV (where the reveal is done poorly) and Final Fantasy VI (where the reveal is done brilliantly). I'll keep this brief and perhaps expound upon it in more detail in my own blog when I find a moment:

In Final Fantasy IV Golbez is a fantastic villain, right down to his ever-memorable theme music. The writers do a perfect job in both keeping him at a distance so he has an omnipotent aura about him while presenting enough interactions to allow the player to get to know his character. Then with about 10% of the game remaining it is suddenly revealed that Golbez is being controlled by some hereto unheard of villain named Zemus who lives on the moon! That's a terrible job of story-telling: you lose your best villain with whom you've developed a substantial relationship to a random new character of unclear motivation who you only meet at the final battle. FFIV is arguably my favorite game of all time, but they screwed up story-wise with this last minute maneuver.

In Final Fantasy VI, by contrast, we are introduced to Kefka early as one of the underlings of the emperor (who at the time is the primary antagonist). Yet the story is crafted so cleverly that any astute gamer realizes early on that Kefka has a level of evil that far supersedes that of the emperor. About half-way through the game, Kefka seizes his opportunity to kill the emperor and stake his claim as the true villain of the story, creating a dark world that perfectly expands the scope of the story while allowing the player more than enough time to come to terms with the change in primary antagonist (aided by the already established relationship between Kefka and the party). FFVII employs a similar form with Shinra and Sephiroth, but I feel their choice to make Sephiroth a somewhat sympathetic figure makes the FFVII ultimately just a bit less effective. I'm honestly not certain there has been a villain better than Kefka or a superior storyline to that of FFVI.

Bernardo Del Castillo
profile image
Wait up, you say that mass effect 1 does it well?.. but is't it exactly the same? you think you are going to fight saren, then you find out saren was being mind controlled, and it was actually the reapers who were the bad guys?
I personally felt that Mass Effect 1 did it wrong, I felt exactly as you described. The only difference is that the other one was a cliffhanger, this is an ending.


none
 
Comment: