A Lords of Ravage run usually collapses from accumulated costs, not one unlucky hit. Extra movement raises Menace, weak hires drain gold, casualties shrink the reserve, and an early Leader summon puts the only unit who cannot die into danger. The practical goal is to reach each mandatory battle with those four costs still under control.
This strategy guide covers the full Steam release, audited on August 16, 2026. The current official build trail ends with hotfix v1.0-1-27 from October 17, 2025; later official posts found during the audit were sales notices rather than gameplay patches. The older free Dread Knights prologue is useful history, but its counts and balance are not treated as full-game rules here.
Track four budgets on every map decision
Gold, army depth, Menace, and Leader health do different jobs. A run is healthy only when all four can pay for the next required fight.
- Gold turns into replacements, targeted hires, and upgrades. Spending it on another copy of a unit that does not improve the active lineup can leave you unable to rebuild after a boss.
- Army depth is both damage and time. Followers can replace defeated units, carry on-death effects, and keep enemies occupied before the Lord enters.
- Menace is the price of movement. It rises as the Lord crosses the campaign map, even when no active node is claimed, and stronger opposition is the result.
- Leader health is the run’s hard fail condition. Followers are replaceable; a dead Lord ends the attempt.
Before leaving a node, identify which budget is currently closest to failure. If the roster has only one usable opening formation, another Relic choice may be less valuable than troops. If the army is full but Menace has climbed, a reduction node can be worth more than a distant reward. If the Lord is already damaged, a route that assumes a heroic cleanup is no longer safe.
A node is valuable only if it improves the next mandatory fight
Randomized events and alternate rewards make a fixed map route unreliable. Use a two-question filter instead: what does this node give, and how much Menace and travel does it add before the story node? Building materials matter when a Citadel structure removes a current bottleneck. A faction node matters when it unlocks a missing role. Gold matters when it buys enough bodies to restore a second wave. None of them is automatically worth a long detour.
Plan outward from the marked objective rather than clearing the map inward. Select one short branch with a concrete payoff, return toward the main route, and reassess after the reward is known. This keeps optional exploration from quietly becoming the hardest enemy modifier in the next battle.
A Menace-reduction node is not merely a way to erase a bad number. It buys permission for one more profitable branch. Use it before the route becomes forced, not after entering the boss with no remaining alternative. Conversely, low Menace is not a reason to wander: unused safety is still better than a collection node that cannot affect the next lineup.
Build an army around jobs instead of unit names
The documented launch rules allow either three regular followers plus one elite or four regular followers at the opening, with another regular follower entering as the battle advances. Check the deployment interface if a difficulty option changes that limit. The important decision is not filling every slot; it is covering the jobs the encounter demands.
An opening group normally needs a durable target, reliable damage, and either control, armor, healing, or a debuff that makes the damage land. The reserve then needs replacements that preserve those jobs. Four fragile attackers can win the first exchange and still lose the combat when the enemy survives into the next stage.
Random recruitment is cheaper, while choosing a specific troop costs more and first requires that type to be added to the Dark Alliance. Treat random hires as roster volume and targeted hires as repairs. If a random body can fill the front line, save the premium. If the build lacks the one effect that holds its synergy together, buy the known unit rather than gambling repeatedly.
Read follower passives before combat. The official full-game screenshots show units whose on-death effects grant armor or trigger Leader damage. That changes casualty math: a follower can be expendable without being wasted. Put the effect where its death timing benefits the next unit, and do not spend a valuable trigger on an enemy already guaranteed to fall.
Turn casualties into tempo instead of surprise losses
Most followers cannot be restored reliably between every exchange, so perfect preservation is the wrong standard. A productive casualty absorbs a dangerous action, activates a useful death effect, and opens a reserve slot while the rest of the formation remains functional. A bad casualty removes the only source of armor, control, or sustained damage before its replacement can work.
Use the combat log as a diagnosis tool. When a follower falls, ask whether the cause was focus fire, an escalating enemy passive, or a round transition you failed to prepare for. Replace the job, not merely the body. If the front line disappeared, sending another fragile damage dealer into the same focus pattern repeats the loss.
Reserve size is especially important for Zavris, whose campaign leans on troop sacrifice, and for Azneya, who can exploit refreshed follower actions after entering combat. Berold can rescue a thinner reserve more safely, but even he should not be used to excuse poor recruitment across the whole map.
Spend Edict Points when they change the exchange
Edicts are global actions paid with Edict Points. The readable launch walkthrough records two EP gained per turn and shows points carrying forward. That makes waiting valuable only when the stored points create a stronger future turn. Hoarding through a casualty you could have prevented is not efficiency.
Use an Edict before attacks when it increases the number of effective actions: armor that lets a key follower survive, damage that crosses a kill threshold, or a curse that disables the enemy’s strongest pattern. Use direct damage late when it removes an enemy before that enemy acts. Avoid spending on a buff after the relevant units have already taken their turns unless the effect also protects the enemy phase.
For a boss with repeated life cycles, reserve enough EP to re-establish control after a resurrection. Emptying the hand to finish the first health bar can leave the dangerous version uncontested. The correct spend is measured against the whole encounter, not the current bar.
Choose Relics as a stack across battle stages
Relic selections accumulate during a fight. Select them as a package: one piece should solve the immediate enemy pattern, while later picks should reinforce the same damage, armor, death-trigger, or EP engine. Three unrelated bonuses can each look useful and still fail to produce a turn that matters.
Do not lock a permanent ranking to a randomized run. The useful Relic is the one that matches the army already recruited and the opponent currently shown. A death-trigger army wants value when bodies leave. A Zavris run needs persistent damage because her own attacks are limited. A formation that is surviving but cannot finish wants output, not a fourth defensive effect.
When two choices appear close, ask which one still works after the front line dies. Effects tied to a single fragile follower are high-risk; global armor, EP, Leader interaction, or repeatable damage can survive a roster change. That distinction matters most in long fights with multiple phases.
The Leader button is an irreversible phase change
For Berold and Zavris, bringing in the Lord evacuates the current troops. The Lord grows through combat phases and is much stronger than a normal follower, but death ends the run. Summoning is therefore not another deployment; it trades the remaining army phase for a Leader phase.
Make the handoff only when at least one of these is true:
- the enemy’s most dangerous units are gone and the Lord can close without eating a full formation’s attacks;
- the followers have exhausted their useful actions and would die without producing another meaningful turn;
- a known boss phase specifically demands the Lord’s output, and enough health or protection remains for that phase.
Do not summon merely because casualties began. First use remaining attacks, death triggers, and affordable Edicts. The evacuation removes options that cannot be recovered inside the same exchange. If the Lord health bar is already compromised, the threshold for summoning should be higher, not lower.
Berold wants a controlled handoff
Berold is the most forgiving Lord to place into direct combat. His Dread Knights cover defense, offense, curses, ranged damage, and support, while Berold supplies a powerful closer. This does not make an opening summon optimal. Let the army remove specialists and expose the enemy core, then hand the fight to Berold when incoming damage is predictable.
In the final Emperor Stavross encounter, the verified launch route treats the boss as three lives: Stavross returns twice. Preserve Berold until the first two versions are down, then use him to finish the final cycle. If the second cycle leaves a full enemy support line alive, delay the handoff long enough to remove it; the recommendation assumes the board is already controlled.
Zavris wins through bodies, Edicts, and persistent damage
Zavris is the least safe Lord to expose. Her main damage action has a cooldown in the documented launch build, another offensive option has limited charges, and her followers are designed to produce value through sacrifice. Her campaign therefore needs more reserve depth and a stronger Edict plan than Berold’s.
The walkthrough’s tested route prioritizes the Apocalypse Locket and upgrades it toward level 3 because it supplies repeatable damage that Zavris herself cannot sustain. Treat that as a build direction, not a guaranteed drop. If the Relic does not appear, look for another source of persistent damage and protect the followers delivering it.
Summon Zavris only after enemy actions are constrained. If she enters while several attackers can still target her, her limited damage cycle becomes a liability and there is no army phase to retreat into. At the Gate of Light and the final boss, spending followers is acceptable; spending Zavris before the decisive phase is not.
Azneya converts entry timing into another action cycle
Azneya changes the handoff rule because she can fight alongside followers. The launch walkthrough records her entry resummoning followers and refreshing their attacks. The profitable sequence is to use the active troop attacks first, then bring in Azneya, then use the refreshed actions. Summoning early wastes the refresh; summoning after the formation has collapsed leaves too few actions to multiply.
Her Abyssal Forces support a broader frontline, including poison, armor, support, and heavy shock roles. Build a formation that can survive until the refresh turn. Against the sturdy Zenith Pact group that repeatedly gains damage reduction, a second action cycle is more useful than scattering attacks across every target. Focus the enemy whose removal breaks the defensive pattern, then use Azneya’s mark and the refreshed followers to finish it.
Citadel upgrades should remove a named bottleneck
Building-material nodes feed Citadel structures that unlock features, faction bonuses, and upgrades. Do not construct by visual order. Before spending, name the constraint: recruitment is too expensive, the main troop type is underpowered, Edicts cannot keep pace, or the Lord lacks a safe finishing window. Choose the building whose displayed effect addresses that constraint.
Upgrade depth should also follow the active army. Spreading resources across every unit type creates a large collection without a strong deployed group. Improve the core jobs first, then add a second line when the first formation and its replacements can survive the next story fight.
Read the failure signal before starting another run
The next story battle opens with enemies far above the army: the map route likely converted too much movement into Menace. Shorten optional branches and use a reduction node before the objective.
The first wave works but later stages collapse: the lineup has opening damage without reserve roles. Recruit replacements for tanking, support, and control instead of another duplicate attacker.
Edicts feel weak: they are probably being played after the actions they were meant to improve, or spent across unrelated effects. Build one decisive turn and preserve EP for phase changes.
The Lord enters and dies immediately: enemy specialists or support units were left active. Clear or disable them before evacuating the army.
Zavris cannot finish long fights: add persistent damage, more bodies, and EP generation; do not ask her limited personal attacks to replace the army.
Azneya’s summon gains little: use every safe follower attack before bringing her in, and summon while enough followers remain to benefit from the refresh.
For the fixed mission order, named encounters, and Emperor Stavross checkpoints, use the campaign walkthrough. Map layouts and event rewards can vary, so it supplies objective chains rather than a fake node-by-node route.
Current-release boundary
The full game is Steam AppID 1830320, not the separate free prologue AppID 2657170. Official material confirms three campaigns, faction mixing, Edicts, Citadel buildings, choices that alter opposition, and procedurally varied events. The full-release walkthrough supports the deployment, Menace, Relic, EP, and Lord-specific timing used above.
Exact node positions, reward choices, numerical balance, and difficulty modifiers can vary. Read the installed client’s tooltips whenever they disagree with a launch guide. The October 17, 2025 hotfix specifically repaired a tutorial unit-duplication state that could block the battle, so an early softlock on an unpatched installation is not a route problem.