Import with review
Bring in supported sheets, documents, PDFs, or photographs. Accept known facts and retain unresolved material for later review.
Between games
DQ Characters
Keep character records, equipment, and training in order.
DQ Characters helps players and GMs maintain DragonQuest character records over a campaign. Bring existing sheets into a reviewable record, keep the party roster connected, and plan training without losing the source material behind a change.
What it helps you do
Useful character details
Keep identity, attributes, magic, ranks, inventory, encumbrance, and common buffs together with derived values.
Training with a record
Plan experience, money, time, prerequisites, and trainers, with GM approvals and a session ledger.
A connected roster
Link the party to the game so preparation and live tools use the intended character context.
Equipment and services
Receive linked Item Forge awards and use supported shop and guild-service workflows.
Getting ready
Choose whether you are creating a new character or bringing an existing one. An existing adventurer can begin with a name and unknown values, then be completed through manual entry or supporting documents. Partial saves let you work over several visits without filling gaps with invented starting statistics.
Select the intended character before importing, shopping, training, or connecting a game. Gather the current sheet and supporting evidence for exceptional attributes, magic items, or effects. An experienced character’s advancement should not be rejected merely because it does not fit an untouched creation-point budget.
How to use DQ Characters
Establish the character and its evidence
Create the record, enter supported identity, race, college, and statistics, and add skills, equipment, and biography as needed. Link or upload the existing material you want considered. Leave unknown movement or other missing details visible. Use explanation and source evidence for unusual values rather than quietly replacing them with plausible defaults.
Character wizard example: work through the creation steps, check background choices, and save the reviewed character. Review an import before applying it
Inspect the extracted facts, mapping, validation, blocked fields, and proposed changes. Accept only the facts you have checked, using the supported review or dry-run view first. A partial import should preserve fields the source did not contain: importing one wallet denomination or one defence value should not erase the rest of the record.
Understand the Virtual Character Sheet
Use the VCS to inspect accepted identity, attributes, magic, ranks, resources, inventory, encumbrance, and derived values. Check calculation explanations, loadout previews, source evidence, and unresolved findings. Keep a baseline value separate from an effective value changed by equipment or a temporary effect, so it can be recomputed when that effect ends.
Connect a familiar Google Sheet through Nexus
In Nexus, link the intended spreadsheet and tab, review the field map, and choose a selective pull when useful. Preview pulls or supported writeback and resolve conflicts before applying them. Inspect formulas, editable targets, and protected areas in your own sheet. A historical writeback rehearsal does not guarantee every custom layout is safe.
Plan and record training
Use Training Roadmap and Guild Guide to compare directions, then Training Assistant to preview EP, SP, weeks, prerequisites, trainer, and GM approval requirements. Start an eligible plan and log sessions using ordinary or campaign dates. Pause, resume, complete, or cancel through the recorded workflow, checking Training Ledger and Character Activity for the resulting trail.
Prepare possessions and practical services
Receive specific Item Forge awards, inspect inventory and storage, and review supported shop purchases with the correct character selected. Check quantity, price, stock, weight, and wallet effects. Use Guild Services to find a relevant treatment, research, training, translation, or other contact; a directory entry does not itself book or perform a service.
Share the right context with the game
Connect the character to the intended roster and campaign. Mentor can use party context, while Runtime and Viewer can use qualified movement and vision where supported. Check unresolved qualification before relying on an exported ability. Use the connected Households route for home life and downtime while keeping the accepted character record as the mechanical reference.
A game example
Bring an established character in without losing history
For example, import an experienced adventurer’s sheet with a magical item that affects a derived value. Review the accepted base statistic and the item’s source separately, leaving an unclear effect as a review task. Check the resulting VCS and equipment weight. Preview a training goal, find the appropriate Guild contact, and obtain any needed GM approval before logging the weeks. Link the reviewed character to the next game so the party context and qualified table capabilities agree.
What you keep
An accepted character record
A maintained VCS with baseline facts, derived values, inventory, evidence, and explicit unresolved questions.
A progression trail
Training previews, approvals, session logs, pauses, completion, and recent activity that explain how the character changed.
Reviewed connections
Sheet-sync history, linked game membership, received item awards, and qualified character context for the suite.
How it fits with the other apps
Common questions
Do I have to upload a sheet before I can use the app?
No. Manual entry is a supported path, and an existing character can be saved while incomplete. Add documents later when they help establish facts. Unknown values should remain visible instead of being invented to complete the screen.
Does a training cost preview mean I can start immediately?
Enough EP, money, and time may still leave a trainer, approval, quest gate, or other manual condition unresolved. Inspect the blockers and qualification. A numerical calculation is useful preparation, not automatic permission to gain every rank.
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.