Home / Columns / True Story: Alec Baldwin Almost Played The Villain In A Recent Marvel Film…But Which One?
Alec-Baldwin-Marvel-Movie-True-Story

True Story: Alec Baldwin Almost Played The Villain In A Recent Marvel Film…But Which One?

Say what you will about Alec Baldwin as a person (and trust me…you can say a lot of things), but I’ve always enjoyed his work as an actor.  He has his natural charisma and energy that makes him suited for some wonderful roles, and I’m glad recent ventures like The Departed and 30 Rock have brought Baldwin back into the limelight as of late (among other, less positive things).  So whenever I hear that Baldwin is up for a role in something, I still get excited…even if ultimately he didn’t get the part.  Like in today’s True Story for instance, which tells the tale of Alec Baldwin telling the tale of the time he almost took a bad guy role in a recent Marvel movie.  Which movie, you ask?  Well we’ll ask ourselves the same question right after the jump.

But first, some background details.  Alec Baldwin was chatting with Howard Stern when he dropped this tantalizing piece of trivia.  Stern asked him flat out if he ever had been contacted to play a bad guy in a comic book film, to which Baldwin replied:

“I have, but I won’t mention which one. I don’t want to undo somebody because they hired someone else to do it. But they asked me to play a villain in one of these Marvel Comics movies.  I wasn’t available…they wanted me to work at a certain time. And because of my wife’s pregnancy, I had to turn down two films this summer that I wanted to do.” 

So the big question, of course, is just which Marvel role Baldwin turned down.  As Cinema Blend points out, Baldwin’s wife has been pregnant for about six months, so there’s tons of projects Baldwin could be referring to—Thor: The Dark World, The Amazing Spider-Man 2, Guardians of the Galaxy, X-Men: Days of Future Past, or Captain America: The Winter Soldier.  Off the bat I can’t imagine him having a role in Guardians or Thor, so let’s just strike those away.  That leaves The Amazing Spider-Man 2, Captain America: The Winter Soldier, and X-Men: Days of Future Past…which I could easily see him having a place in any.

Alec-Baldwin-Marvel-Movie

For The Amazing Spider-Man 2, it could have been the role of Norman Osborne (now occupied by Chris Cooper).  For X-Men: Days of Future Past, it could have been evil businessman Trask (now played by Peter Dinklage).  And for Captain America: The Winter Soldier, it could have been the S.H.I.E.L.D. agent role given to Robert Redford (yeah it’s not official that he’s playing a villain, but come on—you don’t cast Redford and give him a bit part as an agent).  In my mind though, it was most likely the role of Trask in X-Men: Days of Future Past that Baldwin was forced to turn down…which is a damn shame indeed, since he would have been spectacular in the role.  But for what it’s worth, he would have been spectacular in ANY villain role.  He already did a good job in Clerks: The Animated Series for god’s sakes!  Leonardo Leonardo 4evur.

-Matthew

Enjoyed this article? Make sure to follow us on Twitter or like us on Facebook to keep up with even more Geek Binge related goodness! And if you want Geek Binge fun in a timely, convenient fashion, make sure to subscribe to our RSS Feed or Daily Email Newsletter!

About Matthew Legarreta

Matthew Legarreta is the Editor-in-Chief of Geek Binge. A big ol' ball of movie, TV, and video game loving flesh, Matthew started up Geek Binge in the Fall of 2012 to convince himself that he's doing something with his life. He isn't. Matthew also loves writing about himself in the third person, because it makes him feel important or something.

Cool Stuff From Other Cool Sites