Current Heroes

Ruadh Build Guide: Weapons, Clans & Bosses

A current Ruadh build guide covering his Banshee unlock, hammer role, weapons, Clan choices, movement, solo boss tactics and evidence limits.

Updated Patch: 0.14.58630

Ruadh Stonecrusher

Role
Hammer frontliner and support
Difficulty
Not officially rated
Unlock
Defeat the Banshee
Ruadh combines shield and armor pressure with displacement and healing in his official reveal, making him the clearest current fit for players who want a heavy front-line support style.

Quick summary

  • Current roster: Ruadh is one of the three playable Early Access Heroes.
  • Unlock: defeat Iseult, the Banshee, according to version 0.8.57278.
  • Weapon: a massive hammer in the official Ruadh reveal.
  • Official role language: shield breaking, armor shattering, knockback and ally healing.
  • Community reports favor his reach and area pressure but repeatedly flag slow attacks, movement and solo-boss recovery.
  • The build approaches below are candidates for testing, not current-build tier-list claims.

Unlock Ruadh

  1. 1

    Continue beyond Gilles

    Complete Act 1 and progress through the next generated objective sequence toward Iseult, the Banshee.
  2. 2

    Use the current Banshee rule

    In version 0.11, damage affects the stun bar more, parries affect it less and the bar decays more slowly.
  3. 3

    Defeat the Banshee

    Paper Cult's official 0.8 note ties Ruadh's unlock directly to this victory.
  4. 4

    Verify the roster state

    Check Hero selection after the encounter transition. If Ruadh remains locked, record the version and Steam branch before reporting a bug.

Officially described combat role

Ruadh actions described in the official reveal
FunctionReveal descriptionPractical interpretation
Shield pressureSmashes through shieldsA natural candidate for Block-bar pressure
Armor pressureShatters armorUse live icons and enemy state to confirm the applicable action
ControlKnocks enemies awayCreates space, but no universal knockback distance is claimed
SupportKeeps allies alive with powerful healingSupports co-op and army survival without proving an exact heal value

Two evidence-labeled Ruadh build approaches

Ruadh candidate builds: what to try and when they fail
ApproachPriorities to testBest-fit scenarioFailure conditionsEvidence status
Crowd-control / co-op supportBlock and armor pressure, area control, healing access, then movement or dodge recovery; Vortex or Linked effects are community candidates, not prescribed namesDense encounters where allies can punish displaced or softened groupsA boss or elite ignores the crowd-control value; long attack commitment leaves no safe exit; healing is treated as unlimitedOfficial role + community build suggestions; not site-tested
Patient solo-boss pressureUse hammer reach, short confirmed combo windows, movement or dodge recovery and a saved healing optionSingle-target fights where spacing and repeated safe punishes matter more than wave clearGreedy full strings, sitting at an unsafe middle distance, assuming every attack can be block-cancelled or spending the heal too earlyCommunity observations with disputed mechanics removed; not site-tested

What the current community reports broadly agree on

  • Ruadh's hammer reaches farther than its animation speed may initially imply;
  • area pressure and shield breaking feel more comfortable in groups than in long solo-boss exchanges;
  • movement speed or dodge recovery can reduce the cost of his slow commitment;
  • patience and short punish windows matter more than forcing a full combo;
  • retaining a healing option can be more valuable than spending it on routine damage.

These points are observations, not measured balance facts. Use the Emblem Catalog to inspect the small verified reference set and the build-planning framework to turn the effects offered in your run into a trigger-and-payoff plan.

Disputed or still unverified

The community thread does not establish one best Clan, one best weapon variant, exact dodge recovery thresholds, a universal combo string or reliable block-cancelling for every attack. Trials-specific performance also remains unverified. Those claims stay out of the recommendation table until a current version, loadout and repeatable test route can be recorded.

Sources