What are Important Story Details?

Adventure Awaits

Master Your QuestSmith Memory & Context

Creating a high-quality adventure in QuestSmith requires a strategic balance between immediate action and long-term consistency. By utilizing our Memory System and Context Management tools, you ensure the AI remains sharp, logical, and focused throughout your entire story.

Categorizing Important Story Details

To keep your story consistent, you must decide where each piece of information lives. QuestSmith uses three primary layers to organize facts:

The Prompt: Use this for tone, writing style, player role, and the immediate opening situation.
Story Cards: These are for stable facts—things that don't change often. This includes NPC biographies, faction lore, major locations, and the rules of magic or technology.
Memory: This is for dynamic changes—the impact the player has on the world. This includes discoveries, broken promises, betrayals, and the consequences of earlier choices.

The Memory System: Continuity That Matters

The Memory System acts as the AI's “long-term journal.” Its job is not to repeat the transcript, but to distill complex events into actionable facts.

The player discovered a hidden cult symbol in the Whispering Woods.
Marcus now distrusts the player after they refused to pay the debt.
The player currently holds the stolen Royal Seal.

Pro-Tip: Always focus on facts over mood. Mood is handled by your AI Instructions; Memory should focus on the “What” and “Who.”

Managing Story Context Like a Pro

“Context” is the total amount of information the AI can process at once. If you try to stuff your entire world into one massive prompt, the AI will likely drift, repeat itself, or ignore your plot structure.

The QuestSmith Context Strategy:

Distribute the Weight: Use Story Cards for your deep lore. They only “activate” (take up space) when their trigger words appear in the story.
Use Beats for Direction: Instead of telling the AI the whole plot upfront, use Beats to give the AI instructions for just the current scene.
Milestones for Progress: Use Milestones to track when it's time to move to the next chapter, clearing out the “immediate” memory of the previous scene to make room for the new one.
Calibrate Response Length: Adjust your response length settings based on the scene's importance. A high-stakes dialogue needs more “room” than a quick travel sequence.

Putting It All Together: The Mystery Example

If you are building a QuestSmith Mystery, your context management should look like this:

The Prompt: Establishes a “Dark Noir” tone and the player's role as a disgraced detective.
Story Cards: Define the “Silver Lily Syndicate” and the “Mayor’s Office.”
Beats: Provide the AI with one clue to reveal per scene (e.g., “Reveal the bloody handkerchief in the office”).
Memory: As the player finds the handkerchief, you (or a script) update Memory: “The player found the handkerchief with the Mayor’s initials.”

Result: In a later scene, the AI will see that memory and allow the player to confront the Mayor with actual evidence, rather than just guessing.

Core Principle: The strongest QuestSmith stories feel completely open and reactive to the player, but are supported by a carefully planned architectural structure underneath.

What are Important Story Details?

Adventure Awaits

Master Your QuestSmith Memory & Context

Categorizing Important Story Details

To keep your story consistent, you must decide where each piece of information lives. QuestSmith uses three primary layers to organize facts:

The Prompt: Use this for tone, writing style, player role, and the immediate opening situation.
Story Cards: These are for stable facts—things that don't change often. This includes NPC biographies, faction lore, major locations, and the rules of magic or technology.
Memory: This is for dynamic changes—the impact the player has on the world. This includes discoveries, broken promises, betrayals, and the consequences of earlier choices.

The Memory System: Continuity That Matters

The Memory System acts as the AI's “long-term journal.” Its job is not to repeat the transcript, but to distill complex events into actionable facts.

The player discovered a hidden cult symbol in the Whispering Woods.
Marcus now distrusts the player after they refused to pay the debt.
The player currently holds the stolen Royal Seal.

Pro-Tip: Always focus on facts over mood. Mood is handled by your AI Instructions; Memory should focus on the “What” and “Who.”

Managing Story Context Like a Pro

The QuestSmith Context Strategy:

Distribute the Weight: Use Story Cards for your deep lore. They only “activate” (take up space) when their trigger words appear in the story.
Use Beats for Direction: Instead of telling the AI the whole plot upfront, use Beats to give the AI instructions for just the current scene.
Milestones for Progress: Use Milestones to track when it's time to move to the next chapter, clearing out the “immediate” memory of the previous scene to make room for the new one.
Calibrate Response Length: Adjust your response length settings based on the scene's importance. A high-stakes dialogue needs more “room” than a quick travel sequence.

Putting It All Together: The Mystery Example

If you are building a QuestSmith Mystery, your context management should look like this:

The Prompt: Establishes a “Dark Noir” tone and the player's role as a disgraced detective.
Story Cards: Define the “Silver Lily Syndicate” and the “Mayor’s Office.”
Beats: Provide the AI with one clue to reveal per scene (e.g., “Reveal the bloody handkerchief in the office”).
Memory: As the player finds the handkerchief, you (or a script) update Memory: “The player found the handkerchief with the Mayor’s initials.”

Result: In a later scene, the AI will see that memory and allow the player to confront the Mayor with actual evidence, rather than just guessing.

Core Principle: The strongest QuestSmith stories feel completely open and reactive to the player, but are supported by a carefully planned architectural structure underneath.

Master Your QuestSmith Memory & Context

Categorizing Important Story Details

To keep your story consistent, you must decide where each piece of information lives. QuestSmith uses three primary layers to organize facts:

The Prompt: Use this for tone, writing style, player role, and the immediate opening situation.
Story Cards: These are for stable facts—things that don't change often. This includes NPC biographies, faction lore, major locations, and the rules of magic or technology.
Memory: This is for dynamic changes—the impact the player has on the world. This includes discoveries, broken promises, betrayals, and the consequences of earlier choices.

The Memory System: Continuity That Matters

The Memory System acts as the AI's “long-term journal.” Its job is not to repeat the transcript, but to distill complex events into actionable facts.

The player discovered a hidden cult symbol in the Whispering Woods.
Marcus now distrusts the player after they refused to pay the debt.
The player currently holds the stolen Royal Seal.

Pro-Tip: Always focus on facts over mood. Mood is handled by your AI Instructions; Memory should focus on the “What” and “Who.”

Managing Story Context Like a Pro

The QuestSmith Context Strategy:

Distribute the Weight: Use Story Cards for your deep lore. They only “activate” (take up space) when their trigger words appear in the story.
Use Beats for Direction: Instead of telling the AI the whole plot upfront, use Beats to give the AI instructions for just the current scene.
Milestones for Progress: Use Milestones to track when it's time to move to the next chapter, clearing out the “immediate” memory of the previous scene to make room for the new one.
Calibrate Response Length: Adjust your response length settings based on the scene's importance. A high-stakes dialogue needs more “room” than a quick travel sequence.

Putting It All Together: The Mystery Example

If you are building a QuestSmith Mystery, your context management should look like this:

The Prompt: Establishes a “Dark Noir” tone and the player's role as a disgraced detective.
Story Cards: Define the “Silver Lily Syndicate” and the “Mayor’s Office.”
Beats: Provide the AI with one clue to reveal per scene (e.g., “Reveal the bloody handkerchief in the office”).
Memory: As the player finds the handkerchief, you (or a script) update Memory: “The player found the handkerchief with the Mayor’s initials.”

Result: In a later scene, the AI will see that memory and allow the player to confront the Mayor with actual evidence, rather than just guessing.

Core Principle: The strongest QuestSmith stories feel completely open and reactive to the player, but are supported by a carefully planned architectural structure underneath.