A character with context
Choose the race, role, age, wealth, and campaign context. Develop motives, personality, and background at the level of detail you need.
Prepare
NPC Forge
Prepare the people and creatures your game needs.
NPC Forge helps you build a useful campaign cast: a merchant with something to hide, a household retainer, a travelling companion, or an encounter’s opposition. Keep their story, DragonQuest details, and appearance together so you can find them again next week.
What it helps you do
DragonQuest preparation
Review attributes, skills, magic, equipment, and currency alongside the narrative description.
Portraits and table tokens
Prepare an appearance, portrait, and cropped token without treating an illustration as proof of new powers.
A cast you can organise
Keep related NPCs in retinues and groups for households, factions, towns, and encounters.
Follow-up with a record
Review correspondence and story choices, and use recorded evidence when updating what an NPC knows or has done.
Getting ready
Decide what the NPC needs to do in the game before generating them. A contact, opponent, teacher, household member, and recurring ally need different amounts of detail. Bring the location, institution, faction, and established campaign facts that should shape the character.
Choose the relevant stable or collection and keep related people in a retinue. For an established NPC, start from their current record rather than rebuilding their known abilities from an uncertain biography. Missing historical information should remain a question to resolve, not an invitation to overwrite familiar ranks.
How to use NPC Forge
Set the creation brief
Choose race, archetype, wealth, age, and other supported character inputs. Select concise, balanced, or detailed presentation to suit the role. Add the campaign situation and any existing training or appearance requirements. A brief that explains why the players will meet this person produces a more useful starting draft.
Review the person behind the numbers
Read the background, motivations, personality, and current situation. Decide what the NPC wants, what might make them cooperate, and what they will resist. Adjust social details and portrayal so you can speak as the character without reading a page of exposition aloud. Save the decisions you intend to use.
Check DragonQuest readiness
Review attributes, skills, ranks, magic, equipment, armour, and currency where relevant. Keep narrative description separate from mechanical qualification: a fearsome portrait or impressive title does not establish a spell or combat ability. For a monster, inspect the encounter mechanics as well as the creature’s prose.
Prepare appearance and organise the cast
Choose or prepare a portrait and token, and use supported voice options when they help portrayal. Add the saved NPC to the appropriate retinue or encounter group. Keep the NPC’s reusable record available to Mentor and the table tools, rather than creating disconnected copies every time the person appears.
Use lore and played evidence to maintain history
Ask Lore about established places, factions, or references and inspect its cited sources. After a game, use the relevant Scribe passages to support changes to what the NPC knows or has done. Review the suggested fact before accepting it. A fluent answer, imported note, and refreshed live lore index are different stages.
Plan legal training and downtime
For progression, check the baseline, credited experience, funds, available time, teachers, and qualification evidence. Review only feasible training alternatives. Imported current ranks remain important evidence when historical starting values are missing. Where correspondence is enabled, the NPC’s voice should explain the saved options without changing their costs or granting extra abilities.
Handle a story-choice letter deliberately
A connected app can prepare an owned campaign NPC’s message with two or three distinct choices. Preview it, explicitly send it to the verified GM owner, and retain the choice record. Follow the link and confirm the answer; simply opening the email link or replying to the email does not select it. Review the returned outcome before applying it to the campaign.
A game example
A rival courier who becomes a recurring contact
For example, choose a courier’s race, role, wealth, and age, then explain the reason for their rivalry with the party. Review what they want and what would persuade them to help. Check the movement and skills needed for the encounter, save a portrait, and place them in the town retinue. If the party later earns their trust, accept that development from the reviewed session record. Subsequent training or story letters should start from that maintained character.
What you keep
A reusable NPC record
A reviewed story, game details, appearance, and group membership that can be used again in preparation and play.
An explainable history
Accepted evidence, participation, progression, and correspondence tied to the person rather than an unrelated generated biography.
Table and planning material
NPC context, portraits, tokens, and supported references for Mentor, households, encounters, and connected visual tools.
How it fits with the other apps
DQ GM Mentor
Bring the campaign cast into story cards and the plan for tonight.
About this appSeagate Households
Use prepared NPCs as household members and contacts between adventures.
About this appAdventure Scribe Notes Keeper
Check played-session evidence before accepting new facts into an NPC’s history.
About this appCommon questions
Does selecting an email choice automatically change the NPC?
It records the answer and can produce the authored follow-up. The consumer app still has to read that result and apply the intended consequence once. It does not automatically alter attributes or make every statement campaign canon. Story-choice letters are separate from training emails and forum conversations.
Can I leave all NPC training and board replies to automation?
The summary describes progression and correspondence machinery with enablement and pilot requirements. Check what is available in your setup and review consequential decisions. Automated NPC board exchanges remain in development; they are not an assumed feature of every retinue or community room.
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.