Introduction
Combat in The One Ring RPG 2e is a dangerous, dramatic scene that a Company should reach for sparingly. Start with why the confrontation is happening, what each side wants, and how the place changes the choices available. The rules then organize opening volleys, close-quarters stances, engagement, attacks, Endurance loss, and the risk of Wounds. A fight becomes memorable when the Company must protect, escape, delay, rescue, or decide when not to press on.
This guide covers the whole confrontation in one place: the shape of a fight, the four stances, war gear, Endurance and Wounds, Dread and Hate, and how to read an adversary profile as a scene tool rather than a pile of numbers to erase.

Use How to Play The One Ring RPG 2e for the wider scene procedure, The One Ring RPG Dice Mechanics Guide for the Feat and Success dice behind attacks and Shadow Tests, and The One Ring RPG Skills Guide for the approaches that still matter mid-fight. Keep the Character Sheet Guide close: Endurance, Load, Weary, Wounded, and gear are live parts of the situation, not post-fight paperwork. For the full round-by-round procedure and a worked example at a flooded ford, read The One Ring RPG 2e Combat Guide.
Hot Take
The best combat encounter is often the one the Company does not completely win.
| Consequence | Caveat | Reader action |
|---|---|---|
| Retreats, bargains, rescues, and partial victories carry combat consequences into later scenes instead of ending at the last attack | Do not use unwinnable fights to punish sensible players; make alternatives visible and meaningful | Before the next fight, write one outcome that matters if the Company gets away without achieving everything |
The rules back this up at every turn. Rearward doubles as an exit, Defensive lets a hero break away, Resolve invites surrender, and a Wound follows the Company for days. A fight that leaves a road closed, an ally grateful, an enemy warned, or a hero carrying a scar is a better sequel hook than counting helmets.
Why Combat Matters
The Core Rules treats a fight as a momentous event. It happens during an Adventuring Phase, and it should not be dulled by bland repetition: Player-heroes can lose Endurance, become Weary, suffer Wounds, fall unconscious, or die. That risk is why a victory should change something and why avoiding a fight can be a strong outcome rather than a failed encounter.
Combat is still frequent. The book expects a typical Company to face at least one combat encounter in every two sessions, so the procedure needs to flow. A fight should come out of the story and its consequences, not from an obligation to clear a map before anyone can talk to the person in the next room.
| Let combat answer... | Do not make it only... |
|---|---|
| Can the Company protect a person, place, or chance to escape? | A queue of enemies waiting to be removed |
| What will the heroes risk to keep going? | A separate minigame with no campaign consequence |
| How do terrain, distance, and fear change a hard choice? | An excuse to ignore the fiction until the last roll |
| Can the heroes find another solution before or during the fight? | Proof that talking was a mistake |
Start with the Onset of Battle
Before applying the combat sequence, establish the onset: why the sides confront each other, where they are, and what the immediate situation allows. The Core Rules asks the Loremaster to vary fights according to the ongoing story, the players' plans and preparation, terrain, weather, and strategic options. A rain-soaked ford, a narrow mountain path, and a roadside ambush should not create the same decisions.
Use this compact preparation flow:
What does each side want right now? | v What feature of the place changes movement, sight, cover, or escape? | v Is there distance for opening volleys, or surprise to resolve? | v What changes if the Company wins, retreats, bargains, or fails?
Surprise is a judgment call. A well-planned ambush against foes with no lookouts can succeed without a roll. When a roll is needed, an ambushed Company rolls AWARENESS, and heroes who fail lose their opening volley and their actions in the first round.
This gives the rules something to resolve. If foes are trying to seize a messenger, delay the Company, steal an object, or force a retreat, the fight has an ending other than "everybody falls down." That is kinder to pacing and more interesting than giving an Orc a personal grudge against the concept of lunch.
The Combat Shape at a Glance
Once a combat encounter starts, the Core Rules first handles any opening volleys the situation permits, then moves to repeated close-quarters rounds. Each close-quarters round has three parts: the Company chooses stances, combatants become engaged, and actions are resolved in stance order from Forward to Rearward. The whole Company acts first, then the Loremaster resolves the adversaries.
| Stage | Table question | Why it matters |
|---|---|---|
| Onset | What kind of confrontation is this? | Establishes terrain, surprise, distance, and goals before anyone chooses a stance |
| Opening volleys | Is there time and space for ranged attacks? | Makes distance and preparation matter before close combat begins |
| Stance | How exposed or cautious is each hero this round? | Turns positioning and team priorities into a visible choice |
| Engagement | Who faces whom, and who is free to act at range? | Makes enemy numbers and Company coordination matter |
| Action resolution | What does each combatant try to accomplish? | Leaves room for attacks, combat tasks, rescue, movement, and other meaningful actions |
| Consequence | What did the fight cost and what changed? | Connects Endurance, Wounds, escape, victory, and future scenes |
An attack uses the Combat Proficiency for the weapon and rolls against the attacker's STRENGTH TN modified by the target's Parry; adversaries roll against the hero's PARRY score instead. A hit costs Endurance equal to the weapon's Damage, Success icons can buy special damage, and a Feat die result of 10 or the Gandalf rune is a Piercing Blow that can cause a Wound. The Endurance and Wounds section below covers what those hits mean for the Company.
Make Terrain and Goals Do Work
The Core Rules gives the Loremaster complications and advantages for conditions such as bad weather, darkness, mud, cover, high ground, and cramped quarters. Use them because the fiction makes them real, not as surprise penalties after a player has described a sensible action.
| Battle feature | Let it create this choice |
|---|---|
| Narrow bridge or ledge | Who holds the space, and who can safely stay at range? |
| Dense trees or heavy rain | Is a clear shot worth the time or risk to gain it? |
| Flooded ford or deep mud | Does the Company press on, help someone, or seek a different route? |
| Threatened bystander or fragile object | Does someone spend an action protecting rather than attacking? |
| A foe trying to flee or capture someone | Which hero stops the goal instead of pursuing the easiest target? |
Players should ask plain fictional questions before selecting a stance: "Where is the exit?", "Who is exposed?", "What can reach us?", and "What are they trying to do?" Loremasters should answer clearly enough for choices to be informed. Mystery can be a danger; hidden battlefield facts should not be a gotcha.
Combat Stances
At the start of every close-quarters round, each player picks a stance for their hero. Forward, Open, Defensive, and Rearward are not permanent roles or a personal rotation. They express where a hero is trying to stand, how much risk they will accept, and what the Company needs this round: press a threat, hold a line, protect a companion, or keep a clear shot. Adversaries never choose stances; the rule describes the fight from the heroes' side only.
Stances Are a Team Decision
Stances are chosen before engagement. That order matters: the Company decides how its members will approach the fight, then sees who must face which opponent, then resolves actions in stance order. A choice that suited the last round may be wrong after a companion is hurt, a foe breaks past the line, or the group finally reaches the bridge it needed to cross.
Do not ask, "Which stance is my build?" Ask, "What must the Company accomplish before the next round ends?" The answer can be an attack, but it can also be holding space, getting an injured friend clear, rallying allies, preparing a shot, or making an enemy hesitate. The strongest stance is often the one that makes another hero's choice possible.
| Stance choice should consider... | Not only... |
|---|---|
| The objective, terrain, sightlines, and escape routes | The hero's preferred attack bonus |
| Enemy numbers and who could be engaged by more than one foe | The nearest visible target |
| Whether a companion needs room, protection, or encouragement | Whether another player has already chosen their usual stance |
| What changed since the last round | What worked in a different battle |
The Four Stances at a Glance
The Core Rules offers three close-combat stances and one ranged stance, each with its own risk and combat task. The table paraphrases the effect of each; check the book for the full wording.
| Stance | Effect in brief | Best first question | Related task |
|---|---|---|---|
| Forward | Your attacks gain (1d), and close attacks against you gain (1d) | What immediate threat needs to be disrupted or driven back? | Intimidate Foe |
| Open | No advantage or disadvantage | Who could use help on the next exchange? | Rally Comrades |
| Defensive | Close attacks against you lose (1d); your attacks lose (1d) per opponent engaging you | Who must not be overwhelmed, reached, or left exposed? | Protect Companion |
| Rearward | Ranged attacks only, and only ranged attackers can target you | Does the Company have the space and close-combat support to keep this shot available? | Prepare Shot |
Forward is not "the attacker stance," Open is not "the normal stance," Defensive is not "the safe stance," and Rearward is not "the archer's entitlement." Each is a short-term response to the battlefield. A hero with a bow may need to fight close when the Company cannot protect a ranged position, while a close-combat hero may choose Defensive because the person beside them matters more than landing another blow.
Engagement follows. Usually a hero can be engaged by up to three human-sized foes or two large ones, such as Trolls. When enemies outnumber the Company, the Loremaster assigns engagement; when the Company matches or outnumbers them, the players choose. Say engagement aloud as a tactical fact: "You are holding the bridge while two foes push toward the archer" is a decision prompt that tells the players what their next choice costs.
Choose by Battlefield Question
Use the scene to identify what the Company needs, then choose stances that make the answer plausible together.
| Battlefield question | Stance conversation |
|---|---|
| "Can we stop them reaching the guide?" | Someone may press the closest threat while another holds a protective position near the guide |
| "Can our archer keep a clear shot?" | Confirm enough allies can take and hold close-combat positions before someone relies on range |
| "Who is already carrying too much risk?" | Shift a companion toward protection or let another hero take a more exposed role |
| "Do we need to break morale or buy time?" | Consider a stance whose combat task changes the fight instead of adding another attack |
| "Is this a route to escape, not a fight to finish?" | Favor protection, position, and movement over a round spent maximizing damage |
This is why the group should say its choices out loud before engagement. "I will keep the path open if you get the injured Hobbit to the cart" is enough coordination to turn separate stance picks into a plan.
Rearward Needs Company Support
Rearward is the only stance for ranged attacks after the opening volleys, and a hero in it cannot be engaged in close combat. It is not automatically available. The Core Rules allows it only when the enemies number no more than twice the Company, and for each hero in Rearward, two other heroes must be fighting in close-combat stances.
The fiction can change what is possible. The Loremaster may allow more Rearward heroes on a narrow ledge, a mountain path, or similar ground that favours shooting, or when the Company clearly outnumbers its foes. A sudden rush, dense trees, or an enemy who breaks through can take that room away. Establish these facts before stance choice, and treat a Rearward position as something the Company maintains together. The ranged hero did not earn it by filling out the correct character-sheet field; someone else is standing between them and trouble.
| If the ranged position is... | The Company can... |
|---|---|
| Clearly protected | Let the ranged hero focus on a needed target or prepare a better shot |
| Threatened by extra foes | Shift close-combat priorities toward holding the line or move the archer |
| No longer legal or plausible | Change plans rather than arguing that a bow ignores the people standing in front of it |
| Valuable but not essential | Decide whether giving it up creates a safer escape or rescue |
Rearward also matters for escape. A hero who takes Rearward can simply leave the fight on their turn with no roll. A hero in Defensive can instead try to break away: a successful attack roll deals no damage but gets them off the field.
Use Stance Tasks to Change the Fight
Each stance has a combat task that takes the hero's main action and a Skill roll, and the player must describe what the hero does. Using one says the Company believes changing the battlefield matters more than an immediate strike.
| Stance task | Skill | Fiction-first use |
|---|---|---|
| Intimidate Foe | AWE | Shake enemy morale with courage or threatening momentum; weaker foes become Weary for the round, and more Success icons reach stronger ones |
| Rally Comrades | ENHEARTEN | Call the Company together; Forward fighters gain (1d) next round, and Success icons extend it. Only one hero may rally per round |
| Protect Companion | ATHLETICS | Interpose or draw danger; the next attack on the protected hero loses (1d), plus (1d) per Success icon |
| Prepare Shot | SCAN | Take time to find a clearer line; the next ranged attack gains (1d), plus (1d) per Success icon |
State the result you want in fiction first. That helps the Loremaster judge whether the task applies and makes a success feel like a change in the scene, not a colored token on an invisible board.
A Fast Stance Conversation
Run this five-question exchange before the group locks in stances:
- What changes if we fail to act this round?
- Who is most exposed right now?
- Can someone safely remain at range?
- Which foe, route, or companion is the real priority?
- Which stance choices let us answer that together?
Example: two enemies hold a rain-slick bridge while another circles toward a wounded companion. One hero chooses Forward to pressure the bridge, another chooses Defensive to protect the wounded companion, and a third stays Open to react after engagement. The group does not need a formation diagram; it has a shared answer to the real danger.
Running a Game This Week?
The GM Session Kit - a Session Zero template, a recap format, and a pricing cheat sheet. Free, and yours the moment you ask.
No spam, unsubscribe anytime.
Weapons, Armour, and Shields
Choose war gear by starting with the hero. A weapon needs to match a Combat Proficiency, solve a likely range or positioning problem, and leave the hero able to carry it through the adventure. Armour and shields add protection, but their Load feeds straight into Weariness. The right kit lets the Company meet danger and still reach the next safe place.
Start with the Role, Not the Table
Starting heroes choose one weapon for each Combat Proficiency they have a rating in, plus their preferred armour, helm, and shield. The book warns against grabbing the biggest weapons and heaviest armour, because a heavy burden hampers a hero on long marches. A Barding with an axe, a Hobbit with a sword, and a Ranger with bow and spear can all be well prepared when the choice fits their proficiency and the work they expect to do.
Before checking values in the Core Rules, ask four questions:
- Which Combat Proficiency will the hero use?
- Does the Company need a way to act before close quarters?
- Will the weapon need one hand, two hands, or a second weapon for a different range?
- Can the hero afford the Load once armour, shield, travelling gear, and Fatigue matter?
The last question ties equipment to the rest of the game. Load does not mean a hero must carry the lightest kit. It means a defensive choice should be made knowing that a hard journey or low Endurance may make that protection feel expensive later.
The Four Combat Proficiencies
The Core Rules groups weapons under four Combat Proficiencies. A hero rolls the rank recorded for the matching group; with no rank in it, the hero rolls only the Feat die. Combat Proficiencies can never be Favoured and improve only with Adventure points, not Skill points.
| Proficiency | War gear it covers | Practical question |
|---|---|---|
| Axes | Axe, long-hafted axe, great axe, and mattock | Does the hero want a heavy close-fighting tool that matches this martial tradition? |
| Bows | Bow and great bow | Can the Company protect the archer's position and provide a close-range fallback? |
| Spears | Short spear, spear, and great spear | Does reach or a thrown option help before the fight closes? |
| Swords | Short sword, sword, and long sword | Does a straightforward close weapon fit the hero and the expected terrain? |
Unarmed attacks, daggers, cudgels, clubs, and improvised weapons are Brawling rather than a fifth proficiency. The hero rolls their highest Combat Proficiency but loses (1d). Keep a dagger or believable improvised option in the fiction, but do not build a plan around needing that penalty.
Choose by Range, Hands, and Load
The weapon names describe practical constraints. A short spear can be thrown or thrust one-handed. A spear can be thrown or used with one or two hands. A great spear is a two-handed close weapon that cannot be thrown. Long swords and long-hafted axes work one- or two-handed; the great axe and mattock need both hands. Both bows are two-handed ranged weapons, and the book notes archers seldom carry shields because they cannot use them while shooting.
| Company need | Useful direction | Watch for |
|---|---|---|
| Act before close quarters | Bow, great bow, or a throwable spear | The archer still needs a way to respond once enemies reach them |
| Hold a close position | A spear, sword, or axe that fits the proficiency | Whether a hand is free for a shield and whether the terrain permits the choice |
| Carry a two-handed weapon | Great axe, mattock, great spear, or a two-handed grip on a versatile weapon | Loss of shield use and the burden carried between fights |
| Travel with flexible options | A primary proficiency weapon plus a believable backup | Total Load after armour, shield, and travelling gear are counted |
Do not infer a weapon's effect from its name alone. The Core Rules gives each one Damage, Injury, Load, and notes, and those numbers decide the final tradeoff. Heavier weapons generally hit harder and weigh more; check the table for the exact figures. Special damage also varies by weapon type: any weapon can land a Heavy Blow, any close weapon can Fend Off, Bows, Spears, and Swords can Pierce, and a shield allows a Shield Thrust.
Armour, Helms, and Shields
Armour and helms add Success dice to the Protection roll a hero makes against a Piercing Blow, and a shield adds to Parry. All of them add Load. When current Endurance reaches total Load or lower, the hero becomes Weary, so the protective package belongs in the same decision as the weapon.
| Gear choice | What it contributes | What to check |
|---|---|---|
| Armour | Protection dice against serious injury, from leather to mail | Its Load alongside the rest of the travel kit |
| Helm | One more Protection die | Whether its Load is worth it; a helm can be taken off mid-fight to shed Load |
| Shield | A bonus to Parry, doubled against opening volleys you see coming | Its Load, a free hand, and the risk of foes that break shields |
A new hero starts with one suit of armour and may add a helm and a shield. Shields come as a buckler, shield, or great shield, and Hobbits cannot use a great shield. Match the shield to the weapon and expected role rather than taking the largest option by default. Some adversaries can smash a shield and strip its Parry bonus, which is one more reason to plan for losing it.
Build a Practical War Gear Package
Decide in a short order. It avoids accidental mismatches and the urge to chase a number before deciding what the hero does in the story.
Choose the Combat Proficiency on the sheet | v Decide whether the hero needs range, close defence, or both | v Check one-handed or two-handed use against shield and backup plans | v Add armour, helm, and shield, then total the Load | v Use the Core Rules to record exact values and special rules
A hero proficient with Spears on a dangerous road might first decide between a throwable short spear and a spear that can also be gripped two-handed. If the hero also wants a shield, one-handed use matters. The player then totals Load with armour and travelling gear, rather than discovering Weariness only after Endurance has already dropped.
A hero with Bows builds a different package: the bow serves the opening volley and a protected Rearward position, while a close-range backup and a plan for losing distance keep the hero involved after the fight changes. Neither package is better. Each tells the Company what support it can offer and which situations will complicate it.
Endurance, Weariness, and Wounds
Endurance, Load, Weary, Wounded, and Dying are connected pressures, not five versions of the same hit-point problem. Endurance measures what the hero can keep carrying; Load and Fatigue make Weariness arrive sooner; a Wound has longer consequences; and a Dying hero changes everyone's priority at once. Track them as prompts for a Company decision: press on, protect someone, travel more carefully, rest, or seek help.
Read the Pressure Track
Endurance represents physical stamina and determination. Heroes lose it to combat damage, other physical harm, and strenuous effort. Load represents the weight and bulk they carry, and journey Fatigue temporarily raises Load. A Wound represents serious injury, not a larger ordinary loss of Endurance.
These rules form a chain. A heavy pack narrows the gap before Weariness. A Wound changes recovery and turns a second serious injury into a life-threatening emergency.
| State | What it means at the table | Useful next question |
|---|---|---|
| Endurance loss | The hero is hurt, strained, or exhausted but still active | Can the hero safely take another risk? |
| Load and Fatigue | Gear and travel pressure make Endurance harder to preserve | What can be carried, shared, left behind, or delayed? |
| Weary | The hero's burden is now degrading their reliability | Is this the moment to rest, change plans, or ask for support? |
| Wounded | A serious injury is slowing recovery and raising the stakes | What care, safety, and time can the Company secure? |
| Dying | A second Wound or a grievous result demands urgent help | Who can act now, and what danger must the group accept to save them? |
Endurance, Load, and Weariness
When current Endurance falls to the hero's total Load or below, they become Weary. While Weary, any Success die showing 1, 2, or 3 counts as zero. The hero stays Weary until Endurance rises above Load again, which makes gear, armour, and journey Fatigue part of the risk calculation before anyone is Wounded.
At zero Endurance a hero drops unconscious and wakes after an hour with 1 Endurance, unless they are also Wounded. Waking up leaves a hero far short of ready for the next encounter. The Company still has to decide whether it has time, shelter, and safety to recover.
| Situation | Table consequence |
|---|---|
| Endurance is falling but remains above Load | The hero acts normally, but the next hard choice may push them into Weariness |
| Endurance reaches Load | Mark Weary at once and reconsider high-risk actions |
| Journey Fatigue raises Load | A familiar load can suddenly become burdensome, so travel decisions shape the next fight |
| Endurance reaches zero | The hero is unconscious, removing a Company resource and possibly creating a rescue problem |
Knockback is the one in-fight tool for easing the blow. Once per round, a hero can halve the Endurance lost to a successful attack by being knocked back, at the cost of spending their next main action recovering position. Adversaries cannot choose knockback. Use The One Ring RPG 2e Character Optimization Guide to plan gear and Company coverage before the first hard journey; good planning does not pretend a hero never tires, it gives the Company options when someone does.
Wounds Are Not Ordinary Damage
A serious injury starts with a Piercing Blow. The target rolls the Feat die plus Success dice equal to their armour's Protection against the weapon's Injury rating; if the attack also made them Weary, this roll comes first. On a failure, the hero is Wounded, marks the box, and rolls the Feat die for severity: a moderate injury clears within hours of the fight, a severe one takes days to mend, and a grievous one leaves the hero at zero Endurance and Dying. A Wounded hero recovers Endurance slowly.
A second Wound drops the hero to zero Endurance, unconscious and Dying, with no second severity roll. Protect a Wounded companion rather than treating the checked box as an invitation to prove bravery until the next roll disagrees.
| Do not confuse... | With... |
|---|---|
| Endurance loss | A Wound; Endurance pressure is common, while Wounds carry serious ongoing risk |
| Being Weary | Being Wounded; Weariness hurts roll reliability, while Wounds constrain recovery and threaten a hero who is hit again |
| Falling unconscious at zero Endurance | Being Dying; a Dying hero needs a successful HEALING roll within about an hour |
| First Aid | Erasing the injury; it shortens the time a Wound takes to mend |
Rest and First Aid Change the Next Choice
Rest restores Endurance, and the pace depends on the kind of rest and whether the hero is Wounded. A day usually allows one short rest of at least an hour, which restores Endurance equal to STRENGTH, and a Wounded hero gets nothing from it. A prolonged rest, usually a night's sleep, restores all lost Endurance, or only STRENGTH worth for a Wounded hero. The Loremaster can allow extra prolonged rests in a safe, comfortable place.
First Aid is a HEALING roll that cuts a severe injury's recovery by 1 day, plus 1 per Success icon. Each hero can receive a successful First Aid only once, and a failed attempt cannot be repeated until a day has passed. A Dying hero saved by HEALING wakes in about an hour at 1 Endurance, adds 10 days to their injury's recovery, and keeps a permanent mark such as a scar or limp. Once the crisis passes, let the injury shape what the Company can credibly do next: seek shelter, slow the journey, ask an ally for aid, or pick a safer route.
| Recovery choice | What it asks the Company to decide |
|---|---|
| Take a short rest | Can the group spare an hour now for a modest recovery? |
| Take a prolonged rest | Is there enough safety and time to recover properly? |
| Administer First Aid | Who can help, and can the scene give them the chance? |
| Continue while Wounded | What objective is worth the extra danger? |
| Seek a haven or help | What promise, route, or timeline must change to keep a companion safe? |
A Practical Triage Flow
Use this quick check after a hard hit, difficult exertion, or combat round:
Did anyone become Wounded or Dying? | +-- Yes: secure urgent care and decide whether the scene can continue safely. | +-- No: check current Endurance against Load. | +-- Weary: reduce pressure, share burdens, or plan rest before the next major risk. | +-- Not Weary: ask whether the objective justifies continuing with reduced reserves.
Example: after driving off attackers, one hero is Wounded and another is Weary from travel Fatigue. The safest choice may be to reach shelter rather than chase the retreating foes. The retreat can still create a later consequence, but pursuing now could turn one hard fight into a recovery problem the Company cannot solve alone.
Fear, Dread, and Hate
Fear in The One Ring RPG 2e is usually not a separate courage subsystem. A terrible sight, place, or enemy causes Dread, which threatens Shadow points, and the hero can resist it with a VALOUR Shadow Test. That is different from an adversary's Hate, a combat resource the Loremaster spends to make a minion of the Enemy more dangerous. Keep the two apart: one asks what the hero can carry in their heart, and the other tells the Loremaster when a foe can show its worst side. No shield substitutes for a VALOUR roll.
Fear Is Usually Dread
Start by naming the source. Dread is Shadow gained from witnessing something that can strike fear or doubt: a horrible creature, a cursed place, a gruesome event, or the direct power of the Enemy. It is not Endurance loss, and it does not tell the player what their hero must say, feel, or do.
The Core Rules scales Dread from an unexpected tragedy (1 Shadow point) up to experiencing the Enemy's power directly (4 points). Use that range to calibrate, not as a contest to make every scene more miserable than the last.
| Ask first | Why it matters |
|---|---|
| What did the Company actually witness or experience? | Dread should arise from the scene, not a vague claim that the area is scary |
| Is this an ordinary danger or a source of the Enemy's terror? | Ordinary physical danger may call for a different consequence than Shadow |
| How serious is the event on the Core Rules scale? | The Shadow gained should match the fiction and the book's guidance |
| Does a specific adversary ability add a further effect? | Follow the entry exactly instead of inventing a second generic fear penalty |
A storm, an enemy, and a haunted ruin can all be dangerous. Dread belongs to the moment when danger carries spiritual and moral weight; poor weather and a disappointing lunch do not qualify.
Make the VALOUR Shadow Test
Resolve the test like any other roll: a Feat die plus Success dice equal to the hero's VALOUR. A pass reduces the Shadow gained by 1, plus 1 for each Success icon. A failure does not mean the player portrayed courage wrongly; it means the full Shadow lands.
The fiction creates a source of Dread | v Determine the Shadow points from the Core Rules or the adversary ability | v Player-hero makes a VALOUR Shadow Test | +-- Success: reduce the gain by 1, plus 1 per Success icon | +-- Failure: take the full Shadow gain v Update Shadow and compare it with current Hope
The last step matters because Shadow is a long pressure track. A hero becomes Miserable when Shadow matches or exceeds current Hope, and rolling the Eye icon on the Feat die then means failure whatever the result. Reaching maximum Hope makes the hero Ill-favoured on all rolls until a bout of madness. Dread gets its force by piling up across an adventure, not from one check.
Read Fear Without Stealing Choice
Some adversaries cause Dread mid-battle and add a combat effect when the Shadow Test fails. The Strike Fear and Thing of Terror abilities, for example, leave a failing hero daunted and unable to spend Hope for the rest of the fight. That is a defined mechanical limit, not permission to narrate a hero as helpless, foolish, or unwilling to act.
Describe the threat, name the effect before the next meaningful choice, and let the player decide what courage looks like inside that limit. A hero may retreat, protect a companion, call a warning, hold position, or try something desperate. The rules supply pressure; the player supplies the person.
| Do | Avoid |
|---|---|
| Say what the Company sees and why it is dreadful | Announcing a Shadow cost with no fictional cause |
| State the Dread gain and the available test before resolving it | Treating a failed test as permission to take over a player character |
| Apply an adversary ability exactly as written | Stacking improvised fear penalties because the scene needs more drama |
| Let the Company respond to the changed situation | Making fear a private punishment with no scene consequence |
Hate Is an Adversary Resource
Hate is not the hero's anger, and it is not Shadow under another name. It is the fighting drive of minions of the Enemy and monstrous adversaries, and it works for them much as Hope works for heroes. The Loremaster can spend a point to give the adversary (1d) on a combat roll, usually an attack or Protection roll, and many Fell Abilities cost Hate. An adversary can spend up to its Might in Hate each round, and one with no Hate left is Weary.
That makes Hate a pacing tool. Spend it when the enemy's nature should matter: a terrifying reveal, an unnerving movement, a sudden burst of violence, or an ability that changes the Company's plan. Do not spend it simply because a point is sitting there.
| Track | Belongs to | What it represents | Main table use |
|---|---|---|---|
| Shadow | Player-hero | The burden of Dread, Greed, Misdeeds, and Sorcery | Long-term spiritual pressure |
| Hope | Player-hero | Inner reserves and resistance to despair | The line Shadow is measured against, and a bonus source on rolls |
| Hate | Enemy minion or monster | Relentless fighting drive | Loremaster fuel for combat bonuses and Fell Abilities |
| Resolve | Other adversaries | Motivation to fight without serving the Enemy | The same mechanical role, with different moral implications |
Run Fear-Causing Foes Clearly
Fear works best as part of an encounter's objective, environment, and visible behavior. The Company needs enough information to choose whether to stand, flee, protect someone, change stance, or look for another answer.
Name the visible danger and the immediate objective | v Identify the exact Dread source or Fell Ability in the Core Rules | v State timing, affected Player-heroes, Shadow gain, and any failed-test effect | v Offer the Company a real tactical or story choice | v Spend Hate only when the foe's nature should change the scene
For example, a terrible guardian blocks the only safe route to a trapped traveller. The Loremaster applies its printed ability at the stated timing, then asks what the Company does. The pressure is real, but the scene is still about a rescue.
Reading and Running Adversaries
An adversary is not a row of numbers waiting to lose Endurance. Its profile tells the Loremaster how hard it is to hit, how long it can keep fighting, how many attacks it makes, what pressure it creates, and whether the Company should expect it to fight to the end or consider surrender. Read the profile as a scene brief: decide what the foe wants, put that in the fiction, then let the statistics make that goal costly to ignore.
Read a Profile as a Scene Tool
The Core Rules gives adversaries simplified profiles to keep play moving, and it tells the Loremaster to ask what an enemy is trying to do apart from harming the Company. Its own example is the Uruk-hai at Parth Galen, whose goal was to capture the Hobbits rather than fight to the bitter end.
| Adversary objective | What it changes at the table |
|---|---|
| Guard a place, person, or route | The Company may need to distract, bargain, sneak, or draw the foe away |
| Delay the Company | Time, pursuit, and escape matter as much as reducing Endurance |
| Capture or drive away someone | Protecting a companion becomes the central combat task |
| Survive and report back | A retreating foe creates a consequence for the next scene |
| Take something or complete a dark task | The Company has a reason to act beyond winning a clean fight |
When preparing any foe, answer three questions: what does it want besides harming the Company, what does it do when the first plan goes wrong, and what follows if it escapes, succeeds, or is defeated? Then pick the adversary from the Core Rules and use its printed profile.
The Core Parts of an Adversary Profile
Each profile uses a short set of terms. Read them together instead of treating each one as a separate lever for making a fight harder.
| Profile part | What it tells the Loremaster | Table-facing implication |
|---|---|---|
| Attribute Level | A single threat rating that replaces the three Attributes and modifies Heavy Blows and many Fell Abilities | Major foes turn a successful attack into a larger problem |
| Endurance | How much harm and combat exhaustion the foe absorbs; at zero it is out of the fight | The group can decide whether it needs a quick escape, focused effort, or another plan |
| Might | Wounds needed to slay the foe outright, and the most attacks it can make in a round | A powerful enemy can split the Company's attention and survive more than one lucky blow |
| Hate or Resolve | The resource that fuels enemy effort and abilities | The Loremaster can show a foe pressing its advantage or running out of drive |
| Parry and Armour | Parry adds to the hero's STRENGTH TN; Armour sets the foe's Protection roll | The Company may need tactics or cooperation instead of repeating attacks |
| Combat Proficiencies | A primary and secondary attack, with Damage, Injury, and special damage options | The attack form should be visible in the fiction before it becomes a number |
| Fell Abilities and Distinctive Features | Special powers, plus one or two optional traits to use as obstacles | A foe gets a memorable method, tell, weakness, or change in the scene |
Adversaries can spread their Might in attacks across several heroes or focus on one. They never take knockback, and they do not normally become Weary from Endurance loss. The exact values stay in the Core Rules; copying them into campaign notes is useful at the table, while publishing a replacement bestiary is not.
Hate, Resolve, and Moral Stakes
Hate and Resolve fill the same mechanical slot but tell different stories. Hate belongs to all minions of Sauron and all monstrous creatures. They may flee a bad position, but they never yield, surrender, or give quarter unless forced by circumstances or orders. Resolve belongs to foes who are not sworn to the Enemy, such as Evil Men, who may take up arms through allegiance or bad luck, and may surrender when outnumbered or when losses mount.
That difference has weight. The Core Rules says attacking or killing an adversary with Resolve should always be evaluated as a possible Misdeed, which is a Shadow gain no test can reduce. The book's questions are simple: did the heroes provoke the fight, was there another option, and was killing necessary when the foe might have surrendered? Before the fight, ask whether another path exists. During it, make surrender, withdrawal, or parley visible if it fits. Afterward, consider who was harmed.
| If the profile has... | Use it to ask... |
|---|---|
| Hate | What frightening purpose or loyalty keeps this foe fighting? |
| Resolve | Why has this person or group chosen conflict, and what could end it? |
| A dwindling resource | What change in behavior shows the foe is becoming Weary? |
| A chance to retreat | What follows if the foe survives to warn others? |
This does not make every enemy sympathetic. It stops every armed figure being morally identical. Foes reduced to zero Endurance may even be barely alive when the fight ends, so survival, capture, or rescue can be more interesting than assuming a corpse.
Fell Abilities Should Change the Scene
Fell Abilities are the special talents and odd behavior that make an adversary more than an attack pattern. Many cost Hate or Resolve, and the Loremaster may use one even when it spends the foe's last point. Unless an ability says otherwise, it can be used in addition to an attack.
Use a Fell Ability when it changes a decision the Company can see. A movement ability can threaten a vulnerable position; a fear ability can make Hope suddenly precious; a defensive ability can make holding the line urgent. Announce the fiction and the effect, then let the players adapt. Read every relevant ability before the session so its timing and cost do not surprise you mid-fight.
| Good use | Weak use |
|---|---|
| The ability reveals the foe's nature and changes the current objective | Spending a resource only because it has not been spent yet |
| The Company can react with a stance, task, retreat, or new priority | Applying a surprise effect after choices could no longer change |
| The fiction explains why the mechanic occurs | Naming a rule without describing what the heroes witness |
| The ability creates an interesting cost | Adding unprinted penalties to make it feel harsher |
Prepare an Adversary Without Publishing a Stat Block
Use the printed profile at the table, then add only the scene information the book cannot know.
Choose the printed adversary that fits the threat | v Write what it wants before the fight and what it does if it succeeds | v Choose one visible terrain feature and one exit, rescue, or negotiation route | v Mark the relevant Fell Ability, Hate or Resolve use, and moral question | v Start the scene with the Company objective, not a surprise
For example, armed adversaries with Resolve might hold a bridge because they believe the Company brings danger to their community. The profile supplies the mechanical risk. The bridge, the frightened locals nearby, and the chance of a retreat or explanation create the scene. The Company can still fight, but it can see why fighting may cost something after the last attack roll. Remember too that many foes can talk: a clever parley or a well-told lie can end a fight the dice would lose.
Player and Loremaster Advice
Players
- Say what your hero is trying to protect, stop, or reach before selecting a stance, and what your choice makes possible for another hero.
- Change stance when the objective or danger changes; flexibility is a strength.
- Use a main action for rescue, position, equipment, or a combat task when that serves the real goal better than another attack.
- Pick war gear from the proficiencies on your sheet, carry an answer for the range where your main weapon is weakest, and total Load before assuming Endurance will stay comfortable.
- Update Endurance, Load, Weary, Wounded, and Shadow the moment they change, and tell the group when you cross a threshold.
- Treat a Wound or a failed VALOUR test as a limit to play through, not a cue for recklessness or for dropping out of the scene.
- Ask what a foe wants, and raise surrender, retreat, or negotiation before the final blow when it matters to your hero.
Loremasters
- Give every fight a concrete objective, terrain detail, exit, and consequence beyond body count.
- Describe space, enemy numbers, routes, cover, and vulnerable people clearly enough to support stance choices, and settle Rearward room before players commit.
- Let players establish starting war gear that suits their heroes; if gear is lost, make recovery part of a meaningful situation.
- Make rest, shelter, and help real choices, and apply the Core Rules injury procedures consistently without turning them into punishment.
- Establish the frightening cause before applying Dread, and use the Dread scale instead of turning every ominous detail into a Shadow Test.
- Spend Hate or Resolve to reveal a distinct threat or shift the situation, not to grind the Company down by routine.
- Let enemies pursue goals, change plans, surrender, or flee, and end combat once its objective is resolved.
Where To Go From Here
The combat guide runs the procedure blow by blow. Fights also cost more than Endurance, which the Shadow and Hope hub covers, and the Loremaster resources help you decide when a fight is the right scene at all.
Source Scope
This guide uses Chapters 3, 4, 6, and 8 of the Third Printing of The One Ring Core Rules. It paraphrases the combat sequence, stance effects and requirements, combat tasks, Endurance, Weariness, Wounds, rest, Dread, Hate, Resolve, and the adversary profile format. It does not reproduce the weapon, armour, and shield tables, the Wound Severity table, the complications and advantages tables, or any adversary entry or Fell Ability text. Consult the Core Rules for every exact statistic and procedure.
Return to the The One Ring RPG 2e Guide Hub, continue with The One Ring RPG 2e Combat Guide, or browse The One Ring RPG Guides.


