I like to be mister optimism when it comes to games...even games that are slated for mobile and browser based platforms. But I've had an extremely hard time believing that the sixth entry in the Breath of Fire series is going to deliver an experience that will make me proud, once again, of Capcom's beloved role-playing franchise.
Recently, a bevy of new screens have hit the Internets showcasing a little combat, some village building, and some quite lovely -- and adorable -- concept art. Not enough to gather a full impression on, but hey it could be always look worse.
On top of the new screens, first details of the game's story and gameplay have emerged. Thanks to a breakdown over at NeoGAF, we now know combat will feature: no complex command menus, fast and intuitive touch controls, timing based combos, and party members will be AI driven.
Additionally, the game will ditch the predetermined hero Ryu -- a staple of every other past entry -- to allow players to create and customize their own character.
As for story, what's there again does hint that maybe all isn't lost with Breath of Fire 6. A thousand years has passed since someone last held the power of the dragon. There's now a new evil empire -- the Schwarz Empire -- that attacks the main character's village, and -- from what I can only assume -- typical RPG melodrama ensues.
Who knows, maybe this will all turn out quite well. Then again maybe this will be a microtransaction nightmare. Though as it stands right now the game is only destined to grace Japanese shores.
Get more destructoid: 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.