Interacting With the Character's Retinue¶
How to build story around a player Character's soldiers and company.
Why Retainers Matter¶
A Character's retinue is not window dressing. It is a fundamental part of who they are. A knight without a household is a knight in exile. A sea captain without a crew is a captain in name only. A mage without a cabal is a mage doing solitary work.
The company is the Character's statement about their values. It shows what kind of leader they are, what kind of people follow them, what battles they are willing to fight. Over the course of a campaign, the composition and fate of that company becomes part of the Character's legend.
As a GM, you build story around that company. Not by exerting pressure on the player (the player controls their retinue), but by treating it as real and consequential. When a soldier falls, acknowledge it. When a retainer sacrifices themselves, mark it. When the company fractures under the weight of a hard choice, feel that weight.
This is collaborative.
The Collaborative Framework¶
You can suggest a story through a retainer. Here is how it works.
A retainer approaches the Character with a request, a concern, or an offer. The soldier speaks their mind. They explain why something matters to them. They ask if the Character will help, or warn them of something, or reveal information that changes the situation.
You are not using this as a mechanical hook that the player must follow. You are offering narrative possibility. The player can accept it, explore it, embrace it. Or they can decline it. Either choice is valid. Either choice tells you something true about the Character.
If the player declines: - There is no resentment from the retainer. No mutiny. No betrayal. The soldier accepts the decision. - There is no hidden quest-giving NPC that will remind the player later. The moment passes. - The soldier remains loyal and effective. They continue to do their job.
This is respect for the player's agency. You suggested a direction. They chose differently. The story continues.
If the player accepts: - The hook unfolds naturally. You do not force a detour; you follow the thread they grabbed. - The story may surprise you both. A simple request (visiting a sister's village) can become a multi-session arc (the village is besieged, and the Character chooses to stay and help). - The retainer's investment in the outcome deepens. They matter now. They are not an NPC; they are a part of the Character's legend.
Framing a Good Hook¶
A good retainer-driven hook is specific, personal, and reasonable.
Specific. The retainer names what they want or what is wrong. Not, "I'm troubled" (vague). Rather, "My sister was taken in a slaver's raid three seasons ago, and I've heard rumors that her captors are sheltering near our route" (specific and actionable).
Personal. The hook stems from the retainer's own story or relationship, not from GM convenience. It is not "the kingdom needs you to investigate a mysterious tower." It is "I made a promise to a dying friend that I would return home with honor, and I am failing" (personal to the retainer).
Reasonable. The request does not demand that the Character risk everything or abandon their current goals. "Can we spare a half day to visit my family's grave?" is reasonable. "Can we commit to a six-month detour?" is a harder sell and should be the player's choice, not a hook.
A good hook respects the player's autonomy. It does not corner them. It invites them.
Examples of Effective Hooks¶
The Witness¶
Your character is an Errant (a lone swordmaster, not commanding a traditional company). One of their Bonded soldiers, Keegan, has been with them for two seasons. One evening, Keegan says, "There's something I need to tell you. A year before I found you, I was part of a raid. We burned a monastery. I was ordered to, but I chose not to object, and people died. The monastery is about two days south. The monks have been rebuilding. I've been sick with it ever since, and I don't know if I can keep moving forward without going back and facing what I did."
This hook is personal to Keegan. It is not a quest-giver giving a quest. It is a soldier confronting their conscience, and asking the Character if they will walk that road with them.
The player can refuse: "I respect you, Keegan, but my business is urgent. I can't spare the time." Keegan accepts. The weight of his unfinished business remains, character texture, but the campaign moves forward.
The player can accept: the Character and Keegan detour to the monastery. What unfolds might be a conversation with the monks, a chance to help rebuild, a confession, a test. It could be a fight if someone at the monastery wants payment in blood, not apology. The hook is specific enough that you can improvise what happens, and personal enough that it will matter.
The Lost Love¶
Your Character is a Sea Captain. One of your crew, Lysa, has been with you for three years. One morning, during a port stop, Lysa tells you that she saw her former betrothed at the docks. The engagement was broken five years ago by family politics, not by choice. She thinks he is shipping out in two days.
She does not ask you for anything. She just tells you. She says she does not know what she wants to do. She is torn.
This hook does not force the Captain to do anything. It tells the player that Lysa is troubled. If the player's Character cares about her, if they have been building a relationship with Lysa, they might choose to help her sort it out, or to encourage her to seek her betrothed, or to help them escape together. If the player is less invested, the player might say, "That's rough, Lysa. What do you want to do?" and leave the decision to her.
The hook is an opening, not a mandate.
The Conscience¶
Your Character is a Mage who has been building a cabal of followers. One of them, a younger mage named Tor, comes to you with research about a ritual you plan to perform. Tor says, "I've been working the problem you gave me, and I think there's a flaw in the casting. Not a small one. If we try this, it could backfire badly. But I'm not certain. I wanted to tell you before we commit."
This hook presents a legitimate problem. It does not tell the player what to do. The player can trust Tor's judgment and revise the plan. The player can discount Tor's concern and proceed (risking consequences). The player can table the ritual entirely and pursue something else.
What matters is that Tor is shown as thinking, concerned, and willing to challenge the Character. This builds the cabal as a group of people with agency, not as tools.
Reading the Character Through Their Retinue¶
How a player treats their soldiers tells you who their Character is.
A player who accepts every retainer-driven hook might be building a character whose loyalty to their people exceeds their personal ambition. A player who declines most hooks might be building a character who has hard priorities and carries the weight of disappointing people. A player who invests time in naming and bonding soldiers might be building a character who leads through relationships. A player who treats soldiers as expendable resources might be building a character whose ambition exceeds their conscience.
None of these are wrong. They are different Characters with different values.
Pay attention. Adjust your hooks to the player's priorities. If a player is building a character whose relationships are central, weave in more personal, relational hooks. If a player is building a cold, calculating leader, offer hooks that test that character's limits. If a player is building someone caught between duty and desire, frame hooks that explore that tension.
The retinue becomes a mirror that the player and you look into together.
When Not to Push a Hook¶
There are moments when you should not suggest a retainer-driven hook, even if one would narratively fit.
Do not hook a player who is in a momentum scene. If the party is in the middle of a time-critical crisis (fleeing, pursuing, in desperate combat), this is not the moment to have a retainer express a personal need. Wait until rest and safety.
Do not use hooks to stall or delay. If you sense a player has made a decision and is moving toward a goal, do not use a retainer hook to derail them. That is manipulation, not collaboration.
Do not repeat a declined hook. If a player declined a hook once, it is done. Do not have the same retainer make the same request again unless the situation materially changes (the sister's village is now under siege, not simply to be visited). Respect the player's choice.
Do not hook to fix a mechanical problem. If the party is losing a fight badly and you want to give them a chance, introduce a retainer hook to escape or regroup. That is obvious and breaks trust. Let the fight be what it is.
Do not use a hook to override a Character decision. If a Character has decided to betray someone or ignore a former friend, do not have a retainer beg them to reconsider as a way of reversing their choice. You had your moment to offer a hook. The player made their decision. Honor it.
Building Investment Over Time¶
A strong retinue story spans a campaign, not a single session.
Early on, retainers are generic. They have roles and capabilities but little personality. This is fine. The player is still learning the game.
As the campaign progresses, encourage the player to name soldiers. Offer small moments of personality (a scarred archer with a dry sense of humor, a young pikeman who is homesick, a grizzled sergeant who has seen too much). These do not need to be long scenes. A sentence or two of color can do it.
Naming is free and needs no permission; a player may name a Retainer the day they recruit them. What to mark is Bond 2, when a Retainer becomes Distinguished and is known beyond the Company. That soldier now has a relationship with the Character. They have survived battles together. They know each other.
When a Bonded soldier falls, give that moment weight. Do not rush past it. Let the table feel it.
Over multiple campaigns or a very long single campaign, the player will have lost soldiers, acquired new ones, forged deep bonds with some, and watched others move on or fall. This is the arc of leadership. This is the weight of command. This becomes the Character's legacy.
Example: A Campaign Thread¶
Your session begins with a routine journey. One evening at camp, a soldier named Jace approaches the Character. He is a generic sword-and-shield soldier, newly acquired.
Jace says, "Captain, I know I haven't been with you long, but I needed to tell you something. Before I joined your company, I took work guarding a merchant caravan that was trafficking people as cargo. I didn't know it at first, but I realized it. I should have walked. I didn't. I stayed for the coin. I helped lock the cages."
He says he knows the Character will think less of him. He also says that the same merchant is operating again, further south, and if the Character ever wants to make it right, he will help, with no extra coin. But if not, he understands.
This is a hook. The player can accept or decline.
If the player declines: Jace remains with the company. Over the next few sessions, Jace proves himself reliable in combat and loyal. He never brings up the merchant again. But you have established that Jace carries this weight. If later, the party's path brings them near the merchant, you might let the player decide whether to take a detour. The weight is there.
If the player accepts: The party changes course. They find the merchant. What follows might be a political negotiation (the merchant has local protection), a covert rescue operation, or an outright assault. It unfolds based on what the players do.
Afterward, Jace's relationship with the Character has deepened. The Character has shown that they will act against injustice, and Jace has been given a chance to do penance. If Jace reaches Bond 2 later and becomes Distinguished, that standing will carry this arc with it.
Months later, if Jace falls in combat, the loss will matter. The player will remember his shame, his redemption, and his loyalty. They will mourn him not as a generic soldier but as Jace.
That is a retinue-driven story.