Let Companions Challenge Decisions in Your Mercenary Company RPG

Let companion preferences change Trust and mission support after a consequential choice.

Seele Editorial TeamUpdated November 18, 2026

A mercenary-company RPG can make companions feel distinct when they disagree for reasons the player can understand. In fictional Ashen Ledger, Mara argues for protecting civilians while Ivo prioritizes a contract deadline. Before a mission choice, each companion states a preference; the player still makes the final call.

Keep the response legible. Trust ranges from 0 to 3. Honoring a stated preference adds one point, while overriding it removes one. At Trust 3 a companion offers one mission support; at Trust 0 they withhold it. This fixed example is a paper rules scenario, not a tested narrative outcome.

Give each companion a principle behind their disagreement

Tie disagreement to a named priority, not a random mood. Mara wants the company to protect civilians; Ivo wants to meet the contract deadline. Before a consequential command, show each person’s preference and one reason. Their objections can disagree with each other while remaining consistent with their principles.

The player should retain authority. Companions explain a cost or alternative, then the player selects the company’s action. This makes dissent part of decision-making instead of a surprise refusal or an unearned approval.

A mercenary company debates a map as companions visibly disagree.
Companions voice different priorities before the player decides.

Make a bounded Trust change follow the chosen action

Track Trust from 0 to 3 for each companion. When the player honors a stated preference, add one point up to 3. When they override it, remove one down to 0. At Trust 3, the companion offers one defined mission support; at Trust 0, they withhold that support. Show current Trust and the decision that changed it.

Keep the response consistent across missions. A companion should not object to a choice and then lose Trust when the player follows their preference. If two people favor opposite options, make the tradeoff visible before the command is locked in.

Two mission outcomes show different companions supporting or objecting to the captain.
A small Trust range connects disagreement to a visible consequence.

Replay a bridge decision with two opposing preferences

Mara and Ivo both begin at Trust 2. The mission offers two choices. Repair the bridge costs 1 Supply and adds 1 travel day; Mara approves because it protects civilians, while Ivo objects because of the deadline. Choosing it raises Mara to 3 and lowers Ivo to 1. Mara offers one mission support; Ivo does not.

Taking the ford saves the day but leaves the village road exposed. Ivo approves and Mara objects, so Ivo rises to Trust 3 and Mara falls to 1; Ivo offers the support. The route and relationship changes follow the stated rule. This is a paper scenario, not evidence about how players will react to the story.

A stone bridge and shallow ford form two routes through a village.
Either option earns one companion’s support and lowers the other’s Trust.

Prototype one consequential choice before adding dialogue trees

Build a company roster, two companion principles, Trust counters, one mission fork and a support indicator. Let players compare both options before committing. Afterward, show who approved, who objected and exactly how Trust changed. A reset lets the same choice be replayed.

Only after the rule is understood should you add personal quests, dialogue branches or changing loyalties. Keep each reaction tied to a visible preference and let mission support have a defined effect so disagreement shapes play rather than becoming flavor text.

Create Ashen Ledger, a mercenary-company RPG where companions can disagree with the player. Mara prioritizes protecting civilians; Ivo prioritizes contract deadlines. Trust is 0–3 for each. Honoring a companion preference adds 1 Trust, capped at 3; overriding it removes 1, floored at 0. At Trust 3 they grant one mission support; at Trust 0 they withhold it. Both start at Trust 2. Mission choice: Repair bridge, spend 1 Supply and add 1 travel day; Mara approves, Ivo objects. Result: Mara 3/support, Ivo 1/no support. Or take ford, save a day but expose village road; Ivo 3/support, Mara 1/no support. Show reasons, Trust changes and support before/after. Include reset; do not claim narrative playtest results.

SEELE's official page describes a general workflow: generate a playable first version from a prompt, test it in a browser and refine it with follow-up prompts. Use it to inspect whether companion objections and Trust consequences are clear; Ashen Ledger and its rules are fictional design guidance.

Prototype companion disagreement in SEELE

Frequently asked questions

How can companions disagree meaningfully in an RPG?

Give each companion a consistent principle and have them explain how a choice supports or conflicts with it. Let the player make the final decision, then connect the result to a visible relationship or mission consequence so the disagreement affects play. Show the reason before the player commits to the route.

What should a companion Trust system show?

Display each companion’s preference, current Trust, the choice that changed it and any mission support gained or withheld. Define the range and update rule in advance. Start with one decision before adding long dialogue branches or personal quests. This makes each consequence easier to explain and compare.

How do I test an RPG companion decision?

Replay the same fork with each option and calculate the Trust change for every companion. Confirm that approval, objection and support match the stated principles. This checks rule consistency, not whether players find the story convincing. Record both outcomes in a small table so the rule stays auditable.

SEELE AI

Turn this guide into a playable build.

Start with a focused brief, then iterate in the Seele AI Workspace.

Start creating