David Brevik suffered a public humiliation at the hands of Jay Wilson, when the lead designer of Diablo III said to “f*ck that loser” in a public Facebook post. Well, after Jay Wilson got a good lambasting from the Diablo community and apologized to Brevik, it's now become apparent that Brevik 's upcoming ARPG, Marvel Heroes was always destined to be the real Diablo III and the outrage from Wilson has worked as a wonderful platform to help Brevik sell his new game.
According to Now Gamer, Brevik stated that...
That's a cool thing to know. The upcoming MMO, Marvel Heroes, will be an isometric action-RPG that focuses on looting and grinding just like Diablo, but the main difference is that there will be a slightly stronger focus on multiplayer and potentially story. But the real kicker is that gamers will finally get a game similar to what the original vision of Diablo III (gameplay wise) would have been had it been designed by Blizzard North.
Brevik further stated that...
This is a reiteration of what was mentioned before, how Marvel Heroes was going to be the spiritual successor to Diablo II. This is mostly due to the fact that die-hard Diablo fanboys feel as if Diablo III was such a farcry from what helped establish the series as a respectable ARPG series.
One of the neat things they have in store for Marvel Heroes, and something that was scratched from Diablo III was something called BattleNet Town, a hub of sorts which is now a standard in most instanced-based MMOs.
Brevik talked a little bit about this feature, saying...
Well hopefully it all works out well for Marvel Heroes. It would be a lie to say that the game hasn't picked up some sort of steam from the backlash against Diablo III, so maybe Brevik and crew will make good on the renewed interest in this ARPG and deliver. Otherwise, it could be Hellgate: London all over again.
Staff Writer at CinemaBlend.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.