[Thanks to Lydia Schoch for inspiring me to write this. Be sure to check out her post on fictional romances.]
You’ll notice I don’t often write romantic sub-plots in my stories. I was feeling pretty bold with 1NG4 and included one, but it’s largely implied and in the background of the larger story.
Romance is hard to write. You need characters who work on their own, and also complement one another. It’s about balance. If you get unbalanced characters, it doesn’t work—or at best, it only works as wish-fulfillment for people who want to imagine their perfectly ordinary self being married to a demigod or goddess.
And if you’re writing a story where the romance is the plot, then you also have to come up with some reason why two characters who clearly belong together aren’t. Usually social expectations are the best mechanism for doing this, to the point that it’s a cliché—A can’t marry B because it would violate all of their society’s most sacred traditions!
The problem with these sorts of stories is that too often, it becomes more about the pursuit, and in the process, one character gets reduced to nothing more than a McGuffin that the other character is trying to get. I hate that.
Here are some fictional romances I consider effective. You’ll notice that they are generally sub-plots, or at least not the sole focus of the story.
Evie Carnahan and Rick O’Connell (The Mummy)
This works because it’s pretty well-balanced—Evie’s brains and Rick’s adventuring skills make them a natural team. This is what I mean—if Evie were always a helpless damsel in distress, or Rick were always a big stupid lug, it would be dopey. But as it is, you can see why they would gravitate to one another, apart from “It’s a movie and we need a romance.”
Thomasin Yeobright and Diggory Venn (The Return of the Native, by Thomas Hardy)
When you read about Return of the Native, 90% of what you hear about is Eustacia Vye this, Damon Wildeve that. I love the book, but as far as I’m concerned, both of them can go soak their heads. Oh, wait—I guess they do. Sorry if I spoiled this 141-year-old book. Anyway, what I like about the book is Venn’s loyalty to Thomasin, and his (admittedly credulity-straining) adventures as the almost super-human “Reddleman” looking out for her.)
Miranda Lawson and Commander Shepard (Mass Effect 2-3)
Am I the only person who doesn’t hate Miranda? I might well be. Most players find her stuck-up, but I like her. Maybe part of it is that because ME 2/3 built up Commander Shepard as this awesome hero, and Miranda seems like the nearest thing to his equal in a universe that otherwise regards him as something close to a God. She saved his life, and she’s genetically engineered to be perfect, so shecan meet him on even ground. I like that. I don’t see an equivalent romantic interest for female Shepard.
But maybe it’s just my fondness for Australian accents that’s making me biased here.
Honorable Mentions: Unrequited Romances
I started out to make a list of good requited romances, because those are harder for me to write than unrequited ones. But that’s not to say that an unrequited romance can’t make for a good story, because it absolutely can. In fact, the advantage of these stories is that they have conflict inherent in them, as opposed to having to be introduced externally. So, here are some good ones:
– The Atris/Jedi Exile relationship in Knights of the Old Republic II. I talk a little about that here. Actually, KotOR II is brimming with tons of unfulfilled or outright doomed romances. Chris Avellone is great at writing those.
-Elsie Maynard and Jack Point in The Yeomen of the Guard. Just listen to this.
And now, for my favorite fictional romance…
Jane Ballard and Dan Frost (Jane Got a Gun)
Come on, you all knew this would be here. I love this movie, and a big reason why is the relationship between the two leads. The way they gradually rekindle their relationship under brutal circumstances makes for a great story, and the carefree romance of their past contrasted with the grim present is very powerful. True, a lot of what makes it work is the acting as much as anything—the same lines with lesser actors wouldn’t work as well.
I suppose that writing romance for the screen or the stage is easier than writing it in a novel. In a visual medium, putting two attractive people with great chemistry together gets you at least halfway to making the audience to buy in. On the page, though, you have to do a lot more work.
A.C. Flory wrote a brought up a good point about Theresa Gannon, the protagonist of my book, The Directorate:
“I couldn’t relate to the main character… I simply don’t see her as female… to me, Gannon could be a he just as easily as a she.”
I know exactly what she means. Honestly, I’m surprised more readers don’t mention this, because I feel the same way. There was never much of anything distinctively female about Gannon.
“Well, you’re the one who wrote it!” you are no doubt thinking. “Why didn’t you fix that, dummy?”
Good question. As a male, writing a good female character is something I find difficult, for a number of reasons.
The lazy, quick-fix approach to make a character seem distinctively gendered is to resort to stereotypes. I could have made Gannon interested in things like clothes, or shoes, or something like that. That would be stereotypically feminine.
But I hate stereotypes. It’s not that there isn’t any truth to them; most people are stereotypical in one way or another. That’s why stereotypes exist, after all. But the point of writing fiction is to give people something new and surprising. Stereotypes are, by their nature, not new and surprising but old and familiar. So in general, I think it’s good to avoid them whenever possible when you’re writing stories.
This is another way of saying that it would just feel ham-handed and rather disrespectful to have my space soldier run off to go shoe shopping. Other, more skilled writers probably could pull that off, but I couldn’t.
Writing From A Female Perspective
You don’t have to resort to stereotypes to write plausibly feminine characters, though. You can write plausible, relatable, well-rounded characters who are also distinctly women.
The big problem I see in a lot of female characters written by men is that they tend to be distinctly women first, and characters second. Usually this manifests itself in female characters being preoccupied with sex in one way or another, or else being described largely in sexual terms. I’ve read way too many female characters who seem to exist solely as sexual beings, and it gets tiresome. With Gannon, I consciously strove to avoid this. In doing so, I think I made her too non-sexual, and that makes it hard to relate to her.
The Miranda Lawson Problem
Making a character sexy is a risky proposition. If done right, it can make a character that much more memorable. But more often than not, I feel like the risk outweighs the reward, and you can end ruining a character by trying to sex them up.
Miranda Lawson is one of my favorite characters in the Mass Effect video game series. Part of it is Yvonne Strahovski’s performance (I love Australian accents, OK?), but she’s also a pretty well-written character. She’s been genetically engineered to be the “perfect woman”, and as a result, she feels a lot of pressure to be the best–pressure that sometimes makes her do morally questionable things. All in all, a really good character.
But! There’ s a major “but” here (pun not intended): for some reason, BioWare designed many of the game’s dialogue and cinematic scenes to focus, ridiculously, on her backside. Miranda wears a white catsuit, and the animators missed no opportunity to show her from the back, the most egregious example being a dialogue scene where the view “pauses” there for as long as the player wants until they choose to advance in the conversation.
BioWare defended this by saying it’s part of Miranda’s “character” that she’s genetically-engineered to be beautiful, and supposedly all this was to underscore just how sexualized she was, and how that impacts her personality.
Maybe that was the idea, but it totally didn’t come across that way. It became a running joke by Mass Effect 3 that if Miranda was around, the “camera” had to be positioned behind her. It made her seem less like a character and more like a sex object–which was too bad, because she actually is a good character, and it’s a shame she became the butt of jokes instead.
This is something that’s always bothered me, and what I took away from how Miranda is perceived is that making a character sexy is a very dangerous thing to attempt. It can very easily turn your well-crafted character into a ridiculous figure. I think this is especially true for men writing women.
Mary Sues vs. Competent Men
There’s another common criticism that I’m surprised no one has yet leveled at Gannon, but which I fully expect I’ll hear someday: that she’s a “Mary Sue”. “Mary Sues” are “idealized and seemingly perfect” characters, as Wikipedia puts it. Characters who exhibit preternatural skill in a variety of areas. Such characters seem too good to be true, and as such are hard to relate to.
The term “Mary Sue” comes from a parody of Star Trek fan fiction, so this is an issue for sci-fi writers especially. And the original Mary Sue was even a lieutenant, just like Gannon is! So, I probably am guilty of this.
Here’s my defense: there’s another stock character in fiction, referred to as the “Competent Man“. This character archetype is strongly associated with the work of science fiction author Robert Heinlein, who wrote a passage extolling the virtues of having many skills, concluding with the famous phrase, “Specialization is for insects.” His heroes tend to have a wide variety of skills.
And indeed, having many skills is rather key to becoming a hero. Incompetent characters would not be terribly effective at having heroic adventures.
As a few readers noticed, many elements of The Directorate are intended as an homage to exactly the kind of military science fiction that Heinlein pioneered. I think such stories lend themselves to having competent protagonists–after all, usually people who are or have been in military service possess a lot of training in a wide variety of skills.
Have Female Editors
One piece of advice for any men who are writing female characters: make sure you have female editors and/or beta readers. I would never have attempted to publish a novel with a female protagonist if I hadn’t known women who could critique it first. And am I ever glad they did, because their feedback improved Gannon tremendously from the first draft to the one I ultimately published.
That said, there were still times when I would overrule their objections and refuse to modify something. Because, first and foremost, Gannon had to be somebody I understood. If I didn’t do that, I would have no chance of writing her plausibly. So when somebody suggested changing the character in a way that didn’t sit right with me, I would stick with the way I wanted her. I feel it had to be this way, but it’s quite possible this made her less-relatable to everyone else.
As I’ve discussed before, my early writing has been rightly criticized for having too little description. I tried to correct this in The Directorate, and not just in describing the setting–which is essential in sci-fi–but also in how I described the appearance of the characters.
The exception is Gannon. I was deliberately vague about how she looked, because I wanted the reader to project their own image of Gannon. For most of the book, she is the proxy for the reader, and they experience the world through her eyes. My idea was that by leaving her description largely to the reader, they could create their own image of a character they found relatable. (This is something I picked up writing horror: what the reader imagines for themselves is usually way better than whatever you as the author create.)
It’s possible I made her too vaguely-defined, however; and this could make her difficult to relate to.
Creating convincing female characters is one of the biggest challenges of writing fiction for me. I try to avoid obvious pitfalls that I’ve seen a lot of male writers fall into–lengthy descriptions of their anatomy, character traits that are nothing more than clichéd stereotypes–but I’m still not entirely satisfied with what I’ve done so far. The good news is that I can tell I’m improving, and the more I write, the more I feel emboldened to experiment with characterizations, which hopefully will lead to better and more relatable characters.
I had low expectations for this game. After the fiasco of the Mass Effect 3 ending, coupled with EA’s general business practice of filling out their games with overpriced DLC and tacked-on multiplayer, I wasn’t expecting them to do much with a new entry in the series.
Besides, the original Mass Effect trilogy was a lot of fun, but also wildly uneven. The first game had a brilliant story and atmosphere, but clunky controls and emotionless characters. The second game, as re-imagined by EA, had great characters and terrific voice-acting, but an incoherent mess of a plot that was only tangentially related to the story set up by the first game. And the third game had tighter controls, better combat, and a surprisingly good crafting system—but it compounded the story errors of its predecessor tenfold, while also doing major disservices to the characters. And that was before the infamous disaster that was the game’s finale.
All in all, while I had a lot of fun with the Mass Effect trilogy, there was no avoiding the fact that it was a decidedly mixed bag—some brilliant elements; some rather shockingly bad ones. For years, I’ve said that if someone made a game that had the story and atmosphere of Mass Effect 1, the characters and voice-acting of Mass Effect 2, and the gameplay mechanics and crafting systems of Mass Effect 3, it would be a true masterpiece.
And now I know I was right. Because Mass Effect Andromeda is that game.
I don’t think I have ever been as pleasantly surprised by a game as I was by this one. I was expecting a Gears of War clone with a Mass Effect coat of paint. Instead I got an epic adventure in a sprawling galaxy, complete with likable characters, clever writing, and what just might be the best-designed combat and exploration mechanics I’ve ever seen.
You play as Ryder, a special operative who, in the early stages of the game, assumes the mantle of Pathfinder—the person tasked with setting up colonies in the Andromeda galaxy on behalf of an organization called “The Initiative”. Like Shepard in the first three Mass Effects, Ryder can be either male or female. The official canon has male Ryder’s name as “Scott”, and female Ryder’s as “Sara”, but the game allows you to choose your own first name. So, as I have traditionally done in RPGs at least since Fallout: New Vegas, I’m playing as a woman named Jane.
I have never felt such a connection with a player character before. Not with Shepard, not with the Courier, not with J.C. Denton—not even with the Jedi Exile. Something made me feel attached to my Ryder. Fryda Wolff’s terrific voice-acting is part of it, I’m sure, as she manages to at least match the great Jennifer Hale’s Commander Shepard, and perhaps even raise the bar a little higher. Tom Taylorson also does a good job in the brief but important scenes Scott has in a female Ryder playthrough. (I haven’t played the full game as Scott. I’m not sure if I ever will–to me, there can only be one Ryder.)
I can’t give a full plot summary, or this review would be longer than War and Peace. Ryder leads her team across the various worlds of Andromeda, battling the hostile species known as the Kett, making alliances with the native Angara species, setting up outposts, uncovering the remains of a bygone species known as the Remnant and in the process making the worlds of Andromeda livable for the Milky Way species—humans, turians, asari and krogan.
The first planet Ryder explores, Eos, was where I really started to grasp that Andromeda was something far more epic than I had expected. As I drove around the gorgeous, sprawling deserts, listening to Cora and Peebee banter while we fought the Kett and secured our outpost, I realized I was 10 hours in, and the save screen informed me I was only 10% of the way done with the game. For comparison, a typical playthrough of KotOR II or New Vegas (two of my all-time favorite games) takes me between 20-30 hours.
Wow, I thought. I’m sure I’ll pick up the pace soon, but I’m looking at a 40-hour game here.
Try 73 hours. And counting. The game goes on after you beat the final boss.
I have trouble being a completionist my first time through an RPG. I usually start off vowing to do all the sidequests and explore every nook and cranny, but then I get impatient and want to see what happens in the main story and wind up rushing to finish it. That didn’t happen with Andromeda—the game made me feel like I really was exploring new worlds and discovering new wonders, not just mowing down wave after wave of bad guys en route to the end.
Now, it’s true, there are tons of bad guys to be mowed down, and what a system BioWare has designed to do so. As with the other games, there are combat powers, biotic (telekinetic) powers and tech powers. All of these lead to remarkably different playstyles. As if that weren’t enough, Ryder’s weapons are highly customizable. You not only can build new ones from scratch, but you can add augmentations and mods that drastically alter their behavior. (I made all my weapons super rapid-fire laser guns, for example.)
I almost never bother with crafting systems in RPGs, but I was hooked on this one early on. After every mission, I was always rushing back to the modding table to see what new armor and weaponry I could put together.
The way you acquire new equipment is also ingenious. Throughout the game, you can scan various objects for research points that you can spend on building new items. This again reinforces the need to explore every inch of the galaxy in order to build new equipment that leads to better combat. It’s all a very nice feedback loop.
Now, again, good game mechanics don’t count for much without a good story and characters. After all, Mass Effect 3 had a good crafting system too, but nobody walked away from it thinking “I was really satisfied with that shotgun I built!”
Andromeda’s overall story, while not terribly innovative, avoids descending into utter nonsense like Mass Effect 2 and 3 so often did. And its character interactions are every bit as good as those in ME 2. There are even a few scenes that do something very rare for a video game (or even most Hollywood films, for that matter): scenes where the characters don’t say anything in response, but instead convey what they are thinking solely with the facial expressions. There was one scene where two crew members are arguing over something silly and Ryder silently facepalms in the background. This was a level of nuance that I was not expecting. For all the complaints about animation glitches (I’ll get to that), it was nice to see that degree of realism.
Each member of Ryder’s crew has a backstory, as does Ryder herself. The Ryder family history is quite interesting, and gradually piecing it together makes for a very satisfying subplot, with a great payoff during the endgame sequence.
All the backstories are slowly revealed over the course of the game, and the development of relationships works much better than in past Mass Effects because of Andromeda’s slower pace. It seems more plausible that a crew member would fall in love with you over the course of many conversations and missions together, rather than the old model of “three conversations and then bed”.
Now, as you are likely aware, the knock on Andromeda is that it’s glitchy. The animations are awkward and there are weird bugs and incomplete quests.
Yes, all of this is true. The game crashes abruptly sometimes. There are some sidequests that are broken. (One was a simple “scan three things” mission, and the game never gave me the option to scan the third.) The facial animations, while sophisticated and nuanced in concept as I described, do sometimes look a little bizarre. When talking to her AI assistant, SAM, Ryder sometimes turns her head around 180 degrees on her neck, like she’s possessed. In one cutscene, one party member was placed directly over top of another, causing them to meld together—I hadn’t seen anything so weird since the sex scene in Blade Runner 2049. And the krogan party member makes the game’s framerate slow down to a crawl if you enter combat with him. (On the flip side, this glitch also makes Ryder immortal.)
All of these are indeed annoying bugs, and if you came to Andromeda as someone used to polished AAA games, I can see it would be pretty appalling.
Let me explain why I can forgive it: my introduction to RPGs was BioWare’s Knights of the Old Republic, which I first played on the Xbox 360 in 2006. Because it was an original Xbox game that had to be made compatible with the new console, it had all kinds of slowdown issues in combat, random crashes during loading, and a host of other issues. But I enjoyed the thrill of a grand adventure across the galaxy with my rag-tag band of party members so much that I could forgive all. I’d never played anything like it before, and a few bugs here and there couldn’t interfere with the ambitious scope of the game.
Then I played Knights of the Old Republic II, by Obsidian, and again had to deal with broken quests (fuel for Telos, anyone?), glitches, and an ending that seemed (on the first playthrough) confusing and abrupt. But I loved it even more than KotOR I for the brilliance of the writing, the complexity of the characters, the brooding, ominous atmosphere, and the deep, philosophical questions at the core of the story. To this day, it remains my favorite game—perhaps even my favorite work of fiction, regardless of medium.
Since then, I’ve loved lots of games that had their technical flaws, be they bad graphics, (Deus Ex) frequent crashes (Fallout: New Vegas) bizarre texture glitches and entire rooms that didn’t load (Alpha Protocol) or just being so utterly broken they couldn’t be played without cheats. (Mask of the Betrayer) I loved them all, in spite of their technical shortcomings, because they more than made up for it with the sheer ambitiousness of their stories, the scope of their settings, and the depth of their themes.
Mass Effect Andromeda is another in that class. Its flaws are the flaws of a work so daring that it pushes the limits of the possible. Unlike the original Mass Effect trilogy, which always felt oddly constrained despite its space-faring setting, Andromeda really does shoot for the stars. It gives you a sense of freedom, of exploration and of adventure. Whereas Mass Effects 1 -3 boiled down to the story of Commander Shepard vs. the Reapers, Andromeda feels like a universe of countless stories, in which Ryder’s is but one—an important one, with significance to all the others, but still, just one. As I discussed in my KotOR II video, the interplay of galaxy-spanning concerns with deeply personal ones gives the game a truly epic feeling.
That’s another difference with the original series: unlike the Lovecraftian bleakness of the Reaper threat at the heart of Shepard’s story, Andromeda belongs to a different strain of science fiction—the optimistic sort, about life surviving in alien settings and using technology to overcome adversity. A fittingly pioneer spirit underlies all of Ryder’s adventures, and when, after long fights and lengthy treks across strange worlds, Ryder establishes a new outpost, you feel a sense of accomplishment—like you really did use your powers to help out humanity. It’s an inspiring theme; a throwback to the “space cowboys” epics of the past, when space was viewed as another frontier to be tamed and made habitable.
While the writing is not as deep, and the themes are lighter and less complex, Mass EffectAndromeda is the first game I’ve played since KotOR II that really made me feel like I was part of a universe, and even more importantly, made me think about what that really means. Like Obsidian’s epic, it makes the player ponder the meaning and the scale of their decisions, and reflect on, ultimately, humanity’s place in the cosmos. There is no higher compliment that I can pay a work of fiction.