War Of The Roses Series

The Brutal Reality of War Of The Roses

The game shipped in early access in February 2012 before the proper March release, and it was immediately clear it was trying to do something most medieval combat games had never attempted seriously: large-scale melee focused entirely on human versus human encounters without leaning on siege mechanics or ranged archer dominance. You picked a faction, chose a weapon class, and got thrown into matches where the objective was usually capturing banners and holding key zones. Simple enough on paper. The actual execution revealed itself pretty quickly. If you are looking for the game itself, it is available through the Steam store at a very low price point now that it has been abandoned by its publishers. EA acquired Codemasters, and the multiplayer infrastructure for this particular title was quietly shut down rather than maintained. What that means in practice is that there is no active community to matchmake with. Any download you find will be a standalone offline experience. Before you go hunting for cracked versions or old installers, understand that the servers are gone. What remains is a broken-but-fascinating combat system and a single-player mode that was patched into existence late in development. I spent about forty hours in the beta and early launch window trying to learn the parry timing across different weapon classes. The game uses a stamina-based block and counter system that rewards reading opponent animations rather than spamming attacks. Once you commit to a shield bash or a grab throw, you are locked into a recovery animation that leaves you vulnerable for roughly two seconds if your opponent escapes. This mechanic is not advertised anywhere in the tutorial. Players who figured this out from trial and error gained a significant edge in duels against newcomers who just button-mashed.

There is a specific interaction with the spear class that most people miss. When you hold a spear in a confined hallway or doorway and face the correct direction, the weapon gain a reach advantage that reduces the effectiveness of sword users trying to close the distance. I noticed this during one of the last open beta sessions before the official release, tested it in a few custom matches, and used it consistently in the early ranked lobbies. It works because the AI pathfinding for closing distance does not properly account for the extended hitbox of the weapon when stationary. This was never patched out, which tells you something about the state of post-launch support for the title.

What actually works and what does not

The core combat loop is deceptively deep. Each faction carries distinct visual and mechanical flavor. The Lancastrians have more aggressive light weapons. The Yorkists lean toward heavier strikes with longer windups. The Talbot faction, which came later through updates, introduced a balanced middle-ground approach that some players found too generic. None of this matters much if you do not understand the banner capture system, which is the primary objective in most multiplayer modes. Capturing a banner requires standing near it for several seconds while enemies attack you. You can interrupt an enemy capture by damaging them, but you cannot kill them to stop the capture. This design choice creates an interesting risk-reward dynamic where area denial is more valuable than outright killing. In practice, I found that positioning yourself between the banner and the most likely approach vectors mattered more than raw combat skill. A player with mediocre weapons who holds the right choke point consistently outperforms a skilled duelist running around looking for glory. The single-player campaign that eventually shipped is serviceable but flawed. It covers key historical moments from the Wars of the Roses period, but the narrative delivery is stiff and the encounter design often forces you into situations where the AI opponents overwhelm you through sheer numbers rather than tactical challenge. I completed it on the lowest difficulty because the AI on higher settings uses spawn points that make fair engagement nearly impossible. The game was clearly designed for multiplayer first, and the campaign felt like an afterthought that received patchy development time.

Common problems and edge cases

One issue that surfaced repeatedly during the launch window involved the game crashing to desktop when switching weapon classes during a match. This was more prevalent on systems with dual-core processors, though it affected some quad-core setups as well. The workaround was to close unnecessary background applications and ensure the game was set to use a single monitor rather than spanning multiple displays. I also found that disabling hardware acceleration in the graphics settings reduced crash frequency on certain NVIDIA driver versions from the 2012 era. Another problem involves the AI behavior in team-based modes. Friendly units will sometimes stand completely still during banner captures instead of defending you, which turns what should be a coordinated defense into a one-on-one brawl. This is not a setting you can adjust. It is a hardcoded behavior that stems from how the pathfinding system handles the capture objective state. Your only real option is to position yourself as a roaming defender rather than relying on AI support, which changes the entire dynamic of how you approach each round.

Whether it is worth your time now

War of the Roses is a curious artifact. The combat system has genuine depth that most fast-paced fighting games from the same period do not match. Reading animations, managing stamina, and controlling space are all mechanically sound ideas. The problem is that the game exists in a hollowed-out state. There are no living servers. There are no active leaderboards or content updates. The single-player mode is a time capsule of unfinished ambitions. If you find it on sale for less than five dollars and you have a passing interest in experimental medieval combat mechanics, it is worth a quick look. The weapon feel is satisfying once you invest time learning the input timings. But do not expect a complete package. The multiplayer that defined the experience is absent, and the game's technical issues from 2012 still persist in the current executable. Consider it a historical curiosity rather than a functional product, and adjust your expectations accordingly. The single-player campaign can be completed in roughly eight to ten hours on a relaxed pace, and that is probably the most you will get out of it unless you host local matches with friends willing to run a private server workaround.