John Boyega isn't just a new cast member for next year's Pacific Rim Uprising -- he will play Jake Pentecost, son of the late Stacker Pentecost from the original movie. Boyega's also serving as a producer on the sequel, putting weight behind some of the creative decisions as he makes sure that the movie makes fans happy when it lands in theaters. We had a few minutes with Boyega on the red carpet at the SCAD Savannah Film Festival, and we had to ask him why Jaegars appeared to be fighting Jaegars in the first trailers that we saw for Pacific Rim Uprising. And he explained:
The Jaegar battle has been something that has caught fans' eyes from the moment that it happened in the first Pacific Rim Uprising trailer. Jaegars are towering, skyscraper-sized robots that were built to combat Kaiju -- creatures that have emerged from the seas. They shouldn't fight each other. But John Boyega states that fan demand caused the creative team behind Pacific Rim Uprising to put in scenes that pit the robots against each other, and it sounds like they figured out a way to make it happen.
Earlier this year, at New York Comic-Con, Pacific Rim Uprising director Steven S. DeKnight gave a little more insight into the Jaegar in-fighting, telling CinemaBlend:
And John Boyega, who was at the Savannah Film Festival with his searing drama Detroit, says that this "nefarious" activity is integral to the plot, and will work to move it forward. See the battle in question in the trailer below:
We will have all of the answers as to HOW the Kaiju could return, and where our greatest battles will occur, when Pacific Rim Uprising opens in theaters on March 23, 2018. Until then, hit up our Preview Page for the movie, where we have a lot of stories generated from our recent visit to the movie's set. And of course, there's always our 2018 Movie Release Calendar, which has every movie opening next year, for you to brush up on.
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.