Marvel Rivals Has Messed Up A Major Part Of Magneto's Lore
Magneto's New Marvel Rivals Van Dyne Skin Has Messed Up His Backstory
Marvel Rivals has a pretty strong skin game, that can’t be argued. Sure, a lot of them are catered towards the gooners of the world, there’s not enough representation for black characters, and I’m still waiting for my non-gooner Black Widow legendary, but the quality of the skins released is usually quite good.
That makes the skin mistakes all the more noticeable. Over the past year there have been a few mistakes on skins, such as the word “Goot” being carved onto Groot, Captain America's freedom dong, and the mysterious case of Doctor Strange’s missing hands. However, we now have a new skin mistake, this time on Magneto’s new Van Dyne skin, and it’s pretty catastrophic for the character’s lore.
Marvel Rivals Has Goofed Up Magneto’s Number Tattoo
For those that actually know a lot about Magneto, you’ll know that the character is a Holocaust survivor, and was imprisoned in Auschwitz during World War 2. Depending on the comic or the films, it’s where Magneto awakens to his powers.
Prisoners of concentration camps during that time were often assigned a number, which would be tattooed somewhere on their bodies, with Magneto’s located on his left arm. The number — 214782 — has stayed pretty much consistent throughout the character’s history, and can be seen on a number of Magneto’s skins in Marvel Rivals.
Magneto’s number was changed briefly to 24005 in the comics to be more historically accurate, but 214782 is more commonly used.
Unfortunately, that isn’t the case for Magneto’s Van Dyne skin, as a Reddit user called Dejuna1 has spotted that the number reads 214786 instead, and the font for the number is a lot more jovial as well.
It’s not the greatest look, as the one thing you pretty much have to get right on Magneto is his Auschwitz ID number.
Some are arguing that it could be a Marvel Rivals “alternate universe” thing, but given how little Magneto’s number has changed over the years, it’s probably a mistake. It’ll get fixed like the last one, but NetEase has kind of been left with egg on its face once again.