Many players reach a point in long narrative campaigns where early dialogue selections begin to alter how companions respond during later sequences. Without a structured way to note these shifts, it becomes difficult to anticipate when a relationship will unlock new options or close off others. A checklist provides a repeatable method for logging the relevant details at the moment they occur rather than attempting to reconstruct them later. The approach works by isolating only those choices that produce measurable changes in companion availability or dialogue trees, allowing the record to remain manageable even after dozens of hours of play.
The goal is not to record every line of dialogue but to isolate the variables that actually influence companion availability, trust thresholds and joint story branches. This approach works best when applied from the first few hours onward, so the record grows alongside the campaign instead of being assembled in retrospect. Players must also decide in advance which companions receive priority in the checklist, since attempting to track every possible interaction quickly leads to an unreadable document. The following sections outline how to define the checklist items, when to update them and how to test their accuracy against observable game feedback.
Defining the Scope of What Needs Tracking
Begin by listing the companions who appear across multiple chapters and noting the specific interactions that can change their disposition. Focus on moments where the player must choose between supporting one companion’s request or another’s, or where the player’s stance on a faction directly involves a companion. Limit the checklist to these decision points rather than every conversation, because minor flavour text rarely produces lasting mechanical effects. Players should also consider whether a choice affects only one companion or creates ripple effects across several relationships at once, since the latter type usually warrants a separate entry to avoid confusion during later reviews.
Next, identify the observable outcomes that indicate a change has occurred. These might include altered greeting lines, new quest markers that only appear after certain thresholds, or differences in combat support behaviour. Write each outcome as a short, verifiable statement so it can be checked quickly during play without pausing the session for long. A common error at this stage is including every possible dialogue variation instead of restricting entries to those that demonstrably alter future availability or loyalty checks. The checklist remains useful only when its scope stays narrow enough to review in a few minutes before resuming play after a break.
Setting Up the Initial Checklist Columns
Create four simple columns: decision description, companion involved, immediate visible result and predicted long-term consequence. Keep the language concise so entries remain legible when the list is reviewed weeks later. For example, an entry might read “Supported companion A over faction request – immediate: companion A offers extra supplies; predicted: higher loyalty in final act confrontation.” Adding a fifth column for the chapter number helps when the same companion appears in multiple story arcs and the player needs to locate the original context quickly.
Print or save the template before starting a new campaign so the format is already available when the first relevant choice appears. Avoid adding extra columns for speculation; the checklist should capture only what has been confirmed by the game’s own feedback systems. Another frequent mistake is leaving the predicted consequence column blank, which defeats the purpose of forward planning. Filling it with a brief note based on the current situation provides a clear benchmark against which later observations can be compared without relying on memory alone.
Updating Entries During Active Play
After each major story segment, spend a few minutes comparing the checklist against current companion behaviour. If a previously predicted consequence has become visible, move the entry into a “confirmed” section rather than leaving it in the active list. This prevents the document from growing unwieldy and keeps attention on unresolved items. Players should also note any unexpected outcomes that contradict earlier predictions, because these discrepancies often reveal hidden conditions such as prior choices with other characters that the checklist had not yet captured.
When a companion leaves the party temporarily, note the exact chapter and decision that triggered the departure. On their return, check whether prior entries still match the new dialogue or whether an unrecorded factor has altered the outcome. Adjust the checklist wording only when the game itself demonstrates that the original assumption was incomplete. A useful practice is to mark entries with a simple status tag such as “open,” “confirmed,” or “revised,” which allows quick scanning before the next session without rereading full descriptions each time.
Reviewing the Checklist After Extended Breaks
Before resuming a campaign after several days or weeks away, read the most recent five entries aloud to refresh context. Pay particular attention to any companions whose loyalty status remains marked as “provisional.” These are the relationships most likely to produce unexpected branches once the story advances again. The review also serves as an opportunity to discard entries whose predicted consequences have already been resolved or rendered irrelevant by later events.
If the game offers a recap screen or journal, cross-reference it against the checklist rather than replacing the checklist with the game’s summary. The game’s recap often omits the precise wording of earlier choices that matter for companion trust calculations. A practical step is to keep a separate short list of the three or four most active companion threads so that attention remains focused during the first hour after returning, rather than attempting to absorb the entire document at once.
Testing Checklist Accuracy Against Observable Results
Run a short test by deliberately replaying a short section from an earlier save where a key decision was made differently. Observe whether the companion’s later behaviour matches the entry recorded for the original choice. If the outcome diverges, add a brief qualifier to the checklist explaining the additional condition that must also be met. This method works best when the replayed section is short enough to complete within one session and does not require redoing large portions of the campaign.
Limit these tests to sections that can be replayed quickly; otherwise the time cost outweighs the benefit. The checklist gains value only when it reduces uncertainty during the main playthrough, not when it becomes a project in its own right. Players should also avoid treating every divergence as a checklist failure; some differences arise from random elements or difficulty settings that the original entry could not have anticipated, so the focus remains on consistent, repeatable patterns rather than isolated anomalies.
Recognising When the Checklist Has Outlived Its Use
Once a companion’s final loyalty outcome is confirmed in the endgame sequence, archive the relevant entries rather than continuing to carry them forward. Retaining every historical note increases the chance that an outdated prediction will be mistaken for current fact during later replays. A clear signal that an entry is no longer needed is when the companion’s behaviour no longer changes regardless of further choices, indicating that the relationship has reached its maximum or minimum state.
At the end of the campaign, retain only the entries that produced measurable differences in multiple playthroughs. These form the basis for a shorter reference list that can be reused when starting a new game with the same title or a similar system. Over time the checklist evolves from a detailed log into a compact decision aid that highlights the few early choices still worth deliberate attention on subsequent runs. This final distillation prevents the accumulation of redundant notes while preserving the patterns that genuinely affect companion interactions across different campaigns.
What is your perspective?
Share a useful observation. Keep spoilers clearly signposted and follow our community guidelines.