Escort Quests

Context

This video is a follow-up to Tim Cain's earlier video "RPG Features Nobody Asked For," where he listed escort quests as a feature no reviewer has ever requested more of. The comment section overwhelmingly proposed the same fix: have the escort NPC join as a party companion. Tim addresses why this doesn't actually solve the problem.

The Proposed Solution

Many commenters suggested: when an NPC needs escorting, they simply join the player's party as a companion. When you reach the destination, they thank you and leave. This supposedly eliminates issues with NPC walking speed, pathing, the player getting too far ahead, and timing conflicts with other quests.

Problem 1: Companion Mechanics

Making an escort NPC a companion immediately raises mechanical questions:

• Control: Are they controllable like regular companions? If yes, they need full companion systems. If no, players will be confused why this "companion" behaves differently.
• Inventory and equipment: Can you give them items? Change their gear? If not, why does this companion work differently from others?
• Companion limit: Most games cap party size for good reasons — frame rate, combat space, balance.

If They Can Exceed the Limit

Players could collect every escort NPC in the game without delivering any of them, building a massive entourage that breaks combat encounters and amplifies companion AI problems.

If They Can't Exceed the Limit

Players must dismiss an existing companion to accept the quest. This may require backtracking to a base, entering dismissal dialogues, and losing combat or dialogue effectiveness — all to babysit an NPC they didn't want in their party.

Problem 2: Duration

How long does the escort companion stay? This is a trick question — both answers create new problems.

Option A: They Stay Forever

If there's no time pressure, this is no longer an escort quest. It's a companion acquisition quest — a companion with an exit condition ("leave when the player visits location X"). Many regular companions already have exit conditions (alignment shifts, finding artifacts, killing certain NPCs). The escort NPC becomes functionally identical.

The Fallout Example

Tim tried exactly this approach with Tandi in the original Fallout. After rescuing her from the Raiders, she asks to be taken home to Shady Sands. But players who had already completed Shady Sands quests had no reason to return. QA testers discovered that Tandi functioned as a free permanent companion — not great in combat, but useful as an extra target to absorb enemy fire.

Players dragged Tandi through the entire game. She'd often die at the Military Base by running into force fields (like Dogmeat). Every additional unplanned companion amplified Fallout's already-significant companion AI issues. The "solution" created more problems than it solved.

Option B: Add a Timer

If the escort companion has a deadline, congratulations — you've converted a disliked quest type (escort) into a nearly universally hated quest type (timed quests). This is strictly worse.

The Lesson for Designers

Tim frames this as a common junior designer learning moment: there is no clean solution to escort quests. Every approach trades one problem for another. The designer's job is to:

1. Identify which set of problems they hate the least
2. Consider which problems will annoy their player base the least
3. Evaluate which approach best fits their game's design pillars (quest design, exploration, companion systems)
4. Accept that "don't do escort quests" is a perfectly valid choice

As Tim puts it: unless you can do them well, maybe you just shouldn't do them at all.

References

• Tim Cain. YouTube video. https://www.youtube.com/watch?v=nGGMpHgHTZc