Sequels Should Fox Introduce An X-Men Multiverse?

Ghost_Rider

Civilian
Joined
Dec 26, 2016
Messages
203
Reaction score
0
Points
11
This might be the best way to deal with 'rebooting' the X-men without damaging established brands.


They could have all the Jackman continuity X-Men films be on one Earth. Especially since McAvoy, Fassbender and J. Law likely aren't returning.


They could have Deadpool and the NEW rebooted X-Men films be on another Earth.


They could have the TV show Legion be another Earth.


And Evan Peter's Quicksilver could be the one character that carries over and crosses over with all the earths (since he's the only fan favorite from the Jackman continuity worth keeping).

5453675-6762234765-tumbl.gif



This would also make introducing a new actor as Wolverine easier, since it would be on a different Earth than the previous Jackman films.

latest
 
@Ghost_Rider
CaptainAmerica1_zps8c295f96.JPG

Introduce?

We're 2 movies deep into that
and another one coming to yet again cap the original path we were set on whilst the other two universes do w/e at different points in time.
 
or they could use wanda to do something strange
 
multiverse gets way too confusing

i also think some didn't pay attention to DOFP.it's made clear if the time travel
mission is success it will be like the last 50 years-1973-2023-never happened
and only wolverine would remember it.same thing as all the times of bishop warning the team of mutants.

I also don't get why some get this idea jackman can bever be replaced as
wolverine without reboot.both james bond and batman argurbly bigger than X-Men recasted.obviously X-23 is in logan to set up her filling wolverine's void in Deadpool/X-force.X-23 has replaced logan in comics.

of course the one who started this thread would go with deadpool in whole different contunity than any other X related film:whatever:
 
Why shouldn't it be?

The Wade Wilson in Jackman continuity was a 30-something year old man in the 1970s..

This new Wade Wilson is around the same age, but in the 2010s.


So it can't be the same continuity. Even the altering of time couldn't account for that.

Especially since the Wade from X-Men Origins must have been born long before 1973.


It's could be a different earth entirely.
 
And what are you going to do if jackman cameos in deadpool 2 or he and reynolds do deadpool/wolverine film.

Deadpool in present after origins is the same logic for apocalypse which allowes for angel,jubilee and psylocke after the time travel reboot of DOFP they can stick characters anywhere and ignore the original trilogy and first 2 wolverine films.
 
Just act like X1-X6 never happened and ignore it.

Broad Strokes Trope

Broad Strokes is a concept regarding canon where the writers pick and choose what elements of an older story they want to accept into a more recent story. It could be that the overall story is intact but the specific details are changed, or that the story is ignored but the details introduced within are still being worked with. This is most often used when parts of the official canon or even basic continuity cannot be reconciled as they stand.

It assumes that viewers understand that there are mistakes in basic canon, at least early on when the canon was still being defined. The exact degree to which this is used can vary: Sometimes it just ignores single lines that contradict later canon. Other times entire stories are declared Canon Discontinuity but still certain elements influence the new story. This can even happen with a Continuity Reboot, usually because the base story is kept intact.

Usually, this is so people can ignore things. Maybe everything sucked for a while, a Story Arc would have been alright if it wasn't for that one incident, a character gets a bit ridiculous, etc.

The adaptation doesn't explicitly contradict the primary canon. Expect some guessing about how some of these things can possibly be reconciled.

Similar strategies are used involving straight adaptations in relation to the source material. Convoluted backstories usually don't amount to much with the needs of a standalone project, so ideas and characters are jettisoned or combined to make a more cohesive narrative that follows the original in spirit. Other times following the source too closely will just fall into the Continuity Snarl that already exists in the original, thus utilizing Broad Strokes is an element of a Pragmatic Adaptation.

On a more fundamental level, the use of this trope is important for the sake of maximum creative freedom. It is surprisingly easy to limit yourself when you never expected to go beyond a pilot episode or a standalone movie. Then when fleshing out a character you find that giving them a powerful story arc requires contradicting earlier backstory or behavior to make it work.

Canon Discontinuity

When an element of canonicity is removed from the canon of its work by those who write it.

There are numerous reasons why this can happen. It can be an uncomfortable case of Old Shame, double standards, Misaimed Fandom or Unfortunate Implications for the writers. It can also happen when Fanon Discontinuity is so vehement that the writers end up agreeing and rewrite the canon. Sometimes it's just a moment or piece of writing viewed as stupid, unpopular, or simply not making sense within that universe. However, this can also happen if the work was made by a person or developer other than the franchise's original creator, and in rare cases, can also happen when they admit Creator's Apathy about canonicity. A retcon big enough, or dueling writers that are Armed with Canon can cause elements of a work, like characters, events, or episodes to be turfed out of the canon.

Sometimes the discontinuity is more subtle, such as a single line of dialogue or the specifics of an event. Besides those things, everything else is in the canon. When that happens, they're treating it in Broad Strokes. Note that this trope has to do with the creators putting something out of continuity. Obviously, this is one of the meta-causes of Alternate Universe.
 
Last edited:

Users who are viewing this thread

Back
Top
monitoring_string = "afb8e5d7348ab9e99f73cba908f10802"