Oh, boy. Time for me to start seriously considering a Wii U. It seems Nintendo have carpet-bombed the gaming public with a new slate of announcements, enough to send our own Dale North into a tizzy.
First and strangest on the list is Shin Megami Tensei meets Fire Emblem, which as of the moment, no one knows anything much about beyond a vague teaser. Despite my being a fan of both MegaTen and Fire Emblem (the former more than the latter), I can't help but be wary without further details. After all, not every cross-franchise crossover effort has turned out well *cough*CrossEdge*cough*. But hey, it's early.
More definitively exciting, however, was the announcement of a new game from Monolith Soft. It looks to be another "Xeno-" game, and judging by the mecha fighting seen in the brief snippets of gameplay footage, one with a slightly closer relationship to the actual Xenogears/Xenosaga franchise than Xenoblade Chronicles, which astute players may remember was originally named Monado.
In first-party news, the Big N announced new features for the Miiverse social network (as well as a smartphone-based iteration), a Yoshi game from the makers of the Kirby games (go figure), yet another party game (besides the theme-park themed Wonderful 101), and an HD remake of The Legend of Zelda: Wind Waker. I wonder if that last announcement will spawn petitions by "fans" to rework Wind Waker's stylized look into something more realistic.
Photo Gallery: (3 images)
Click to zoom - browse by swipe, or use arrow keys
Get more Japanator: We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out
Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.