For Honor – What the Development Team Learned From the Closed Alpha

For Honor’s recent closed alpha yielded glorious victories, heartbreaking defeats, and a mountain of feedback. Members of the development team have been poring over all the information gathered during the long weekend and they’re already hard at work refining, balancing, and readying For Honor for the next step. In the video below, producer Stephane Cardin shares statistics on player behavior, including average play time, matchmaking speed, and more. He also elaborates on what the strongest lessons were from the Alpha and how the team is addressing these issues.

What else did the team learn? Check out the For Honor infographic below to see the most popular heroes and modes, as well as average match duration per mode and other stats:

For more on For Honor, check out our previous coverage:

For Honor – Up Close With Duel Mode

For Honor – 6 Essential Battlefield Tactics

For Honor – Viking Raider Takes Center Stage in Campaign Walkthrough

For Honor

For Honor

Release date — February 14, 2017
Developer — Ubisoft Montreal
Enter the chaos of a raging war as a bold knight, brutal viking, or mysterious samurai, three of the greatest warrior legacies. For Honor is a fast-paced, competitive experience mixing skill, strategy, and team play with visceral melee combat.

The Art of Battle, For Honor’s innovative control system, puts you in total control of your heroes, each with distinct skills and weapons, as you fight for land, glory, and honor. As a skilled warrior on an intense, believable battleground, you annihilate all soldiers, archers, and opposing heroes who stand in your way.

ESRB Rating: MATURE with Blood and Gore, Intense Violence
The Author

Chris Watters loves to captain tall ships, drive motorbikes off cliffs, and fight cassowaries. Video games have made his life a lot more manageable. He is a former host and writer at GameSpot, the author of The Gamer's Bucket List, and now a Communications Specialist for Ubisoft. Follow him on Twitter at @CTWatters.