Thursday, October 25, 2012

Far Right Religion and Poisoning Our Politics

Enough is enough: we have to stop letting poisonous theology infect our politics by voting for it. Fundamentalist viewpoints are too often anti-societal and anti-humanitarian, and we shouldn’t allow rotten religion to dictate our politics. Numerous examples of this abound, but what’s got me fired up is the issue of rape, since so many folks seem to be espousing religiously-motivated views on the subject that are both offensive and wrong.


The Bible is wrong on rape, and because of that, Christians that take the Good Book literally don’t know what to do with it. It comes down to this: fundamentalists believe that the Bible is inerrant and (usually) the word of God, and that means the Bible always has to be right. It has to have all the answers, but that presents a problem, both for the fundamentalist and for everyone else, too. I think I can say that, as a society, we have intelligently agreed that rape is wrong, and that it is a horrible crime, and that means that most evangelicals think the same thing, even when the Bible seems to suggest otherwise. That leaves the fundamentalist with three options: 1) admit that his or her moral compass is right and that the Bible must therefore be errant (even if only on some matters); 2) decide that because the Bible is inerrant, his or her moral compass must be incorrect; or 3) uncomfortably try to rationalize the Bible’s stance on rape. The problem for society is that we have elected or could elect far too many politicians that choose either option 2) or option 3), which in turn legitimizes the extreme and terrible positions on rape that they hold. We have to stop. We must no longer elect politicians who hold these beliefs (and other extreme fundamental positions like them) and seem unable to answer even some of the most basic moral questions properly.

Now before I begin, I hope you’ll allow a brief caveat. Christians that choose option 1) on this or in any other area where the Bible and morality come into conflict, often abandon or lack fundamental views on the Bible. Once the Bible is no longer inerrant, it becomes open to interpretation and selective reading, allowing for a so-called “liberal” Christian viewpoint on any number of issues. I’m not concerned with those Christians who are not so chained to the literal aspects of a two thousand year old religion that they cannot comfortably adapt it to suit modern sensibilities and advancements. My issue is only with those Christians who would tether us to the often incorrect morality of people that lived thousands of years ago.

When it comes down to it, the Bible does not have a great deal to say about rape, but everything that it does say about it is wrong. We can start from the beginning, with Genesis and the story of Lot, the only man deemed worthy enough of surviving the destruction of the wicked city of Sodom. This is the earliest point at which rape (or rather, the possibility of it) comes up, and we should expect that the virtuous Lot should know how to properly respond. What we find in Genesis, though, is that Lot has the wrong answer:[i]


9:4 Now before they lay down, the men of the city, the men of Sodom, both old and young, all the people from every quarter, surrounded the house.
9:5 And they called to Lot and said to him, “Where are the men who came to you tonight? Bring them out to us that we may know them carnally.”
9:6 So Lot went out to them through the doorway, shut the door behind him,
9:7 and said, “Please, my brethren, do not do so wickedly!
9:8 “See now, I have two daughters who have not known a man; please, let me bring them out to you, and you may do to them as you wish; only do nothing to these men, since this is the reason they have come under the shadow of my roof.”


We have here, in the very first book of the Bible, a man compromising with a gang of rapists by offering them his virgin daughters instead of his (admittedly angelic) houseguests. And, instead of admonishment for treating his daughters like tools meant to sate a bunch of drunks, Lot is allowed to escape Sodom’s destruction. So, almost right away, the Bible gives us a supposedly virtuous character who doesn’t seem concerned about protecting his own family from rape. A similar story, about an unnamed Levite, is recounted in Judges 19-22:27, which ends with the Levite’s concubine dead and her bones scattered across the Israel.

To modern eyes, this should seem reprehensible; however, from a Biblical perspective, Lot (or his Levite counterpart in Judges) may not have been that out of line. Quite frankly, the Bible doesn’t see rape as a particularly heinous crime, as demonstrated in the laws laid down regarding it in Deuteronomy: 


22:23 If a young woman who is a virgin is betrothed to a husband, and a man finds her in the city and lies with her,
22:24 “then you shall bring them both out to the gate of the city, and you shall stone them to death with stones, the young woman because she did not cry out in the city, and the man because he humbled his neighbor’s wife; so you shall put away the evil from among you.
22:25 “But if a man finds a betrothed young woman in the countryside, and the man forces her and lies with her, then only the man who lay with her shall die.
22:26 “But you shall do nothing to the young woman; there is in the young woman no sin deserving of death, for just as when a man rises against his neighbor and kills him, even so is this matter.
22:27 “For he found her in the countryside, and the betrothed young woman cried out, but there was no one to save her.
22:28 “If a man finds a young woman who is a virgin, who is not betrothed, and he seizes her and lies with her, and they are found out,
22:29 ”Then the man who lay with her shall give to the young woman’s father fifty shekels of silver, and she shall be his wife because he has humbled her; she shall not be permitted to divorce her all his days.


There are almost too many problems to innumerate in these barbaric laws (from many perspectives), but here’s what we can take a few things away from them with regard to rape. If a woman is raped in in a city and does not cry out (perhaps because she is terrified into silence or gagged) for help, she should die along with her rapist.[ii] If the rape occurs instead in the countryside, where no one can hear her, she is fortunately absolved of any wrongdoing (whether she cries out or not). If the rapist is caught in the act, the man has to pay a fine to the girl’s father, and has to marry her, with no possibility of divorce. This is perhaps the vilest aspect of all that Deuteronomy has to say on the matter of rape, as it means the victim must spend the rest of her life married to her rapist.
The attitudes of Lot and the Levite toward rape are disturbingly dismissive. While rapes of houseguests seem impermissible, the rapes of family seem to be an acceptable compromise.

Meanwhile, in Deuteronomy, we learn the punishment for rape varies depending on whether the rape also results in adultery (willful or not)—with adultery apparently being the more serious crime, since the rape of a woman not engaged results in marriage for both parties, rather than death.
Now, these examples come from the Old Testament. One might expect that Jesus, the great moral teacher, would condemn rape more forcefully and more mercifully (in the case of the victim). Unfortunately, the New Testament has very little to say on the subject, mentioning it only once, and only indirectly on that occasion. This happens in the Gospel of Matthew, where Jesus refers to upholding the laws of the Prophets:


5:17 “Do not think that I come to destroy the Law or the Prophets. I did not come to destroy but to fulfill.
5:18 “For assuredly, I say to you, till heaven and earth pass away, one jot or one tittle will by no means pass from the law till all is fulfilled.
5:19 “Whoever therefore breaks one of the least of these commandments, and teaches men so, shall be called least in the kingdom of heaven; but whoever does[iii] and teaches them, he shall be called great in the kingdom of heaven.


Once “all is fulfilled,” Jesus suggests that there may be changes to the laws of Moses; however, as of yet, all has not been fulfilled, so the laws of the Old Testament seem to stand. Beyond this indirect reference, Jesus offers no advice on the matter of rape to followers of the faith, and nor does the rest of the New Testament.

So, when the Bible mentions rape, it gets the matter barbarically wrong, and it is otherwise largely silent. Where does that leave us, today?  It leaves us with politicians, influenced strongly by fundamentalist Christian teachings, who don’t seem to understand the severity of rape as a crime. Not long ago, Todd Akin, Republican member of the House of Representatives and Senate candidate for Missouri made now infamous remarks regarding “legitimate rapes” and the apparent impossibility of pregnancy resulting from them. In the time following, numerous Republicans called for Akin to resign, but others have tried to stand with them or have offered views that are in many ways just as terrible.

One recent example is Tom Smith, a Republican candidate for Senate from Pennsylvania. Here’s an exchange between Smith and some reporters (source), regarding his stance on access to abortions:


Robert Vickers, Patriot News: In light of Congressman Akin’s comments, is there any situation that you think a woman should have access to an abortion?

Tom Smith: My stance is on record and it’s very simplistic: I’m pro-life, period. And what that Congressman said, I do not agree with at all. He should have never said anything like that.

Vickers: So in cases of incest or rape…

Laura Olson, Post-Gazette: No exceptions?

Smith: No exceptions.

Mark Scolforo, Associated Press: How would you tell a daughter or a granddaughter who, God forbid, would be the victim of a rape, to keep the child against her own will? Do you have a way to explain that?

Smith: I lived something similar to that with my own family. She chose life, and I commend her for that. She knew my views. But, fortunately for me, I didn’t have to… she chose the way I thought. No, don’t get me wrong, it wasn’t rape.

Scolforo: Similar how?

Smith: Uh, having a baby out of wedlock.

Scolforo: That’s similar to rape?

Smith: No, no, no, but… put yourself in a father’s situation, yes. It is similar. But, back to the original, I’m pro-life, period.


As a father, Smith apparently sees situations of rape and pre-marital sex as similar, which isn’t that different from the Bible equating adultery and rape in Deuteronomy.  In one instance, we have a woman who had consensual sex, became pregnant, and decided to carry the baby to term. In the other, we have a woman who was victimized and violated, became pregnant, and, according to Tom Smith, should do the same, without question. That he can even relate the two situations to one another suggests that either he views rape as a less serious crime than the rest of the population, or he views pre-marital sex as seriously as the rest of the population sees rape. Both positions are ridiculous and abhorrent.

Only within the last week during a political debate, another Republican Senate candidate, Richard Mourdock, offered his own cruel and unusual view of rape (source):
"The only exception I have to have an abortion is in the case of the life of the mother," said Mourdock, the Tea Party-backed state treasurer. "I struggled with it myself for a long time, but I came to realize life is that gift from God. I think that even when life begins in that horrible situation of rape, that it is something that God intended to happen."

The idea that pregnancies resulting from rape are a gift echoes sentiments of former Senator (and candidate for the 2012 Republican presidential nomination) Rick Santorum, who suggested that a woman could “make the best out of a bad situation” (source). Mourdock’s comments are even more callous, however, as they suggest that he believes the benevolent creator of the universe would deliberately allow or cause a rape to happen in order for it to result in a pregnancy. His remarks further suggest that the rape is ultimately justified because of the resulting pregnancy. But we all know that a good end shouldn’t justify terrible means to get there, and I can’t fathom how a rape could never be a terrible way for a benevolent God to arrange a pregnancy.

These politicians are undoubtedly not the first to espouse such positions, and unfortunately, they likely won’t be the last do so, either.  The truth is that they should never have arrived at the conclusion that any rape is trivial (in Smith’s case) or ultimately something positive because of a pregnancy (in the cases of Mourdock and Santorum), and nor should any other person, citizen or no. Such beliefs are poisonous and horrible, and were it not for the legitimacy of certain fundamentalist positions, rooted in ancient religion, people knowingly holding them would never even be considered for election to any government post in any civilized and humane society.

As citizens, we have to stand up and make sure that these beliefs are not legitimate. We may prefer a candidate’s views on fiscal matters (like taxes), but we should never sacrifice our moral fabric and endanger our sense of social justice over matters such as money.  The only responsible and moral thing a citizen can do is to vote against candidates with such views. That does not have to mean compromising your views on other, unrelated matters, as even a vote for a third-party candidate or a write-in vote is a vote against such ill-informed, fundamentalist moral ineptitude.

Get out and vote. You owe it to the country. Even if you’re in a state or district that will likely lean toward a candidate with such despicable views, vote against them. I truly believe that if we all voted, such terrible beliefs would find that they are truly in the minority. So, why don’t we prove that in November, and for every election in the future?


[i] All quotations are drawn from the New King James Version—any italics represent words that are absent from the original Hebrew or Greek but would have been understood. (This is why you’ll see the verb “to be” italicized in many translations of the New Testament, as the verb was understood to be the verb of most sentences otherwise lacking one.)
[ii] The idea that she otherwise enjoyed being “humbled” is implicit here, which is quite barbaric, too.
[iii] The Greek verb is ποιεω (poieo), which has connotations of “doing right,” not just acting.

Wednesday, August 29, 2012

What the Internet needs more off...

...is my poor attempts at eloquence. Mostly, I need an excuse to update this thing, so here's some bad poetry. It's like Christmas in August, right? And no, I don't really title these things. I'm not even sure I finished some of these, since I open this thing so infrequently.

Alpha
Speakers crooning
As they often do
Fragile glass
Filled with liver damage

Decadent confections
Corrupt a forgotten smile
Dopamine flutters
Like dandelions in the wind

Beta
Of two forms
In company, in laughter
Gears churning
Behind the curtain
Lying quiet
Fearful of falling bombs

Trigger hangs
Target in the center
Pull the switch

Shields crumble
Broken fortress exposed
Alarms sound
Defend the bulwark
Walls rebuilt
Only to fall again

Trigger hangs
Target in the center
Pull the switch

Gamma
Silence too often recurrent
And never blissful or profound
Punctuates discordian static
No more than bedlam devoid of succor

A friendship tranquil and empty
With allies welcome though bitter and dark
Dulls the quiet refrain of regret
To calm the wish to populate the silence

And thus comes not calm but complacence
With a journey ever downward
Along a path of no returns
And a silent ending of its own

Monday, June 25, 2012

Polutropos Odysseus


Most of us read ancient literature in translation these days, whether in school or for pleasure. These translations range from literal to flowery, but in general, all of them will be missing wonderful things that you can find in the original text. Words in one language don't always translate completely into another, which means that translators have to make choices about the particular meanings that they want to capture when rendering a passage in the target language. Here’s an example. These five lines begin one of the pillars of Western literature, the Odyssey:
ἄνδρα μοι ἔννεπε, μοῦσα, πολύτροπον, ὃς μάλα πολλὰ
πλάγχθη, ἐπεὶ Τροίης ἱερὸν πτολίεθρον ἔπερσεν:
πολλῶν δ᾽ ἀνθρώπων ἴδεν ἄστεα καὶ νόον ἔγνω,
πολλὰ δ᾽ ὅ γ᾽ ἐν πόντῳ πάθεν ἄλγεα ὃν κατὰ θυμόν,
ἀρνύμενος ἥν τε ψυχὴν καὶ νόστον ἑταίρων.
Here’s my quick and mostly literal translation, though many of you are probably familiar with the lines in general:
Tell me of the man, oh muse, much-turned, who every way
was made to wander, after he destroyed the divine city of Troy:
he marveled at the cities of many men and knew their minds,
and many pains he suffered on the sea in his heart,
striving to save his life and the homecoming of his companions.
Nearly all of us first came into the contact with the Odyssey through some translation or another. Robert Fitzgerald’s translation has long been popular in schools, but you may have first read Richmond Lattimore’s classic translation, Stanley Lombardo’s modern verse rendering, or perhaps an older prose translation, such as Samuel Butler’s or that of W.H.D. Rouse.

All of these translations, and most others, render lines 3-5 in mostly the same way as I’ve done, though each of course exercises his or her poetic muscles in one way or another with word-choice and phrasing. Every translator, however, faces a challenge in the first two lines, largely coming from the word πολύτροπον (polutropon or polytropon). This is the word I’ve translated as “much-turned,” which is an entirely literal reading that gives no real sense of the word's broad range.

Here are some examples to demonstrate what I mean. Take Samuel Butler’s translation of the first two lines (emphasis is mine—the italics are the translator’s rendering of πολύτροπον):
Tell me, O Muse, of that ingenious hero, who traveled far and wide after he had sacked the famous town of Troy.
W.H.D. Rouse takes a different approach in his prose translation:
This is the story of a man, one who was never at a loss. He travelled far in the world, after the sack of Troy, the virgin fortress
Here’s Fitzgerald’s, which is probably the most well-known:
Sing in me, Muse, and through me tell the story
of that man skilled in all ways of contending,
the wanderer, harried for years on end,
after he plundered the stronghold
on the proud height of Troy.
Richmond Lattimore (whose translation was the first one I read), gives us the following:
Tell me, Muse, of the man of many ways, who was driven
far journeys, after he had sacked Troy’s sacred citadel.
And last, but not least of the translations I have on hand, Stanley Lombardo, translates these lines so:
Speak, Memory, of the cunning hero,
The wanderer, blown off course time and again
After he plundered Troy’s sacred heights.
Here, just from five examples (six, if you count my own attempt), we have Odysseus described as “cunning,” “ingenious,” “never at a loss,” “of many ways,”  “skilled in all ways of contending,” and the more opaque “much-turned.” Every one of these renderings brings with it a certain picture of the hero, but in the original Greek, polutropon carries all of them and more.

Polutropon is an object-form of πολύτροπος (polutropos), a compound of πολύς (polus), “many” or “much,” (which you’ll recognize from “polytheism," and) and τρόπος (tropos), “turn,” or “way.” Tropos also carries the sense of a “manner” or “habit” (which should feel familiar if you've ever spent time at TV Tropes). Taken together, the most sensible literal English rendering of polutropos is “many-turned” or “much-turned,” but neither one of those captures much of the word’s real meaning.

Lattimore’s translation, “of many ways,” is perhaps nearest to providing some sense of the word in English while staying as true to the Greek as is reasonable. Polutropos is also used of the god Hermes, metaphorically, to indicate a certain craftiness or versatility. Odysseus certainly fits that bill, as well, which gives us Butler’s “ingenious” or Lombardo’s ”cunning.”

But, even ”much-turned” describes something about Odysseus. After the sack of Troy, his νόστος (nostos) or “homecoming,” doesn’t come to fruition for ten years. Why does it take so long? The Cyclops Polyphemus, after his famous (and painful) encounter with Odysseus, calls upon his father Poseidon to curse the man “skilled in all ways of contending, ” such that he comes home long after he would otherwise (and to find his home a mess when he finally does). Much of Odysseus’ ten year wanderings are a direct result of this incident, as Poseidon answers his son’s prayer, leaving the hero “much-turned” away from his destination.

Polutropos is just one example of why it can be illuminating and altogether more rewarding to read literature in its original language. Though each translation of the word is in and of itself an accurate one, each is forced to sacrifice some aspect of its greater meaning. Odysseus in particular is exemplary of every shade of meaning polutropos possesses, and the best way to capture that is to go back to the original Homeric Greek.

If you’re interested in learning more about Homeric Greek and Ancient Greek in general, you can head here. This site contains a few texts in the original Greek (like Homer’s Iliad) enhanced with mouseover definitions, as well as some suggestions on how to start learning the language on your own.

I’m eternally grateful to Professor Keith Dickson of the Classics Department at Purdue University, who sparked my love for the classics. This piece is ultimately derived from his lectures on Greek literature, which I thoroughly enjoyed all the way back in 2003.

Friday, June 22, 2012

Historical Rhymes Galore

In two days, I'll be packing up and heading back to the mind-numbing quiet of my hometown, South Bend, Indiana. The last time I did this, I had just finished my last year at Purdue University, but there was largely one thing on my mind:

I had imported the latest Hooverphonic album, and there was a chance it wasn't going to arrive at campus before my final day there. As it happened, it arrived at the last possible moment. I picked it up from the mail room before leaving campus for the final time. I then forced my parents to listen to it for the entire ride home, and it was awesome. For me, anyway.

As someone (who may have not actually been Mark Twain) once said, "History doesn't repeat itself, but it rhymes," and I hit the rhyme in stride with this upcoming move. Two years ago, Hooverphonic put out a new album--The Night Before--that came packaged with a new lead singer that never made it stateside. Having found it at an unbelievable-for-an-import price of $7.50, I ordered it and very nearly didn't get it prior to my actual move.

But it came in today, and it's got some of their best work since No More Sweet Music. Since I got the album in time to add it to my phone, I'll be able to listen to it privately for this trip back to South Bend, but I can't help but enjoy the coincidence. For your listening pleasure, here's my current favorite track:


Wednesday, June 13, 2012

Writer's Block

I often feel the urge to write even though I have nothing worth writing.

Most of the time, I call it writer's block--that's what it is, after all, isn't it? I want to write, to self-express (as Kevin Smith puts it, for instance), but the words are not forthcoming. I often wonder if others face these problems in their mediums of choice. Do artists sometimes not know what to draw? Do the lines just never feel right? The same could be said of musicians and their notes, or sculptures and the clay available to them.

Sometimes--nearly all of the time, in fact--it feels as though the words are there to write what I desire, but the structure is absent. Even now I'm writing largely off-the-cuff, having not known what would spill outward once I started typing into the posting interface on Blogger.  But what I'm writing now isn't what I want to write. It's just a misdirection, meant to trick my fingers and slightly alcohol addled brain into thinking the motions are in the proper place.

I do not, to be honest, understand writer's block. Most of often when I encounter it, the impetus to create is present: that desire inexplicable by any other means but to "self-express" in some fashion or another. For me, that fashion has always been one of words--I lack the talent to turn pencil strokes into recognition except by the arbitrary meanings of alphabet characters strung in still more arbitrary sequences. The words, indeed, are forthcoming, but that thing the words are necessary for: the scene, the character, the theme, the message...these are ephemeral, elusive.

Monday, June 4, 2012

A Recognition Scene

For context, you can listen to the following (or at least Google the lyrics):


More specifically, the recognition scene (or anagnorisis) in a Greek drama involves the sudden revelation to the main character of a critical fact. The most well-known example is probably the scene in Oedipos Tyrannos in which Oedipus learns that he is the murderer (of his own father) at the center of the play's central conflict (the plague) and the husband of his own mother (the queen). The recognition scene in the embedded Mountain Goats song is sweeter, in some ways (and not just because of the stolen candy), as it captures in time the moment in time when one of a pair of friends realizes not only that the other is crucial to his or her (though the singer is male, it's not specifically called out as such in the song's narrative) life, but that they will probably be separated someday. It's a bittersweet moment, and one that many people can probably relate to.

I do not often free-write, but I'm in the mood to, and recognition scenes are on my mind. So here's a recognition scene (post-writing comment: in verse, apparently, even if prose was my original intent). I make no apologies for the lack of literary quality, as the intent here is to put words to paper (haven't I done that already up above?), and there's Guinness and Jameson both at hand. Hopefully, the words that follow do not assault the senses violently, at the very least.

Ordered strips of gray concrete
Dividing patches of densely packed snow
So blinding in the early morning sun

 Mercury hovers in digits solitary
And the wind defies the numbers
Stinging skin, dying it painfully red

But it is that time appointed
A finger already numb from cold
Rings a doorbell in sweet anticipation

Yet harsh exposure continues
The programmed chime left unanswered
A meeting perhaps forgotten or forestalled

Minutes tick while the flow of blood slows
And dry eyes well with tears soon frozen
By the bitter truths of mid-December

Something masquerading as a finger
Strikes the doorbell thrice more
First in concern, then desperation, and finally anger

Morning crawls on, limping in the harsh chill
Time passes unmarked as higher thought declines
Such that departure is dismissed on principle

An age goes by and only then a door opens
Fury hardened in winter melts like ice in summer
Leaving only three words spoken from visitor to guest

Tuesday, May 15, 2012

The Magic of the Kindle Made Me a Believer

This will be a short one, contrary to my normal verbosity.

I've resisted getting a Kindle (or some other e-reader) for some time. Like others, I wanted the feel of a real book in my hands, and ultimately worried that the experience of reading wouldn't be the same without that. There's just something in the feel of the paper in your hands, and the weight of the book itself, that has always contributed to the experience for me.

Today, in light of a surprise influx of funds, I picked up a Kindle Touch, ultimately because the lower price of ebooks would go a long way to supporting my interest in way too many books that come out these days. I'm incredibly happy to report that reading on my Kindle feels so much like reading a regular book that I find myself acting out old habits while reading: reaching for the top corner of the device as I near the last line on the page, so I can turn it seamlessly; looking for my bookmark as I pause my reading to take care of something else; and cradling the Kindle (with the fold-over case) just like I would any other book.

While I was in line at Radio Shack, the guy behind me mentioned that he loved his Kindle, and that I would "read more and read faster," and at least, for the moment, I'm inclined to believe him.

If you've been on the fence, do yourself a favor and go pick up one of the many Kindle models (personally, I'd stick to the E-Ink screens, rather than the backlit screen of the Kindle Fire, though). If you love books as much as I do, I don't think you'll regret it.

Monday, April 30, 2012

On Mass Effect 3: A Broken Narrative

I discussed before how Bioware failed to live up to the expectations they fostered for Mass Effect 3. That failure has played a part in the controversy surrounding the game's finale, but it's by no means the only part of the problem. The largest contributor to the outcry, as you might expect , the ending itself. The ending, only the last fifteen minutes or so of the game, contains a large number of inconsistencies and other narrative problems [N.B. Spoilers abound in the link and the rest of this post], lovingly collected for your pleasure by the fans.  These issues are so numerous that fans combined them with a mountain of circumstantial evidence from the rest of the game to conclude that maybe Commander Shepard was in fact dreaming while unconscious or "indoctrinated" by the Reapers.

To be honest, inconsistencies like these aren't exactly rare in video game narratives (or in narratives in general). Mass Effect 2 had a number of them all to itself, and the same could be said of many other games. With any narrative work, the audience suspends disbelief so that these things don't get in the way of their enjoyment; however, if a writer isn't careful, his narrative may end up breaking this suspension of disbelief, intentionally or not. When that happens, the audience often finds it very easy to pick apart the entire work, viewing things as problematic that they may not have noticed at all otherwise. In a nutshell, that's what lead to the massive Google document on the inconsistencies I linked above.

Many of the problems in Mass Effect 3's ending are minor and don't explicitly endanger the narrative. For example, while it's pretty odd that Admiral Anderson says he follows the Commander up to the Citadel (the setting for the game's last few scenes) when he's clearly ahead of Shepard on the path and seems to have gotten there before her according to some of the following dialogue, the throwaway line about rooms shifting is enough to allow the audience to wave it off. These minor issues, however, have some pretty big friends, all of which break from the narrative substantial ways. These larger inconsistencies ultimately create the impression that Mass Effect 3's ending was written for some sort of alternate reality Mass Effect series that had different emphases and themes. This Bizarro World Mass Effect (let's call it Massive Effect) would, in accordance with the ending of Mass Effect 3, have an emphasis on uniformity as the answer; a focus on the galaxy rather than the individuals within it; and have the tension between organic and synthetic life as its central conflict. By contrast, Mass Effect as we received featuresan underlying method of unifying the diverse to overcome a common enemy or threat; a focus on individuals and their lives, from family problems and love to matters of revenge and personal hatreds; and a central conflict in which "small" beings struggle against the impossible and win.

The differences between Massive Effect and Mass Effect are easily seen in their disparate approaches to the theme of diversity. In the "best" ending to Massive Effect, we're given the opportunity to create a new form of life that synthesizes organics and synthetics into a new hybrid form of life that eliminates by necessity the conflict between the two of them. This synthesis option neatly ties up the organics/synthetics problem that the ending presents as paramount (which I'll discuss in more detail below), but it's a jarring break in Mass Effect's treatment of difference up until this point.

Throughout the series, Commander Shepard assembles a rag-tag team of humans and aliens of varying species to combat a threat that's greater than all of them. Their differing backgrounds, unique perspectives, and areas of expertise all prove valuable to the mission at hand. In both Mass Effect and Mass Effect 2, Shepard brings aliens aboard human-centric vessels that are initially hostile to alien life. Through victory, she then proves that the hostility is unwarranted. On the smaller scale, this idea of working together in spite of difference is displayed in the resolving of loyalty conflicts between squadmates in Mass Effect 2. Examples continue of the strength to be found in unity despite diversity in Mass Effect 3, with Shepard doing the same thing on a galactic scale, bringing together numerous diverse fleets and research crews for the final battle with the Reapers. The downloadable Prothean squadmate, Javik, even comments near the game's end that it is the acceptance of diversity within the galactic fleet that has made victory against the Reapers attainable, as opposed to the situation in his cycle, where every race, under the empire, was essentially Prothean in outlook and strategy.

Positioning synthesis as the best ending (by having it only available in a mostly complete playthrough or with lots of multiplayer to boost your "score" in single-player) puts it at an odd place with regard to this long-running theme of the series. Up until that point, the solution has always been for diverse individuals (or races) to work together despite their differences (and indeed, often to succeed because of those differences), not to abandon those differences in favor of making everyone the same. This break in the narrative doesn't in and of itself a narrative problem, but it certainly causes a thematic one, which leads to an overall decrease in narrative cohesion.

Just as the ending to Massive Effect performs a weird about-face on diversity, it also abandons one of the greatest strengths and focus of the Mass Effect series: its characters. Over the course of three games, the Commander works with a menagerie of team mates, many of which become loyal friends and some of which are potential romantic interests. We learn about their histories, their peoples, their problems, and their dreams. We reunite them with lost family heirlooms, help them get revenge, save their families, represent them in court, and a number of other things that are entirely personal and only tangentially related to the greater cosmic threat of the Reapers. We do these things because the characters are well written, interesting, and the sorts of characters that really come alive in a narrative. Such characters are somewhat rare in fiction, but not in Mass Effect as a whole. Beyond your squadmates, there are bit-part characters that are just as memorable as the ones with all the screen time, from an annoying, sensationalist reporter to a battle-hardened (and totally awesome) quarian lieutenant.
Admittedly, the characters didn't come fully into the spotlight until Mass Effect 2 (which has a kind of Ocean's Eleven vibe), but even then, half the joy of the characters was meeting old favorites from the original Mass Effect. Because the audience has come to care so much about these characters, they could have (and I think, should have) been a centerpiece of the game's conclusion. There are any number of character-related plot-lines that are ultimately left unresolved in the ending to Massive Effect, ranging from whether Tali'Zorah vas Normandy gets to build her house on the quarian homeworld or whether Urdnot Wrex can truly manage to unite and control the bloodthristy krogan in light of the curing of their sterility plague.

Instead of rewarding our dedication to and love of these characters, Massive Effect presents us with an ending that has massive consequences for the galaxy at large, but the impact of which on our friends and favorites can only be speculated upon. Indeed, with the majority of the galactic fleet potentially stranded in Earth's solar system after the final battle, we can reasonably wonder if Tali'Zorah can even make it home to build her new house or if Wrex will ever make it back to his homeworld to lead his people to greatness. Your crew is (maybe?) stranded on some unknown garden world with apparently no way home, and with various species requiring differing types of food to survive, there's no telling who would be able to live and thrive on such a mystery world. At the end of Massive Effect, we've saved the galaxy, but we may have doomed our friends to painful (or at the very least, lonely) deaths. This again breaks from the strong character focus of Mass Effect as a whole, placing Massive Effect in Bizarro World as an alternate story that somehow got mangled with the one that had been so successful going back to 2007.

The last split between Massive Effect and Mass Effect that I want to address, that of their differing central conflicts, has been the subject of a lot of ridicule. The Catalyst in Massive Effect reveals that the purpose of the Reapers is to protect organic life from being wiped out by synthetic life, which is a somewhat circular argument, since the Reapers are largely synthetic themselves. The break in the narrative from Mass Effect comes in two parts here. Firstly, while the geth are painted as synthetics bent on destroying organics in the original Mass Effect, we learn that they do so largely because of the influence of the Reapers themselves. Additionally, through interaction with Legion (an advanced geth that becomes a squad member) in Mass Effect 2, we learn that the geth have a history of only attacking organics in self defense (as they did in the Morning War with their quarian creators, after which they let the quarians retreat without wiping them out). In Mass Effect 3, we're even given the opportunity to reconcile the story's main organic/synthetic conflict between the quarians and the geth, achieving unity despite diversity (which I dealt with above as well). While the example of the quarians and the geth does not by itself disprove the Catalyst's assertion that synthetics will always wipe out organic life eventually, the assertion is thematically at odds with the game's own narrative, which suggests that organics and synthetics do not, in fact, have to be at odds with one another.

Secondly, the games have never been primarily about the above conflict. The geth in Mass Effect were mostly unimportant servants of the actual threat, the Reapers themselves. From our first real interaction with a Reaper through our last one before Mass Effect 3, the Reapers are painted as a cosmic, unknowable force of evil, "beyond [our] comprehension." To them, the races of the galaxy are no more than "dust struggling against cosmic winds." The central conflict of the series has been between the Reapers and life throughout the galaxy: ants struggling against giants. In both Mass Effect and Mass Effect 2, Shepard and crew do seemingly impossible things in the fight against the inevitable: first destroying a Reaper and then entering uncharted space at the center of the galaxy to stop a second attempt by the Reapers to harvest life less directly. The theme itself is carried forward into Mass Effect 3, in that uniting the races against the Reapers seems impossible, but Commander Shepard does so (and spectacularly so in "perfect" playthroughs). This theme, and the conflict that goes along with it, are largely abandoned in the ending in favor of the secondary organics/synthetics conflict, which was resolved to narrative satisfaction several missions prior to the game's ending (with the geth/quarian conflict being its primary representation, it is also the vehicle for its resolution in a narrative sense). This sudden shift, from defeating the Reapers to resolving the apparently inherent conflict between organic and synthetic life (which the narrative has prior to this point shown to be a suspect assumption) takes the wind out of the game's narrative sails.

Ultimately, that's what you would expect if a narrative had an ending so different in theme and structure from everything before it. Mass Effect and my hypothetical Massive Effect are two different narratives with different themes and strengths, and they should have never been blended together into one story. The ending of Mass Effect 3, as a result, breaks the narrative of Mass Effect as a whole, and unfortunately, the schism is so great that the "clarification" that Bioware has suggested we will receive in Extended Cut DLC has very little chance of actually repairing any of the damage. But hey, Mass Effect was always a series about doing the impossible...maybe there's at least a glimmer of hope yet.

We'll see when the DLC is released later this summer.

Monday, April 23, 2012

Hints on Class Design in 5th Edition

I’m going to make a slight detour in my series on Mass Effect 3 to talk about the first truly interesting tidbit to come out of Wizards of the Coast’s weekly “Legends & Lore” column regarding 5th Edition (or, as they’re strangely calling it, “D&D Next”). Just today, Mike Mearls gave us the first in what will hopefully be a run of articles on general class design. This first article discusses broadly the design goals for the cleric in the next edition. What you’ll find in the article probably won’t feel very interesting at first. Clerics will be healing, using divine magic, representing their gods, and perhaps wearing heavy armor. If you’re familiar with clerics at all, all of that’s been the case for around thirty years now. We do, though, get a few interesting tidbits, and I'd like to speculate wildly about what those tidbits mean for the new edition's class design as a whole--if the world needs more of anything, that thing is lots of speculation from everyone (What, you think I forgot about it?).

The first of these tidbits has to do with divine magic as a whole, which could have some implications for the druid, as well (all quotes are, unless otherwise noted, drawn from the "Legends & Lore" article linked above):
Divine spells are rarely naked displays of power meant to smite and blast the cleric's enemies. Instead, the cleric's magic lends strength, support, and durability to both the cleric and his or her allies. Spells such as bless, cure light wounds, and neutralize poison are iconic divine spells. They lend aid to the cleric's allies and help reverse the efforts of the cleric's enemies. A cleric might help overcome an ogre berserker by healing the party's fighter, allowing the fighter to survive long enough to deal a deadly attack.
For veterans of D&D, this probably seems pretty familiar. The prevailing wisdom regarding clerics has always painted them as support characters, but there's actually been a shift in what clerics actually do (or at least, what they're best at) recently. And no, that shift didn't actually start with 4th Edition. 3rd Edition did a lot of weird things with the clerics because no one liked playing them. In 3rd Edition, clerics were solid blasters at many levels with the right domains and spell choices. Higher level spells like storm of vengeance and miracle were far from the subtle, indirect things we were used to clerics focusing on, and you could now play a cleric that did all of that stuff without having to be a specialty priest (that is, a priest your party hates because you don't heal them).

4th Edition continued the trend, blending healing with flashy damaging effects and the like as part of the standard kit of the Leader Role. The role itself was heavily influenced by the crusader class from 3rd Edition's Tome of Battle: The Book of Nine Swords, which is perhaps appropriate, given that Gygax's original inspiration for the cleric were romanticized crusaders.

Now, by and large, in 3rd Edition, most cleric spells were still subtle, but with game improvements like spontaneous healing, you didn't have to sacrifice the flashy spells to keep the subtle ones in stock. Paizo's Pathfinder Roleplaying Game continued the trend by essentially allowing clerics to heal without using spells at all, and indeed, with proper character choices, also handle things like poison and disease without them, too.

With my best speculating hat on, I wonder if specifically calling out the subtle effects that in some ways fell by the wayside means we'll be seeing something more like the cleric of old than the cleric of the last decade or so. Pre-release material for the cleric in 4th Edition highlighted the exact opposite, emphasizing the fact that you could heal while doing cool things, instead of having to waste your actions on them. That's a notable shift, I think. By way of association, this seems to suggest that the druid (assuming it makes it into the Player's Handbook) will have a spell list a lot like the one it has to day, as their spell list is still largely rather subtle, excepting the thematic spells like chain lightning and ice storm.

Next on the list, we have clerics reflecting the gods they worship:
A cleric of the god of shadows should have different abilities than a cleric of the god of storms. On an adventure, they should have different approaches that are supported by divine gifts given to them by the gods. We should expect a cleric of the god of shadows to excel at hiding—even in heavy armor—while a cleric of the storm god can call down thunder and lightning.
Of the Editions of Yore, AD&D 2nd Edition went the farthest with this concept, giving specialty priests spell lists made up only of spells appropriate for their deities. No doubt this led to a lot of strife at the table, though, as no matter what, people seem to expect clerics to be walking life batteries. A cleric of the thunder god that doesn't even have raise dead on his spell list isn't useful to a large number of adventuring groups. 3rd Edition attempted to solve that problem through Domains, which provided a small thematic list of spells, but these spells were so few in number they were often eclipsed by the frankly gargantuan general cleric spell list. As a result, most clerics ended up feeling a lot like each other, regardless of their domains.

I'm actually not too familiar with the way clerics and their gods were handled in 4th Edition, but it does seem at the least that the developers want a cleric's choice of god to have a far greater influence on his or her abilities than it did in 3rd Edition. If done properly, this may make clerics far more interesting to play, but historically, nobody's really succeeded at that yet (in D&D and its successor, anyway). Beyond all that, if clerics have too many cool things, they may end up being too powerful, which was a major problem in 3rd Edition, which gave a lot of new toys out in an attempt to make people play the healer.

If I had to hazard a guess, we're going to see something like additional domain abilities as a cleric gains levels, as we find in Pathfinder for the cleric, and also the divine oracle's mysteries. Whether or not we'll see a compartmentalized spell list I can't say from this with any confidence. I can imagine, though, a base cleric list of those subtle, iconic cleric spells mentioned above, fleshed out by spells in thematic keeping with one's deity. Considering I've tried to do that on my own (and gave up in the face of the task's immensity), I wouldn't mind seeing something like that in a new edition.

Last, and definitely actually foremost, for me, though, is this bit:
Keep in mind that these goals are guiding principles for the typical expression of a class. One of the concepts we've embraced is the idea of creating starting points, but then allowing a lot of room to maneuver for players who want to tinker with mechanics or who prefer to craft their character's story first, then find mechanics to match that story second. As I mentioned at our PAX East seminar, our battle cry is "Don't get in the way." The basic idea behind that approach is that we create a starting point, but then give players the options and tools to modify their characters as they see fit.
One of my personal problems with 4th Edition was that the strictly codified class roles and class builds and power selections got in the way of my character concepts. I'm the sort of player that likes to take a relatively flexible base and try a lot of different things with it over time. Every time I play a character of a class I've tackled before I like to explore a fighting style I haven't tried before, or focus on non-combat skills, or whatever else. Because 4th Edition wanted a set of finely tuned classes for balance, you didn't actually get a lot of options in determining how your character fought--most classes had two basic fighting styles (say, the ranger's archery or two-weapon fighting) and if you wanted a ranger with a two-handed sword, you'd probably have to play a barbarian, even if you didn't want to be an angry savage.

For me, that lack of player option really limited the potential I saw in the game, though I know it worked really well for a lot of other people. Personally, if the above bit about not getting in the way isn't just "PR speak," I'll be far more willing to check out 5th Edition when the time comes. If 4th Edition had released with a more open class system that allowed for a lot of experimentation and a wealth of options for every class, I probably could have overlooked many of the other problems I had with it. As it is, I switched to Pathfinder some time ago and haven't looked back, but a small part of me has always pined for D&D itself.

These little tidbits are the first thing that have me really thinking Wizards might have a shot at winning me back.

Tuesday, April 10, 2012

On Mass Effect 3: The Hype Machine and its Pitfalls

Previously, I discussed, in very broad strokes, the situation surrounding Mass Effect 3 and the fan-powered uprising against Bioware and EA sparked by the game's conclusion. Here, I'll be detailing the picture of the game Bioware painted in interviews with the press leading up to the game's release (as well as some of the promotional marketing material), and how the final game didn't live up to that original picture. Some (and perhaps many) fans of the game feel that they were mislead about the game they purchased, and this has played a significant part in the backlash against Mass Effect 3 and Bioware as a developer.

This post will contain spoilers for all three Mass Effect games.

The Mass Effect trilogy was groundbreaking not just for Bioware, but for gaming as a whole, as the idea of personal choices having consequences and results spanning an entire trilogy was something new in an industry lately at risk for stagnation. The series, with its various "decision points," and carrying those decisions forward to each game, has been in some ways a grand experiment in game design, and as such, Mass Effect 3, the final stage of that experiment, was perhaps the most anticipated title to ever come out of Bioware. Expectations follow naturally from all that anticipation, and after Mass Effect 2, Bioware had a monumental task ahead of them in rising to meet all that anticipation and expectation.

In terms of engaging the customer base, much of Bioware's work was already done by the first two games in the series. Judging by sales figures for the first two games, somewhere around two million fans were waiting to carry their personally crafted Commander Shepard into Mass Effect 3 to see how the story would conclude. Both Mass Effect and Mass Effect 2 offered the player a number of key decision points that could have unforeseen consequences as the series drew to a close. In Mass Effect, on the planet Virmire, you're given a chance to talk down the krogan battlemaster Wrex, who disagrees with destroying a laboratory that may hold the key to curing the genophage, a fertility plague infecting his people. Alternatively, you can shoot him and end it there. Later, faced with the impending nuke detonation, you have to make a choice to save one of two crew members: Gunnery Chief Ashley Williams or Lieutenant Kaiden Alenko. In another scenario, you're forced to decide between destroying the last queen of the rachni, an insectoid race that once threatened the galaxy, or allowing them a second chance. In Mass Effect 2, you're tasked with gaining the loyalty of your squad before tackling a seemingly impossible suicide mission, and non-loyal crew members have a high chance of not making it out alive. Along the way, you might re-write Reaper-worshipping geth heretics or destroy them, and you have to decide whether questionable research into the nature of the krogan genophage is worth saving.

These examples are only some of the major decision points in the two games. Along the way in each, you interact with a number of non-player characters, and your interactions with them are tracked by the game and determine whether or not they appear in later games in the series. You also have the opportunity to pursue romance in each game, and this comes with its own decision points: your potential partners from the first game are present only in supporting roles in the second, but you have an entire set of new "fish in the sea." Do you abandon your former partner for a newfound fling or do you remain true to them throughout the second game?

Even in Mass Effect 2, the results of your choices in the first game could be seen, such as when Wrex becomes a clan leader among the krogan if he survives your confrontation at Virmire. You meet the survivor of Ashley and Kaiden briefly. When fans felt Liara (one of the most popular romance options in the first game) had too minor of a role in Mass Effect 2 was lacking, Bioware produced a massive downloadable mission expanding on her character, and, if you choose, on your relationship with her as well. Naturally, seeing decisions from the first game carry over into the second game left fans clamoring to find out how the decisions they'd made would carry on into Mass Effect 3. In terms of creating a strong selling point for Mass Effect 3, Bioware's work was done once Mass Effect 2 was on store shelves.

Their real task, then, was delivering on the implicit promise that Mass Effect was really the fan's story, since scarcely any two play throughs would be exactly the same. Fans were somewhat apprehensive after Mass Effect 2 (as the general plot of the game remains the same, regardless of your choices) and following the release of Dragon Age II, which was viewed by many as a lackluster title. Bioware knew what they had to do to quell the fears of these devoted fans: they needed to convince the fans that their story was going to come to a magnificent conclusion, and that it was truly going to be their story.

For fans worried that choices in Mass Effect didn't have a huge impact on Mass Effect 2, Bioware sent the message that many things would have an even greater impact on Mass Effect 3. Following that, in numerous interviews in the year or so prior to Mass Effect 3's release, Bioware representatives hammered that point home: this was your story, and the ending you got would be different from the one your friend got. The fans had no need to worry, as Bioware knew exactly what they were doing. Mass Effect 3 was going to deliver, and deliver magnificently. The game was in good hands.

Except that it wasn't. Rather, it seems like those hands got all buttered up and dropped the game when it came to the conclusion. For whatever reason, the conclusion to Mass Effect 3 (and indeed, the series as a whole) failed to live up to their statements in interviews. Fans were angry. "Hundreds of hours" invested in the series, they said, were wasted. "Their choices never mattered," they complained. Was the fan dissatisfaction warranted? Had Bioware promised more than they were able to deliver? The best way to answer those questions (since Bioware has been pretty tight-lipped since the whole controversy exploded) is to take a look at those interviews, find out what they said about the game, and whether the game was what they said it would be.

Almost one year ago, in a video interview with GameInformer, Casey Hudson (executive producer for the franchise) had this to say:
“For people who are invested in these characters and the back-story of the universe and everything, all of these things come to a resolution in Mass Effect 3. And they are resolved in a way that's very different based on what you would do in those situations.”
Assuming that, in context, Hudson was referring to the game as a whole, Mass Effect 3 lived up to this statement admirably. Long-standing plot-lines, such as the problem of the krogan genophage are resolved in masterful sequences of gameplay and narrative. Key decisions from the previous games come in to play, and if, for instance, Wrex is dead in your story, his replacement is a vengeful warmonger, giving your decision on whether to cure the genophage or clandestinely sabotage the cure vastly different context than if Wrex survived all the way back in Mass Effect.

But there's one plot-line that doesn't get this kind of resolution, and that's the one that has to do with the Reapers (you know, the primary antagonists). Throughout Mass Effect and Mass Effect 2, they're depicted as unknowable, Lovecraftian forces of evil and destruction. They taunt you with their unfathomable motives (through Sovereign in the first game and Harbinger in the second). The goals and purpose of the Reapers was one of the series' greatest mysteries, and Mass Effect 3 attempts to shed some light on that mystery.

In the game's conclusion, you are introduced to an entity called the Catalyst, who explains the Reapers and their motivations in only a few lines of expository dialogue. Commander Shepard asks the Catalyst if it knows how to stop the Reapers, after which the following exchange occurs:
CATALYST: "Perhaps. I control the Reapers. They are my solution."
SHEPARD: "Solution? To what?"
CATALYST: "Chaos. The created will always rebel against their creators. But we found a way to stop that from happening, a way to restore order for the next cycle."
SHEPARD: "By wiping out organic life?"
CATALYST: "No. We harvest advanced civilizations, leaving the younger ones alone. Just as we left your people alive the last time we were here."
SHEPARD: "But you killed the rest..."
CATALYST: "We helped them ascend, so they could make way for new life, storing the old life in Reaper form."
SHEPARD: "I think we'd rather keep our own form."
CATALYST: "No, you can't. Without us to stop it, synthetics would destroy all organics. We've created the cycle so that never happens. That's the solution."
The problem is that there's nothing unfathomable in this at all, and this provides an unsatisfying resolution to the mystery of the Reapers. In five simple, short, and straight-forward lines of dialogue, the Catalyst explains to Shepard (and the player) that the Reapers are a "solution" to the problem of a technological singularity, in which artificial life can outpace and threaten organic life. This presents a whole range of problems, as it stands, as other interactions with the Reapers tell us they view organic life as a "an accident" and they don't seem to be motivated by anything resembling preservation instincts (other than self-preservation, anyway). For those fans deeply invested in the lore of the setting and in trying to solve the mystery of the Reapers, this whole explanation is ultimately empty.


Now, this post is already far longer than I thought it would be originally, so I'm only going to provide one further quote (this one also from Casey Hudson) as an example of how Bioware didn't live up to the hype with which they surrounded their game. In another interview with GameInformer given only two months before the game's release, Hudson responds to a question wondering whether the same complexity found in Mass Effect 2's ending would be found in Mass Effect 3:
"Yeah, and I’d say much more so, because we have the ability to build the endings out in a way that we don’t have to worry about eventually tying them back together somewhere. This story arc is coming to an end with this game. That means the endings can be a lot more different. At this point we’re taking into account so many decisions that you’ve made as a player and reflecting a lot of that stuff. It’s not even in any way like the traditional game endings, where you can say how many endings there are or whether you got ending A, B, or C.
It’s more like there are some really obvious things that are different and then lots and lots of smaller things, lots of things about who lives and who dies, civilizations that rose and fell, all the way down to individual characters. That becomes the state of where you left your galaxy. The endings have a lot more sophistication and variety in them. It would be interesting to see if somebody could put together a chart for that. Even with Mass Effect 2’s..." [the interviewer cuts him off here]
 Here, we see the implicit promise that all of the branching paths from the first two games result in a wide variety of endings for Mass Effect 3 and the ending for the trilogy as a whole. Because Mass Effect 2's ending gave you a great degree of control over how you tackled the final mission (by assigning squad mates to various tasks) culminating in who survives the final mission (influenced by crew member loyalty, how much you've upgraded your ship, and what assignments you give out), fans had a template through which they interpreted this statement.

The ending delivered in the game, however, doesn't coincide with Hudson's statement here at all. Shepard, after his conversation with the Catalyst (excerpted above) is presented with a choice on how to defeat the Reapers. Depending on your war assets score (essentially, how much of the galactic fleet you've gathered for the final assault on Earth), you're presented with up to three choices on how to use the anti-Reaper Crucible to win the battle. Your choice, flavored again by your total number of war assets, results in the game playing a a single cutscene with seven variations. Most noticeably, your choice determines the color of the explosion that fires from the Crucible to defeat the Reapers. Depending on your total war assets, the explosion may or may not destroy Earth as collateral damage.

After this cutscene, another plays that shows your pilot, Joker, flying your ship away from the battle and becoming stranded on a garden-like world. The Mass Relays (ancient devices that make instantaneous space travel possible) are all destroyed, potentially stranding much of the galactic fleet Earth's solar system. Galactic civilization, which depends on the Mass Relays for trade and transit, will likely collapse, and that's before taking into account all of the damage the Reapers did to the galaxy during the war that plays out throughout Mass Effect 3.

Hudson is right in that you do, in the course of the game, decide the fates of three major civilizations, but these decisions that you make have no bearing on the ultimate state of the galaxy after the game's ending. No matter what choices you make throughout all three games, the ending to the game is largely the same. Galactic civilization has crumbled, and the game's epilogue scene (depicting a grandfather telling a grandson the legend of "The Shepard") indicates that it takes as least as long as it does for the story to become a legend for galactic civilization to rebuild.

Hudson had to, at this point, have known the game's ending. Normally, games take six to eight weeks to become certified and ready for distribution, so Mass Effect 3 had to have been complete by January (roughly) if it was to make it onto store shelves in time for the March 6th 2012 release date. In an attempt to maintain hype for the game, he (perhaps unwittingly) mislead the fans into thinking they were going to get something very different from what the game actually delivered.

There are numerous other interviews and quotes from folks who worked on the game, like the lead writer, Mac Walters, and Mike Gamble, the associate producer. A handful of them are collected here on the GameFAQs message boards for Mass Effect 3 (PC version). All of them indicated that the game would take far more into account regarding all the branch points leading up to the conclusion than it actually did, and this played no small part in fostering the fan anger that lead to the entire fan movement to "Retake" Mass Effect.

There's no doubt that Bioware was attempting to do something massive with Mass Effect 3. Trying to account for so many decisions across three whole games in the game's conclusion was like standing before the sheer cliff face of Mount Improbable. Ultimately, they weren't able to deliver as well as they probably hoped in this regard. Where they truly failed, though, and sowed the seeds for this massive fan backlash against them, was in all these little quotes and sound bites that led the fans to believe Bioware had actually succeeded at their monumental task.

In the end, they probably would have been better off letting the hype machine of the two previous games do its work. Their comments on the game, contributions to the hype machine itself, did little more than add fuel to the fire when the bomb inevitably went off. Coming soon, I'll be taking a detailed look at the ending itself, which is really where most of the kindling for that fire came from before eventually tackling Bioware's response to the fan outcry, which made the whole thing explode like a "freak gasoline fight accident."