One-Piece-Burning-Blood.png

Are you a One Piece fan? Are you a beat-em-up fan? Well what if I told you that Bandai Namco Entertainment have announced some new details for their upcoming One Piece beat-em-up One Piece: Burning Blood, would you be interested? Then read on!

The game was originally announced back in September and should be arriving on consoles in early 2016, still a little bit away but I’m sure there’s plenty to keep you going until then. We’ve all got a backlog we need to work on.

So far Monkey D. Luffy, Sabo, Ace (woo!), Bartolomeo, Ener, Crocodile, have been announced as being part of the roster but the newest announcement is the Smoker will be part of that! You can expect more characters to be announced as time goes on. Personally, I’m holding out for Chopper, Zoro and Shanks to be announced.

The game has several features that will add a level of strategy to your run of the mill fighting game. Have you ever hoped that you’d get to see Luffy, Ace and maybe Sabo fight side by side? Well, I’m here to tell you that this game makes that a reality! Players can create a team of 3 and swap them out to create a tactical advantage!

There’s certain characters that can use special Logia moves for unique abilities, which will allow players to burn through enemies or move faster that lightning! Logia fruits also give you the use of Logia Guard which can make some characters untouchable by physical attacks for a short time. However, you can use Haki Blow as a counter to this, so don’t worry about anyone spamming the guard move.

Last but by no means least, as in the manga, Devil Fruits will be making an appearance which is the source of unique massive Special Attacks and Reinforced Special Attacks.

I’ve mentioned this before but One Piece: Burning Blood is due to be released in Europe, Middle-East, Africa and Australasia at some point in 2016.

I know you’ve scrolled this far and expecting to see a trailer and I’m not one to disappoint so here you go:

For privacy reasons YouTube needs your permission to be loaded.

//