A household around a character
Connect household members and retinues to the character, with abodes, languages, city, and guild context.
Between games
Seagate Households
Keep home life, contacts, and downtime connected to the campaign.
Seagate Households gives characters a place between adventures. Work with household members, contacts, living arrangements, and downtime, keeping the outcome of conversations distinct from promises that still need to be carried out.
What it helps you do
Talk with contacts
Use supported NPC text and voice conversations to explore household matters and follow-up.
A history between adventures
Keep dated adventure history and gaps in view when working through downtime and weekly catch-up.
Practical downtime choices
Review training, risk stance, money, and living standards alongside the household’s circumstances.
Reviewed NPC letters
Prepare a campaign NPC’s letter with choices, preview it, and explicitly send it through the connected correspondence workflow.
Getting ready
Open the intended character’s household and check its owner, abode, location, and assigned companions. Bring the character’s dated adventure history into view before processing a gap between expeditions. The home and retinue give conversations context; they are not a separate character-mechanics authority.
Decide which interactions are ordinary roleplay and which need a GM-approved outcome. A promise, generated report, completed task status, and confirmed reward are different facts. Richer persistent NPC memory is described as local or pilot work, so check its availability before depending on it across sessions.
How to use Seagate Households
Arrange the abode and household cast
Use the household workspace to select or maintain the location, map, portrait, saved positions, and assigned NPCs. Recruit or assign eligible companions through the supported ownership workflow. Check that people belong to the right character and household rather than assuming every NPC in a shared collection is yours to employ.
The project’s middle living-standard house plan provides a concrete setting for residents, household tasks, and between-game roleplay. Talk with a particular companion
Select the NPC and use supported text or voice conversation. Their personality, background, motivations, morale, helpfulness, brevity, and household circumstances shape the interaction. Ask a concrete question or discuss a task. Keep the conversation’s statements distinct from accepted game events, particularly when an NPC proposes a future action.
Assign work and review its report
Where supported, give the companion a task and follow its start, end, and in-progress or completed status. Read the later report or available audio. Treat the report as what the NPC says happened, then confirm any discovery or consequence as appropriate. Finishing the task does not automatically award a reward or resolve an adventure.
Select the actual gap between adventures
Review the older adventure’s end and the next adventure’s start. Enter Catchup for that dated period instead of processing an arbitrary unlabelled week. Check how many weeks are available and how many are already accounted for by training or previous catch-up. Correct missing or invalid chronology before treating the period as usable downtime.
Work through downtime choices
Review SP available or at risk, living standard, household costs, and cautious or daring risk stance. Process a week and inspect its finances and activity log. Continue only through the available gap, keeping processed and training weeks consistent. The choices affect opportunities and misfortune in the supported simulation; generated narrative still needs appropriate campaign review.
Compose a reviewed household letter
A verified GM can choose an eligible owned NPC in Stories, write a short letter with two or three distinct options, and preview it. Confirm sending explicitly through Forge’s shared correspondence workflow. Keep the letter identity, check delivery and answer separately, and record the selected choice once. Editing the letter’s content requires a new event rather than silently changing an already sent choice.
Carry accepted outcomes back to the character
Review the household’s reports, dated logs, and chosen answers alongside the character’s history. Record the accepted consequences in the appropriate campaign or character workflow. Do not treat a narrative promise as completed training, income, or an inventory award. Check the corresponding mechanical record when an outcome affects those values.
A game example
Use the weeks at home between two expeditions
For example, select the dated interval between a character’s return and the next departure. Check training weeks, choose a living standard and risk stance, then review one catch-up week at a time. Ask a household companion to investigate a local matter and inspect their later report. If the GM wants a choice about what to do next, prepare and preview a letter. Keep the accepted answer and confirmed results separate from the companion’s unverified claims.
What you keep
A maintained household
The abode, location, companion assignments, and relevant conversation or task context for the character.
Accounted-for downtime
Dated periods, processed weeks, training use, financial changes, and activity logs you can inspect later.
Reviewed correspondence
Frozen letter content, send and delivery state, and a retained chosen answer tied to the eligible campaign NPC.
How it fits with the other apps
Common questions
Will an NPC automatically remember every conversation?
Do not assume the richer long-term memory work is deployed for every household. The summary describes provenance, correction, and forgetting features with local or pilot limits. Preserve important accepted commitments and check the active setup rather than relying on an apparently confident recollection.
Is Stories here the same as Seagate Stories?
The household Stories surface manages owned-NPC letters and their answers. The separate Seagate Stories project is a narrative inspiration feed. A selected household answer does not automatically run skill checks, award rewards, or advance a complete branching adventure.
Usage guide based on the 7 October 2026 project summary, reviewed 8 October 2026. Examples illustrate possible games. Some connected features require sign-in, GM permissions, or a configured local table.