Ryse: Son of Rome wants you to feel the weight of a gladius. It wants the clash of shields to mean something. Crytek built a Roman revenge story around a combat system that rewards rhythm over button-mashing, then buried the whole thing under a launch lineup that asked it to be a showcase rather than a game. The result is a hack-and-slash that looks magnificent and thinks small.
Trailer, via IGDBcom.
Marius Titus and the Road to Britannia
You play as Marius Titus, a Roman centurion who watches barbarian bandits murder his family. Commander Vitallion transfers him to the XIV Legion and promises vengeance. The legion sails for Britannia, where river chains nearly wreck the fleet. Marius survives a trebuchet hit, destroys the towers holding the chains, and Vitallion promotes him to the rank of centurion. From there the XIV Legion marches on York, captures British king Oswald and his daughter Boudica, and gets ordered north beyond Hadrian’s Wall to retrieve Nero’s son Commodus.
The plot runs on revenge, betrayal and divine intervention. It also runs on rails. Marius rises through the ranks because the script says so, not because the game gives you a choice in the matter.
Flow, Executions and the Rhythm Problem
Combat emphasizes “flow” — the ability to move from one kill to the next with few limitations between. Enemies are designed to break that flow. When you deal enough damage, you trigger an execution sequence: quick-time events where the game highlights enemies in colors and you press the buttons it tells you to press. Executions grant extra resources depending on how well you perform them.
The team added executions because it found the combat too difficult for players. That admission explains a lot. What was meant to be precision and timing becomes a color-coded prompt. You block to break enemy combos, you counterattack, you build long combos for rewards. The pieces are there. The tension is not.
The combat layers stack like this, in order of how much they matter:
- Flow — chaining kills without interruption, the system everything else serves
- Blocking and counterattacks — the tool for breaking enemy combos
- Execution sequences — the color-coded quick-time events that grant resources
- Kinect voice commands — calling in arrows or catapults from other characters
The Kinect That Wouldn’t Leave
Development began in 2006 as a first-person Kinect-only title for Xbox 360. Crytek gradually redesigned it into a third-person hack and slash, with Kinect serving a diminished role. You can still shout commands to other characters for arrow strikes and catapult support. It works. It also feels like a vestige of a different game that no longer exists.
The competitive multiplayer modes, developed by Ruffian Games, were cancelled. What shipped instead is a cooperative mode: waves of enemies on maps that change dynamically. It is functional. It is not the reason to play Ryse.
A Roman Legion Worth Looking At
Crytek partnered with The Imaginarium Studios for the cinematic and motion-capture technology, and it shows. The large-scale battles, where you cooperate with or command other characters against crowds of enemies, are the game’s best argument for itself. Marius’s march on York has scale. The defense of Rome in the opening has spectacle.
Then the camera pulls back and you realize the spectacle is doing the work the mechanics should be doing.
What Ryse Gets Right
The setting is the asset. An alternate Ancient Rome where Marius leads the XIV Legion against Briton rebels, captures a king, and chases a missing prince past Hadrian’s Wall — that is a campaign with a spine. Vitallion’s promise of vengeance gives the early hours momentum. The promotion to centurion after the river-chain sequence lands because you earned it in a battle that felt like a battle.
The execution system, for all its problems, does solve a real issue. New players can finish fights. The “mashing to mastery” concept — where combat rewards creativity in how you handle enemies — is a genuine idea. It just never fully arrives.
Where the Legion Falls Short
The story resolves in a place you will see coming. The game begins in medias res with Marius leading the defence of Rome and telling his life story to Emperor Nero, which means every beat between that opening and the finale is a flashback with a known endpoint. That structure drains tension from a plot that already struggles to surprise.
Multiplayer is thin. Cooperative waves on changing maps is a mode, not a community. The cancelled competitive modes leave a hole the shipped product never fills.
And the execution sequences, the mechanic Crytek added because the combat was too hard, become the combat. You are not mastering flow. You are waiting for the color prompt.
The Verdict on Ryse: Son of Rome
Ryse: Son of Rome is a gorgeous, competent, fundamentally cautious game. Development started in 2006, the game was revealed as Codename: Kingdoms at E3 2010, and it was reintroduced as Ryse: Son of Rome three years later. The seams show. The Roman setting deserves better than a revenge plot that telegraphs its ending. The combat deserves better than quick-time events dressed as depth. The cooperative mode deserves better than dynamic maps and nothing else.
What it has is craft. The motion capture, the scale of the battles, the weight of the shield — those are real. What it lacks is conviction about what kind of game it wants to be.
- A first-person Kinect title
- A third-person slasher
- A co-op wave fighter
Ryse tried on all three and committed to none.
Six point six out of ten. Worth playing for the setting and the spectacle. Not worth playing for the flow.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.
