Unlike Reed Richards and Ben Grimm’s World War II military service, it is a lot harder to ignore Magneto’s background in World War II, since all of the terrible things that had happened to him during the Holocaust because he was Jewish are a huge part of his characterization, ever since he first revealed his background in Uncanny X-Men #150 (by Chris Claremont, Dave Cockrum and Joe Rubinstein)…

Now, Professor Xavier’s background in the Korean War had obviously could be written out if need be…

Uncanny X Men
X men 12

Okay, so we have established out that they’re both pretty firmly entrenched in the past, so how, then, do you reconcile this with the fact that they would each have to be in their mid-to-late 80s at the absolutely very earliest?

Uncanny X-Men #167

uncanny-x-men-167-1

With Xavier, it was when he was taken over by a Brood Queen in Uncanny X-Men #167 (by Claremont, Paul Smith and Bob Wiacek)…

uncanny-x-men-167-2

They stopped the Brood Queen, but his body was now destroyed…so they just cloned him another one!

Defenders#16

defenders-16-1
defenders-16-2

Meanwhile, in Defenders #16 (by Len Wein, Sal Buscema and Mike Esposito), Magneto and his Brotherhood of the Evil Mutants had been trying to manipulate an “ultimate mutant,” but instead, Magneto and his cronies were reduced to infancy..

 

Magneto returned in X-Men #104!

x-men-104-1
x-men-104-2

And we have learned that he was re-aged to adulthood…

Obviously, he was aged to a younger age than before.

Source: Cbr

Facebook comments:

Leave a Reply

Adcodes and Instructions provided for: animatedtimes.com ============================================== animatedtimes.com ============================================== ======================================== SID 15564 EDGE_Animatedtimes.com ======================================== PLACE THIS CODE BEFORE THE TAG Edge Ad Code: EDGE_Animatedtimes.com ======================================== ======================================== ***EDGE Trafficking Instructions:*** ======================================== EDGE ad code should be placed directly on the site within the body at the end of the page. The default EDGE configuration is described below. If you have requested a custom configuration, please disregard default settings below. EDGE can be trafficked through ad servers via javascript tags, 1x1 javascript pixel, or DFP/GPT synchronous tag. In DFP, make sure that SafeFrame is disabled (it is automatically enabled by default), otherwise the tags will not work properly. For DFP/GPT, see this link to "Traffic and serve out-of-page creatives": https://support.google.com/dfp_premium/answer/1154352?hl=en ======================================== ======================================== ***EDGE Default Configuration:*** ======================================== SLIDER - Rails w/ Content Detect and Footer w/ Ad Detect: - Serve rail placements (160x600, 300x250 and 300x600) for Desktop when open space is available. All sizes are located at the bottom of the window by default. - When rail space is not available, serve 728x90 or 970x90 footer. With Ad Detect enabled for desktop footers, a 728x90 or 970x90 will not be served when it covers a standard IAB format (728x90, 300x250, 160x600, and/or 300x600). ======================================== ======================================== ***EDGE Default Settings:*** ======================================== - Device Targeting: Desktop, Tablet, and Mobile Phone - 100/24 Frequency cap - Minimum Time between EDGE sliders: 3 seconds is the minimum time allowed; may be increased ========================================