Why protecting one complicated character can matter more than saving an entire fictional kingdom.

Spoiler warning: Major spoilers for the original The Last of Us game, remade as Part I, and HBO’s first season. No Part II or Season 2 spoilers. The linked ACOTAR article contains its own major book spoilers.

You know the quest.

Take this person to that place. Keep them alive. Collect your payment. Try not to get emotionally involved.

Excellent. A straightforward job. Finally, some professional boundaries in a fantasy-adjacent workplace.

Then the person starts talking.

They have opinions. They ask questions you don’t want to answer. Somewhere between the third ambush and the seventh argument, your hardened adventurer develops a devastating condition: giving a damn.

Congratulations. Your escort quest has become The Last of Us.

The payment is no longer the point. The destination is becoming complicated. And your character’s emotional defenses appear to have the structural integrity of a wet paper bag.

The kingdom is in danger. Anyway, how’s our weird little friend?

D&D adventures love a threatened kingdom. Ancient evil rises. The royal line is in peril. A hooded figure unfolds a map that took the DM six hours to make.

The players nod respectfully.

Then someone asks whether the nervous stablehand from last session made it home.

This can feel mildly insulting when you have prepared twelve noble houses and a succession crisis. The stablehand was called Ben because you panicked.

But Ben lent the rogue a coat. He remembered the cleric’s name. He wanted to see the ocean, and the party promised they’d take him.

The kingdom has a population. Ben has a relationship with the players.

That’s why a story about crossing a ruined country can land harder than another announcement that civilization is in danger. Joel starts out hired to transport Ellie. Their growing bond turns an assignment into something he can no longer treat as business.

For a DM, there’s a useful lesson here: let the party know someone before asking them to fear losing that person.

“Thousands will suffer” tells them the scale. “Ben left his coat in your bag” gives them something to hold.

Ellie is a person, which is terribly inconvenient for the quest log

The quickest way to make players resent an escort mission is to give them luggage with hit points.

It walks slowly. It wanders into danger. It contributes nothing except additional work. When rescued, it immediately resumes walking toward the same cliff.

You could replace it with a wheelbarrow and improve party morale.

Ellie matters because she has a personality and a will of her own. She’s funny, angry, curious, stubborn, and capable of affecting what happens. Her connection with Joel develops through friction as well as affection.

So give your companion something beyond a destination:

• A skill the party actually needs.

• An opinion that occasionally challenges them.

• A desire they understand, even when it causes trouble.

• A chance to help when the heroes are struggling.

Your apprentice healer might refuse to abandon an injured enemy. Your exiled prince might be excellent at fixing boots and hopeless at speaking to anyone who isn’t staff.

Let the players discover these things in play. A three-page biography is homework. Someone quietly repairing your broken shield is a relationship.

Found family includes finding each other annoying

You don’t need constant declarations of affection to build attachment.

Sometimes you need someone who knows exactly how irritating you are and still saves you a seat.

Our 6 D&D Monsters That Would Be Absolutely Terrible Roommates takes the domestic version of that problem to an unreasonable conclusion. A traveling companion offers similar opportunities, with fewer tenancy protections.

Who steals the blankets? Who insists they know a shortcut? Who notices the fighter hasn’t eaten and puts food beside them without making it a conversation?

Those little habits give affection somewhere to grow. They also give the party jokes that belong to their particular adventure.

Eventually, the companion who complains about every hill gets injured, and the barbarian carries them uphill while complaining twice as loudly.

Nobody says anything tender. Everyone understands.

The ending works because the relationship has consequences

Here comes the major spoiler.

At the hospital, Joel learns that the Fireflies’ attempt to develop a cure will kill Ellie. He rescues her by force, killing people in his way, and later lies to her about what happened.

You can understand the attachment driving him without finding every action defensible. His love for Ellie doesn’t make questions about her agency disappear. The Fireflies’ goal doesn’t make what they intend to do to her a simple matter either.

That tension is the part worth discussing. The ending asks what protecting someone means when other people have plans for them—and when the protector makes decisions on their behalf.

We explored a related tabletop problem in ACOTAR Book 6 Is Here, and the Night Court Needs a Session Zero: private loyalties can create very public consequences. Follow that link after reading if you’re avoiding ACOTAR spoilers.

An ally is still allowed to be furious with you. Someone you love can still feel betrayed by your protection. Saving a person doesn’t automatically settle what happens between you afterward.

That is inconvenient for heroes who would prefer to resolve everything with one excellent damage roll.

Borrow the emotional problem. Let your players choose the answer.

The original game tells Joel’s story through a fixed ending. Your D&D table has several people making decisions, and they may have extremely different ideas about what should happen.

Give them room to act.

They might challenge the supposed solution, seek another expert, bargain, refuse, or attempt something you didn’t anticipate. Investigating the situation should matter. So should asking the companion what they want.

An original adventure seed: the party escorts a young cartographer to a city whose protective wards are failing. Her living memories contain the only surviving map of their construction. The city’s proposed extraction would erase those memories—including everyone she has met along the journey.

She wants to help. She’s frightened. The city’s representative has already described the party’s bond with her as an “emotional complication.”

Watch how quickly the players stop liking that representative.

Then let them investigate the ritual, speak with her, and pursue alternatives. Resist deciding that only one outcome will make your story sufficiently tragic. Your players may earn a hopeful ending. Let them have it.

Pack something suitably ominous

 

For a survival campaign full of reclaimed ruins and things you absolutely should not touch, I’d bring our Ancient Poison seven-piece dice set.

Its turquoise-green finish and black numbering suit the mood beautifully. Perfect for the ranger investigating an abandoned building or the druid with suspicious mushroom expertise. The dice can settle your saving throw. They cannot stop you adopting another emotionally complicated NPC.

Make room for the person behind the objective

You can build a magnificent kingdom and still find that your players care most about the difficult person traveling beside them.

Give that person something to contribute. Let them form opinions about the party. Give everyone time for arguments, small kindnesses, and a meal that isn’t interrupted by combat.

Then, when a difficult decision arrives, you won’t need to announce that the stakes are personal.

The players will already be checking whether their friend is safe.

Which NPC has your party become unexpectedly attached to—and how thoroughly did that derail the DM’s plans? Tell us in the comments.

Game on. Check on your escort NPC.