What it does
Quest Generator creates RPG-style quest ideas with objectives, challenges, rewards, and story hooks. It is intended for use with tabletop role-playing games, including D&D, as well as video-game and other tabletop-RPG projects. The result is a prompt-driven starting point rather than a rulebook or a complete game master: the tool takes a textual direction and develops it into a quest premise that can be adapted to a campaign, one session, or an in-game assignment.
The tool presents the text that will be sent to its generation service under the label Prompt being sent. It then calls the /tools/ai-generator backend endpoint to produce the quest. The interaction itself takes place in the browser, but generation is not entirely client-side because the prompt is sent to a backend. The implementation uses plain browser APIs and does not rely on a separate client-side library. A built-in sample is available for exploring the tool, and a result can be copied to the clipboard. Output is not updated live while typing, so the user must explicitly request generation.
When to use it
- Start a tabletop campaign: Give the generator a setting, conflict, faction, or theme, then use the resulting objectives, challenges, and rewards as the basis for a session.
- Fill an empty quest slot: Use it when a game master needs a quick side quest that connects to an existing setting but does not require a fully authored adventure.
- Develop a video-game side activity: Describe the desired player role, location, or difficulty, then adapt the generated quest into objectives and completion conditions.
- Create reusable quest prompts: Ask for several versions of the same concept and use Regenerate with a different angle when the first result is too familiar or does not fit the intended tone.
- Brainstorm rewards and story hooks: Prompt for a quest around a particular weakness, such as a missing heir or a dangerous artifact, and extract the reward and follow-up ideas that can be introduced later.
- Prepare alternatives for multiple players: Generate quest concepts for different character levels, party compositions, or play styles, then select the version that best matches the group.
- Explore the interface with built-in material: Use the sample quest to see how a prompt is turned into a quest before writing a direction of your own.
How to use it
- Open the tool and review the sample. The tool ships with a built-in example, so you can inspect the expected input-and-output relationship without starting from a blank page.
- Enter or paste a quest direction. Describe the subject of the quest in the text-entry interface. A JSON file, saved document, or other file cannot be supplied because the tool has no file input and does not support opening files.
- Make the prompt concrete. Include the kind of setting, conflict, intended audience, or desired quest shape that matters. For example, specify that you want a wilderness escort quest with a moral complication rather than merely asking for a random adventure.
- Review the generated prompt. The text submitted for generation is identified as Prompt being sent. Check that it reflects what you intended and does not contain wording you would rather omit.
- Request the quest. The output does not update as you type, so use the interface’s generation action once the prompt is ready. The tool’s request-generation control is not given a specific text label in the interface description.
- Read and adapt the result. Look for a clear objective, a meaningful challenge, a reward, and at least one story hook. Add campaign-specific names, locations, non-player characters, and rules as needed; the generator does not automatically incorporate material from a file.
- Copy what you want to keep. Use the available copy action to put the generated result on the clipboard for pasting into a campaign note, design document, or game session. If the angle is unsuitable, select Regenerate with a different angle to request another version.
Worked example
Suppose you are preparing a D&D-style wilderness session for a party that has agreed to escort a wounded surveyor across a mountain pass. The complication is that the surveyor carries a map that could expose the location of a hidden sanctuary. A useful prompt would be:
Create a wilderness escort quest for a small adventuring party. The travelers must guide a wounded surveyor across a mountain pass, but the surveyor carries a map to a hidden sanctuary. Include a clear objective, a noncombat challenge, a combat threat, a reward, and one story hook that could lead to a later adventure.
After requesting generation, the expected result should be a quest built around those elements. For example, the main objective could be to keep the surveyor alive and reach the pass before his condition worsens. The noncombat challenge could involve reading broken trail markers and deciding whether to cross an exposed ridge or take a longer, safer route. The combat threat could be a pack of territorial predators drawn to the surveyor’s blood or the map-bearing equipment.
The reward should connect to the requested premise rather than being an unrelated treasure. It could include the surveyor’s trust, payment, and partial access to the map after the sanctuary’s location is verified. The story hook can then introduce a second opportunity: the map identifies someone other than the party’s employer who also wants to reach the sanctuary. That follow-up gives the game master a way to continue the scenario without treating the escort as a completely isolated errand.
The exact wording will vary, but a suitable response should still address the prompt’s five requested parts: objective, noncombat challenge, combat threat, reward, and story hook. If the generated version loses the moral connection between the map and the sanctuary, refine the prompt or use Regenerate with a different angle. Copy the result once it fits your notes, then add the names, distances, character details, and rules required for your actual game.
Limitations and edge cases
- There is no file-based workflow. The tool cannot open or upload a campaign document, setting bible, character sheet, map, or saved quest. You must paste the relevant text into the prompt yourself. Use a different tool or your normal document system when you need extensive source material to be analyzed automatically.
- Generation requires a backend request. Although the interface runs in the browser, the tool calls /tools/ai-generator rather than generating entirely on the local device. The prompt is therefore transmitted to the service for processing. The tool does not state that the generated quest is stored between visits.
- Output is not live. The result does not update continuously while you type, and there is no automatic run. You must request generation after changing the prompt.
- State is not remembered. The tool does not use local storage to preserve prior prompts or results. Keep important output by copying it to the clipboard and placing it in your own notes.
- There is no direct download. The result can be copied, but the tool cannot save it as a downloadable file. If you need a standalone document, paste the copied result into a text editor or document application and save it there.
- No numeric limits are published. The tool does not state a maximum prompt length, output length, generation count, or other numeric limit. That does not guarantee unlimited input; it means there is no documented threshold to plan against.
- Generated content may need adaptation. The result is a creative prompt response, not a rules-validated adventure module. It will not automatically contain the statistics, encounter balance, treasure values, legal constraints, or campaign continuity required for your table. A campaign-management tool is better for structured timelines and connected records.
Troubleshooting
- Problem: The generation request fails with “Insufficient credits.”
Fix: The account has too few credits to run the request. Use the credit system described by the tool to obtain more, then try the request again. - Problem: The tool displays “Insufficient credits. Visit /rewards to get more.”
Fix: Follow the stated route to /rewards and add credits before submitting the prompt again. - Problem: The quest ignores an important part of the prompt.
Fix: Make the missing requirement more explicit, remove competing instructions, and request another generation. You can also select Regenerate with a different angle if the existing result needs an alternative interpretation. - Problem: The output is too short or too general for a campaign.
Fix: Add the required structure directly to the prompt, such as asking for a distinct objective, challenge, reward, and story hook. Use a separate writing tool if you need extensive prose, editing, or a fully formatted adventure. - Problem: A previously generated quest is gone after leaving the page.
Fix: The tool does not remember state between visits. Copy the result before navigating away and save it in your own notes or document application. - Problem: You want to use existing campaign material as the input.
Fix: The tool cannot open a file. Copy the necessary text and paste it into the prompt. For large source collections, use a tool designed for document upload and analysis.
Frequently asked questions
Does the quest run entirely on my device? No. The interface is in the browser, but the tool calls the /tools/ai-generator backend endpoint to create the quest. The prompt is sent to that service.
Can I keep a generated quest between visits? The tool does not use local storage and does not remember its state between visits. Copy the result and save it in your own notes if you want to retain it.
What file types can I upload? None. The tool has no file input and accepts no file types. It works with text that you type or paste into the interface.
Can I download the generated quest? No. There is no download feature. You can copy the result to the clipboard and paste it into a document application if you need to save it as a file.
Does the output change while I type? No. The tool does not update the output live and does not run automatically. You must request generation after entering or changing the prompt.
Is there a published prompt or output length limit? No numeric limit is published. The interface does not state a maximum length, so do not assume a particular threshold is guaranteed or guaranteed to be rejected.
What happens if I do not have enough credits? The tool reports “Insufficient credits.” Its fuller message is “Insufficient credits. Visit /rewards to get more.”
When should I use a different tool? Use a document-based assistant for large uploaded source materials, a writing application for long-form editing and file export, or a structured campaign-management tool for timelines, character records, and mechanically balanced encounters. Quest Generator is best suited to producing a concise, prompt-directed quest concept with objectives, challenges, rewards, and story hooks.