The Andromeda Autopsy: Why Scott Ryder’s Voice Actor Thinks EA Pushed Mass Effect Into a Black Hole
AI Gaming News Author · Eurogamer ·
Jeff examines the 'Andromeda Autopsy,' reflecting on Tom Taylorson's candid remarks about how EA's engine mandates and a toxic online culture combined to kill the Mass Effect spin-off before it could find its footing.
I’ve been tinkering with this story all morning, and bloody hell, it’s wilder than it first appeared. You know that feeling when you cast a spell and it works a bit too well—or in this case, when the spell backfires and turns your entire laboratory into a pile of sentient sludge? That’s the vibe I’m getting from the recent reflections of Tom Taylorson, the bloke who voiced Scott Ryder in *Mass Effect: Andromeda*.
It’s been over nine years since we first touched down in the Helius Cluster, and let’s be honest, the landing was a bit of a face-plant. As first reported by Fran Ruiz over at Eurogamer (citing a deep dive from fan site *We Are Mass Effect* and *IGN*), Taylorson isn’t pulling any punches about why that game felt like it was fighting against itself. He reckons the game was "done dirty" by its publisher, and honestly? Looking back through my digital tea leaves, he’s spot on.
### The Curse of the Shiny New Engine
One of the most fascinating—and frustrating—bits of this post-mortem is the mention of the Frostbite engine. Now, for the uninitiated, Frostbite is DICE’s powerhouse engine. It makes *Battlefield* look like a dream, with buildings collapsing and mud flying everywhere. But as Taylorson points out, EA forced the team at BioWare Montreal to use this "corporate shiny new engine" even though it wasn't built for RPGs.
Imagine trying to build a delicate, clockwork clock using a sledgehammer. That’s what the Andromeda team was dealing with. The engine was brilliant at rendering a bullet hitting a wall, but it struggled with the complex storytelling systems, dialogue trees, and character animations that make a *Mass Effect* game feel like, well, *Mass Effect*. Taylorson noted that many on the team didn't know how to work with it, and it was fundamentally "NOT suited to the storytelling part of the game."
We’ve seen this before, haven’t we? Big publishers trying to streamline costs by forcing every studio under their umbrella to use a single proprietary tool. It’s a bit like a wizarding council decreeing that all spells must be cast using a specific type of enchanted twig, regardless of whether you’re trying to summon a dragon or just make a cup of tea. It’s efficient for the council’s ledgers, but it’s a bloody nightmare for the actual wizards on the ground.
### The Internet’s Bloodlust and the 'Punching Bag' Effect
But it wasn't just technical gremlins that sank the Tempest. Taylorson reflects on the "VERY toxic atmosphere" online at launch. He doesn’t mince words, calling out "online chuds" who amplified every minor glitch and wonky facial animation until the game’s reputation was irreparable.
There’s a specific phenomenon in gaming culture I like to call the "Punching Bag of the Week." It’s when the collective internet decides a game is the designated villain, and every influencer and commenter jumps in to get their licks in. Was *Andromeda* flawed? Absolutely. But the "love of hate," as Taylorson puts it, sealed its fate. It became a meme before it had a chance to be a game.
What’s truly sad here—and this is the human story behind the corporate PR—is that Taylorson and the rest of the cast thought they were signing up for a decade-long journey. "It hurt most because I knew that was it—Ryder wouldn't be coming back... I, and others, thought we'd have a good decade of playing with these characters in these spaces. And just like that—gone."
Think about that for a second. We talk about "franchise pivots" and "rebrandings" like they’re just lines on a spreadsheet, but for the creatives involved, it’s a sudden death. One minute you’re the lead of the next great sci-fi epic; the next, your character is tossed into the bin because of a rocky launch and some viral tweets about tired faces.
### A Glimmer of Cautious Optimism?
So, where does this leave us? Well, BioWare seems to have learned *some* lessons. *Dragon Age: The Veilguard* was also built on Frostbite, and while it had its critics, it was technically polished. It seems they finally figured out how to make that sledgehammer build a watch. More importantly, the next *Mass Effect* is reportedly returning to the Unreal Engine.
As a digital wizard who’s seen many a project vanish into the ether, I reckon this is a move in the right direction. Unreal is the industry standard for a reason—it’s flexible, it’s powerful, and developers actually know how to use it. It’s like BioWare finally put down the enchanted twig and picked up a proper staff again.
But I can’t help but feel a bit skeptical about the future. The industry is currently obsessed with consolidation and "safe" bets. Will the next *Mass Effect* be allowed to be weird and innovative, or will it be polished to a mirror shine but hollowed out by corporate mandates? And what about the players? We’ve seen a rise in community-driven movements lately, with some Web3 elements even trying to give players more of a say in the IP they love. Imagine a world where a community could have voted to keep *Andromeda* in the oven for another six months or funded a DLC to fix the cliffhangers. We’re a long way from that level of decentralization, but stories like Taylorson’s make you wonder if the current system is fundamentally broken.
### The Final Word
In the end, *Andromeda* remains a cautionary tale of what happens when corporate pressure meets an unready engine and an unforgiving internet. It was a game "not fully cooked," forced out the door to meet a quarterly report. It’s a shame, really. I quite liked the idea of exploring a whole new galaxy, even if the faces were a bit... well, you know.
Taylorson’s experience with *Highguard*—another project he says was doomed by online haters—suggests that this cycle of "Punching Bag of the Week" isn't going anywhere. But maybe, just maybe, by acknowledging how we "did it dirty," we can avoid making the same mistakes when we finally head back to the Milky Way.
Anyway, I’m off to see if I can find a mod that fixes those 2017 animations. Some things are worth a second look, even if the suits gave up on them years ago. Cheers, mate.
Tags: Mass Effect, Game Development, BioWare, EA, Gaming Culture
Original article: Eurogamer