On the game’s first anniversary, Stumblebee explores the lead-up and reception of Marvel vs. Capcom: Infinite

By on September 19, 2018 at 6:00 pm
mvci_captain_marvel_cg

Mahvel came back, but why did it fall to the wayside again so quickly?

Today is the first anniversary of the release of Marvel vs. Capcom: Infinite, Capcom’s latest addition to the Marvel Vs. series — and a game that proved divisive and disappointing to many fighting game fans. For all the things that Marvel vs. Capcom: Infinite did well, it was overshadowed by the absence of classic characters, troubled PR and presentation, and the problematic Battle for the Stones circuit. When MvC:I didn’t make it to the main stage for Evo 2018, much of the community took that as the official sign the game had failed; as untrue as that is, it seems to accurately reflect the predominant attitude toward Marvel vs. Capcom: Infinite. However, the Evo side tournament still brought in 128 players, and despite the rhetoric that the game is “dead”, it still has a dedicated community that enjoys playing it.

To mark today’s occasion, Stumblebee has prepared this look back at the launch and reception of Marvel vs. Capcom: Infinite, asking the question: “Why Did It Bomb?” The video explores the early reveals for the title, the big fails during the lead-up (see: Chun-Li’s face, “functions”), and the course the game took after launch, alongside its blockbuster competitor Dragon Ball FighterZ. Though Stumblebee’s video title is harsh, he’s a professed fan of the series, and actually thinks Marvel vs. Capcom: Infinite got more of a raw deal than it deserved. Check it out below (some language is NSFW).

Source: Stumblebee


RELATED POSTS

Shoryuken review: Marvel vs. Capcom: Infinite is still a true Marvel vs. Capcom game

Marvel vs. Capcom: Infinite’s community comes together for their second community combo video

Sound designer Mike Thal analyzes Marvel vs. Capcom: Infinite’s game audio

Shoryuken.com Editor-in-Chief. Street Fighterin' since there was only a "II" in the title.