A journal-based Quest, Faction, and Renown manager for Foundry Virtual Tabletop and the D&D 5e game system.

Create quest briefings and faction profiles, assign adventures to individual characters, award currency and items, record successes or failures, and track how each character or adventuring group is regarded by different factions—all without replacing Foundry's native Journals or D&D5e character sheets.

Current release: 0.0.9 · Interface language: English · License: MIT

Install the module · Get started · Quest workflow · Renown guide · Troubleshooting

The Reputation tab is designed for the native D&D5e Character and Group sheets. Third-party replacement sheets may not display the tab, even where the Reputation Manager remains accessible.

1. Open Foundry Setup → Add-on Modules → Install Module.

2. Paste this manifest URL into Manifest URL:

   https://github.com/hammer-PvP/Hammer-s-Quest-Renown/releases/latest/download/module.json
   

    

3. Install the module, then enable Hammer's Quest & Renown in your D&D5e World under Manage Modules.

4. Log in as GM. The module creates or maintains its managed Journal folders automatically.

5. Open the Journal Directory to access its management tools.

You can also obtain release files from GitHub Releases.

Updating an existing World? Back up the complete World with Foundry stopped before updating. The module preserves existing managed Journal IDs, Actor Renown ledgers, quest outcomes, and payout history through its versioned migrations. A backup is still strongly recommended for a live campaign.

For a complete first Quest, follow this order:

1. Create a Faction. In the Journal Directory, select Factions. Name it, describe it, and optionally configure an emblem, rank thresholds, and GM-only notes. Save.
2. Create a Quest. Select New Quest, enter a title, choose the Faction, add its public briefing and objectives, then configure any rewards. Save. New Quests start as Unavailable.
3. Make the Quest Available. Open Quest Manager, find the Quest, and select Make Available.
4. Give it to your players. Select Quest Giving, choose eligible Characters, and confirm. Each new recipient starts with Accepted status.
5. Resolve each Character's outcome. Use Quest Turn-In for success or Fail Turn-In for failure. The two actions are independent; one Character may complete the Quest while another fails or is still working on it.
6. Finish the Quest when appropriate. Select Finish Quest to move its Journal to Finished. This does not automatically mark unfinished Characters as Failed.

When logged in as GM, the Journal Directory adds four buttons:

Managed Quest and Faction Journals also have an Edit Quest / Faction control for GMs. A supported D&D5e Character or Group sheet provides Reputation access through its custom tab or a header control where available.

The module uses two managed root folders:

Journal Directory
├── Hammer's Factions
│   ├── The Eastern Council
│   └── Guardians of the Vale
└── Hammer's Quests
    ├── Active
    │   ├── The Missing Silver
    │   └── The Lost Echo Blade
    └── Finished
        ├── Danger in the Skies
        └── The Broken Oath

• Hammer's Factions: Faction Journals are stored separately from Quests.
• Active: Quests whose global status is Available or Unavailable.
• Finished: Quests the GM has administratively finished (internally Inactive), whether Characters succeeded, failed, or still have unfinished records.
• A Quest's owner Faction is stored as a reference, not a folder. A Quest can affect other Factions through its rewards or penalties.

Important: each Quest is one shared native Journal, and a native Journal has only one physical folder. Its location reflects the GM's global administrative status, not the result of any single Character. Finished can therefore contain mixed individual outcomes.

Finishing a Quest does not fail pending Characters, take away Renown, revoke a previous success, or issue any other reward. The GM can use Fail Turn-In on a Finished Quest to resolve remaining Characters as Failed. To resume successful Turn-Ins, use Reopen (Available) first.

Select Factions in the Journal Directory to create or edit a Faction.

A Faction has:

• Name and public description for its native Faction Profile Journal page.
• An optional emblem/image, selected with Foundry's built-in File Picker.
• Renown ranks with configurable minimum thresholds. Thresholds can be negative; each Faction has its own rank scale.
• A separate GM Notes page for secrets, NPCs, and campaign information.

The default ranks are:

These are editable defaults, not fixed rules.

Faction discovery: a Character or Group gains a recorded relationship with a Faction when it receives its first Renown ledger entry for that Faction. A zero-point manual adjustment is a useful way to establish a known Faction without changing the balance. Eligible Players receive read-only access to Faction profiles associated with their known Characters or Groups.

Select New Quest or Quest Manager → Create Quest.

The Quest Editor lets the GM configure:

• Quest name and owner Faction (an existing Faction is currently required).
• Flavor Text for the public Quest Briefing.
• Objectives, with checkboxes in the editor; these are shared Quest fields, not separate per-Character objective trackers.
• Currency rewards: Platinum, Gold, Electrum, Silver, and Copper pieces.
• Item rewards: drag Items from the World or Compendiums and set a quantity.
• Renown rewards: add separate signed Renown amounts for multiple different Factions. These do not need to match the owner Faction.

Players can read the public Quest Briefing, objectives, and announced success rewards when their User has access to the Journal. Item links can use Foundry's native UUID handling, with tooltip details where accessible.

The Quest Editor also has:

• Failure Penalties, disabled by default. When enabled, define negative whole-number Renown changes against one or more Factions. These values are not published in the public Quest Briefing.
• GM Notes, stored in a separate protected Journal page rather than in the public page.

After a Success Turn-In, reward definitions are locked to protect previously issued per-Character rewards. After a Failure Turn-In, failure penalty definitions are likewise locked to protect existing failure records. Plan changes before issuing the first corresponding Turn-In.

A new Quest is saved Unavailable with no assigned Characters. Use the Quest Manager to change its availability and distribute it.

Open Quest Manager to search by Quest name, Faction, or status. Each Quest displays its global availability, count of assigned Characters, and counts of active, completed, and failed Characters.

1. Make the Quest Available.
2. Select Quest Giving.
3. Select the Characters who should receive it; Select All and Clear Selection are available.
4. Confirm to mark each newly assigned Character Accepted.

A Character is eligible for Quest Giving only if it is a character Actor with an explicit Owner permission for at least one non-GM User. Merely belonging to a Group does not make a Character eligible. You may assign additional eligible Characters later, even if other Characters already completed the Quest. An already assigned Character cannot be given the same Quest twice.

The module grants eligible recipients Observer access to the Quest Journal, not Owner access. It does not assign Quests automatically to Groups.

Use Quest Turn-In on an Available Quest:

1. Select the assigned, unfinished Characters who completed the Quest.
2. Review the configured rewards. Each selected Character receives the full currency amount and full Item quantities, directly into that Character's inventory.
3. Choose whether each configured Faction Renown line targets Characters, Groups, or both.
4. Optionally check Represented Groups drawn from the selected Characters' D&D5e Group memberships. Groups are never preselected.
5. Confirm Complete & Grant Each.

Each selected Character receives its own personal Renown amount for the relevant reward rows. An explicitly selected Group Actor receives the configured collective Renown once per Quest, rather than once per member. Currency and Items are Character rewards; Groups do not receive those items or coins through this operation.

A Character's Completion does not finish the Quest globally. Other assigned Characters can complete it later and receive their own rewards. Payout records help prevent duplicate distribution if an operation must be resumed.

Use Fail Turn-In on an Available or Finished Quest:

1. Select the assigned Characters who failed.
2. Review any enabled Failure Penalties.
3. Optionally select eligible represented Group Actors, and choose Character/Group targets for each penalty row.
4. Confirm Mark Failed.

The selected Characters become Failed. If no Failure Penalties were enabled, only the outcome changes. If configured, the module applies the selected negative Renown changes. It does not issue success currency, items, or success Renown. Group penalties are never automatic.

A previous Completed outcome is not overwritten by Failure Turn-In.

The Undo Failure action is GM-only and is intended for accidental Failure Turn-Ins.

1. Open the affected Quest in Quest Manager and select Undo Failure. It is also accessible from View Results where applicable.
2. Select the incorrectly Failed Characters; use Select All Failed for a batch correction.
3. Optionally choose Group penalty corrections when the affected Groups are eligible for reversal. Group correction is independent from Character selection.
4. Enter a required reason and confirm.

For the selected Characters, the module restores the previously recorded unfinished state where available, or Accepted for older failures without a prior-state record. Assignments and Journal access remain intact. Applicable Renown penalties receive compensating positive ledger entries; original transactions remain in the audit history. The correction is designed to avoid compensating the same penalty twice.

Undo Failure does not reopen a globally Finished Quest. If those Characters should successfully turn in the Quest afterward, select Reopen (Available) separately.

Undo Failure is not a general Undo Success function. Do not use it to try to withdraw currency, items, or Renown from a previously Completed Character.

The GM can open View Results to inspect individual Character statuses, completed Turn-Ins, Failed Turn-Ins, selected Groups, Renown effects, and recorded failure corrections. Results are read-only and preserve historical records.

• Finish Quest moves the Journal to Hammer's Quests / Finished and keeps every Character's current result intact.
• Reopen (Available) returns it to Hammer's Quests / Active; a previous Completed or Failed result does not reset just because the Quest was reopened.

Renown is recorded per Actor and per Faction. A Character's reputation is independent from the reputation of a Group Actor, even if the Character is a Group member.

On supported D&D5e Character and Group sheets, open Reputation to see each known Faction's:

• Name
• Current rank
• Current Renown and the Faction's maximum rank threshold, displayed compactly as current / max

A Character sheet shows only that Character's personal Renown. A Group sheet shows only that Group Actor's Renown. Balances are not automatically combined, inherited, or shared.

Open Renown from the Journal Directory, or Manage from a supported Reputation tab.

GM capabilities include:

• Select one or many Characters using checkboxes, search, and Select All/Clear controls.
• Select Group Actors separately; selecting a Character never automatically selects their Group.
• Choose a Faction and enter a positive, negative, or zero whole-number adjustment.
• Enter a required reason and review the projected balance for each selected Actor before recording.
• Inspect a Character's or Group's existing Factions and history without changing the selected adjustment recipients.
• Review the five most recent events or open the full, paginated history.

Each recipient receives the full amount entered. For example, a +5 adjustment applied to three Characters gives +5 to each, not a total of five points distributed among them.

Players can view their permitted reputation information, but only the GM can change Renown.

Players continue using Foundry's native Journal Directory and supported D&D5e Actor sheets.

• Quest Journals are read-only and shared with Players whose Users explicitly own assigned Characters.
• Public Quest pages show the briefing, objectives, assigned Characters, and announced rewards.
• A personalized panel shows Quest Accepted, Quest Completed, or Quest Failed for the selected Character. Completed uses a simple green check seal; Failed uses a red cracked-X seal.
• If a User owns multiple assigned Characters, the panel offers a Character selector to switch the displayed outcome.
• Faction profiles become readable when an eligible Character or Group has a Renown record for that Faction.
• Private GM Notes remain hidden, and optional Failure Penalties are not listed in the public Quest Briefing.

Permission model: Foundry Journal permissions belong to Users, not individual Characters. The Character selector personalizes the result panel; it is not an independent, Character-level security boundary. A User who owns several Characters may be able to access a shared Quest Journal through any one of them.

This module stores Quest and Faction data in native JournalEntry documents, and Renown history in Actor flags. It does not require a separate database, duplicate a Journal for each recipient, or depend on Character Builder.

To keep a campaign safe:

1. Back up before updating, particularly if the World already contains paid Quests or reputation history.
2. Avoid having multiple GM clients run the same Turn-In or batch adjustment at the same time. Foundry document changes across multiple Actors are not an atomic database transaction.
3. If an operation was interrupted, use the relevant Resume option in the module instead of repeating it as a new operation or editing flags manually.
4. Use View Results and the Reputation history to audit awards, penalties, and corrections.
5. Use Finish Quest, Fail Turn-In, and Undo Failure for their separate purposes; one does not implicitly perform the others.

Versioned migration logic is included for the module's existing managed campaign records. The Active/Finished filing also preserves native Quest Journal IDs and moves only documents identified as belonging to the module.

If you encounter a bug, include your Foundry version, D&D5e system version, module version, and relevant console messages in a GitHub issue. Please avoid posting private campaign data or player information publicly.

• A new Quest requires an existing Faction as its owner. Standalone factionless Quests are not supported yet.
• Quest progress and Turn-In outcomes are individual per Character; Group membership does not automatically copy personal progress or Renown.
• Objectives belong to the shared Quest document; independent per-Character objective completion is not provided.
• Failure Penalties currently affect Renown only. Automatic currency deductions and Item removal are not part of Failure Turn-In.
• Undo Failure is supported; automatic reversal of a successful Turn-In's currency and Items is not.
• No built-in automatic quest prerequisites, quest chains, or rank-based perks.
• The native Journal folders Active and Finished express global Quest administration, not personalized folders per player.

For version-specific changes, see GitHub Releases. This README is a feature and usage guide, not a changelog.

Hammer's Quest & Renown is developed by Hammer and released under the MIT License.

Designed for Foundry Virtual Tabletop and the D&D5e system. These are separate projects and are not bundled with this module.