Here we go again. A social media post has dragged one of gaming's oldest grudges back into the spotlight, and Metal Gear fans are not letting it go quietly.
The complaint is familiar: Hideo Kojima swapping out David Hayter, the voice behind Solid Snake and Big Boss, for Hollywood star Kiefer Sutherland in Metal Gear Solid 5: The Phantom Pain. The post laid into Kojima for discarding a longtime collaborator in favor of Tinseltown shine, and plenty of players nodded along.
Hayter's run started with the original Metal Gear Solid in 1998 and carried through Metal Gear Solid 2: Sons of Liberty, Metal Gear Solid 3: Snake Eater, and Metal Gear Solid: Peace Walker. That gravelly rasp basically became the character's signature.
Then came 2015's The Phantom Pain, and with it Sutherland. The switch sparked a massive backlash at the time, and Hayter didn't sugarcoat it. He said he wasn't even given the courtesy of a heads-up, called the whole thing humiliating, admitted he held no particular fondness for Kojima, and refused to play The Phantom Pain for a while. Fans lined up behind him, arguing the recasting betrayed what the series meant to them.
But time heals. In 2025, Hayter finally played through The Phantom Pain and changed his tune, praising its gameplay as the best in the series and saying publicly that everything was water under the bridge. That same year, he returned to voice Snake in Metal Gear Solid 3: Remake. The man himself has made peace, yet this old post still managed to yank everyone's memories right back to the recasting mess.
It's a reminder of how personal these casting calls can feel. To a lot of players, Hayter wasn't just a voice, he was Snake. So when the swap happened, it landed less like a business decision and more like a betrayal.
Even with Hayter moving on, the fandom clearly hasn't fully closed the book. Some wounds in gaming just take a lot longer to scar over.
Where do you stand? Was Kojima right to bring in Sutherland, or should Hayter have kept the role for good? Sound off below.
Comments (0)
Log in to join the discussion
Log InNo comments yet