When last we saw Sebastian Stan in a Marvel Cinematic Universe film, he was being placed into cryogenic sleep by his best friend and former colleague, Steve Rogers (Chris Evans), in the end-credits sequence for Captain America: Civil War. With Bucky on ice, we weren't sure exactly WHEN he'd return to action, even though he had at least three movies where his presence would make sense. Well, when we spoke with Sebastian Stan in Toronto on behalf of his dark comedy I, Tonya, he confirmed that he's suiting up for the mysterious Avengers 4, though plot details were on ice, as well. Stan told CinemaBlend:
A lack of a full script has become the norm, not just at Marvel but on most major properties, in an effort to prevent leaks. While Mark Hamill will tell fascinating stories about reading the full script for Star Wars: The Force Awakens, I highly doubt that Daisy Ridley or John Boyega can carry around full scripts for, say, Star Wars: The Last Jedi. And as Sebastian Stan notes, he is kept on a need to know basis, and only reads the parts that his character, The Winter Soldier, is involved in. When I asked him if that means he feels like he's lacking ownership over the direction of the character, he emphasized that it's the trust he has in his creative team that means he doesn't need full ownership, stating:
Not that we are trying to leapfrog past Avengers: Infinity War, but we're mildly fascinated with Avengers 4, for so many reasons. It doesn't have a title, and we have been told that the title it likely will carry is such a spoiler, Marvel can't reveal it yet. Also, it arrives in theaters one year after Infinity War... when in the past we have had to wait for full Avengers stories to come out. What type of story will it tell? Who will be around to tell it? Speculate in the comments section below, and use our Upcoming Marvel Movies feature to stay up to date on every MCU event on our horizon.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.