Thor 4 hasn’t been officially announced yet, but comments from stars Chris Hemsworth and Tessa Thompson suggests it’s only a matter of time before the God of Thunder gets a new standalone movie. The hero’s been through a “Hela” of a lot recently, though, so what fresh turmoil could another film throw at him? Well, we might now have a clue as We Got This Covered has learned which comic book storyline Marvel is entertaining the idea of adapting for Thor 4.
According to our source, the movie will be based on the “Siege” comic book arc. The brief synopsis we’ve been given of the MCU take on the storyline is that it’ll involve humans wanting to take over New Asgard, located in Norway, and its advanced tech. Given that there’s no script just yet though, we’re told that all of these are just ideas at this stage and things can always change.
Still, this is pretty unexpected in some ways as Thor left Earth behind at the end of Avengers: Endgame, suggesting his next adventure in the MCU would be a cosmic one. So, it’d be a surprise if his fourth solo movie took him back down to Terra Firma. That being said, there may be a bigger reason as to why “Siege” would be the perfect story to adapt in the film.
Though this sounds like a very different version of the comic book arc, the use of the “Siege” storyline in Thor 4 could be yet another piece of evidence that points to the “Dark Reign” event coming in Phase Four. In the source material, it’s Norman Osborn who’s behind the attack on Asgard, as this took place during his leadership of the Dark Avengers and HAMMER (his replacement for S.H.I.E.L.D.). After all, Osborn is rumored to be the big bad of the next phase, so the villain could very well be involved in the movie somehow.
According to other sources, Thor 4 is a while off, but the God of Thunder could show up in Guardians of the Galaxy Vol. 3 first. While we await the Asgardian’s return though, let us know if you like the sounds of this storyline in the comments section below.
from Movies – We Got This Covered https://ift.tt/2xiFeCR
0 comments: