#War of the vikings full

As infuriating as the control scheme is, War of the Vikings offers a very authentic-feeling battleground experience.

Given the problems with attacking, it is immensely gratifying to slay a foe in an extended exchange of strikes and parries.

#War of the vikings full

If you want to go full Viking, youвЂ™ll be charging headlong into battle, swinging your weapon of choice wildly around you, trying desperately not to get deducted XP for friendly fire. Never let it be said that itвЂ™s anything less than intense in a mayhem-and-chaos sort of way. War of the Vikings isnвЂ™t all bad, though. Without advanced technical knowledge, itвЂ™s impossible to say what caused these multi-second freeze-ups, but it was common enough on a computer that can run TESO on Ultra at 80-100 fps to warrant mentioning, since that doesnвЂ™t bode well for older PCs. Granted, this may be out of the developerвЂ™s control, but it worth mentioning since you really canвЂ™t escape it in a multiplayer-only game.ДЄside from the design choices, there are some technical issues with War of the Vikings which make for awkward system lag on even the beastliest of rigs at seemingly random intervals during play. You can save yourself some trouble and offense by simply ignoring chat entirely, as youвЂ™ll likely never see anything of any value come out of it. YouвЂ™ll see a deluge of racial, homophobic, and misogynistic chatter, punctuated on occasion with inane remarks about вЂњnoob axes.вЂќ YouвЂ™ll likely be chastised for running too eagerly into combat one second, then again moments later for being a coward. The community is reminiscent of what youвЂ™d find in an overly competitive match of League of Legends or DOTA 2. Unfortunately, the mechanics arenвЂ™t the only thing wrong with War of the Vikings. This is the crux of the obscene learning curve to succeed at melee combat in War of the Vikings. Of course, both attacking and parrying are things you can eventually acclimate to, but it begs the question of why this mechanic would be implemented at all. The mechanic is the same for swinging and parrying, so you have to look away from your assailant in order to activate your parry, which in turn makes you fail to parry the blow more often than not. Speaking of flailing, you can, in theory, parry your opponentвЂ™s strikes, too. Obviously, when youвЂ™re looking away from your target, youвЂ™re probably not going to hit them, so youвЂ™ll try to swing your target back into your sights during the animation, which leads to a whole lot of wild flailing. Mouselook is always on in War of the Vikings, so making an attack necessitates you look away from your target when you swipe left or right to launch the attack. When it comes time to swing, however, you have to swipe the mouse either left, right to swing from that direction. Click and hold the left mouse button to charge up your attack is a reasonable enough start. The first thing that struck me as being horribly awry was how you swing your weapon. ThatвЂ™s not to say youвЂ™ll be proficient with the basic controls immediately, however, as the learning curve is much steeper than you might expect thanks to a seemingly senseless control scheme. Once youвЂ™ve got the basic controls, youвЂ™re off to the multiplayer mayhem. The only single player portion is the tutorial where you learn to swing a sword and parry an attack. The description вЂњMultiplayer Close Quarter CombatвЂќ sums up the nature of War of the Vikings quite well for the most part, assuming youвЂ™re willing to overlook the seemingly overpowered bow and arrow, and various thrown weapons. ItвЂ™s quite exciting for such a simple sounding premise, but many core design decisions are working against the well being of War of the Vikings.

You play on a team of Vikings or Saxons, running around, trying to hack and slash your enemies to death before they hack and slash you to death. If youвЂ™re not familiar with the concept, imagine Call of Duty: Medieval Warfare. I never played 2012вЂ™s War of the Roses, so FatsharkвЂ™s follow-up, War of the Vikings, took me a bit my surprise.