What are Acts, Arcs, and Beats?

Managing Your Context in QuestSmith

If your story is becoming incoherent, losing important details, or forgetting plot elements, you are likely running out of Context Space.

What is Context?

Context is the total amount of information the AI model can process in a single response. Measured in tokens (roughly 4 characters per token), this space is shared by your Adventure text, AI Instructions, Plot Essentials, Story Cards, and Memory.

Healthy Context vs. Unhealthy Context: Ideally, your Adventure History (the actual story text) should take up the most space. If a single component—like a massive Story Card or an oversized Prompt—soars above the rest, it “crowds out” the AI's ability to remember what happened five minutes ago.

Optimizing Your Structure (Acts, Arcs, & Beats)

The most common cause of context bloat is trying to put the whole plot into one prompt. Instead, use a structured hierarchy:

• Acts: Use these for the major phases (Setup, Escalation, Resolution).
• Arcs: Keep specific quest lines (e.g., “Find the Prince”) focused.
• Beats: This is the secret to context health. Use Beats to define only the current scene.

• A weak Beat might be: “The player explores the clinic.” (Too vague, AI might wander).
• A strong Beat might be: “The player searches the clinic and finds evidence the victims were moved.” (Focused, moves the story forward, and allows old context to be cleared once the beat is finished).

Trimming the “Required” Components

Certain parts of your story are Always-In-Context. If these are too bulky, your story will suffer.

• AI Instructions: Look for redundancy. Instead of saying “Ensure characters speak in their defined personality and never use generic tropes,” shorten it to: “NPCs speak befitting their personality.”
• Plot Essentials: Move non-essential info to Story Cards. Ask yourself: “Does the AI need to know this in every single scene?” If not, it doesn't belong in Plot Essentials.
• Author’s Note: Keep this as a “surgical strike.” Use it for immediate style shifts (e.g., Style: Slow-paced) rather than long paragraphs of rules.

Managing “Dynamic” Components (Story Cards & Memory)

Dynamic elements only take up space when they are triggered or needed.

• Story Cards: These occupy up to 25% of your available context.

• Check your triggers: Don't use broad triggers like Em for a character named Emily. It will trigger on Empire, Gems, and Them, wasting space.
• Let the AI fill the blanks: You don't need to describe every inch of an NPC's outfit. Tell the AI the “Vibe” and let it generate the small details.

• The Memory System: Memory should carry forward facts, not mood.

• Bad Memory: “The player felt uneasy.” (Vague, wastes space).
• Good Memory: “The player exposed the mayor's secret deal.” (A hard fact the AI can act on later).

Context Priority (What gets cut first?)

When your context fills up, QuestSmith removes information in a specific order. Knowing this helps you protect your most important details.

• Lowest Priority (Cut First): Story Summary. If your context is full, the AI stops reading the summary first.
• Second to Cut: AI Instructions. Long instruction lists will be truncated.
• Third to Cut: Plot Essentials. Detailed world descriptions start to disappear.
• Highest Priority (Never Cut): The Last Action. The AI will always see your most recent input and its most recent output.

The Context Checklist

• Is my Prompt focused on style and setup? (Leave the rest to cards).
• Are my Story Cards triggered by specific, space-separated words?
• Does my Memory Bank contain facts rather than descriptions?
• Am I using Beats to give the AI a clear goal for the current scene?

By distributing your story details across Beats, Story Cards, and Memory, you prevent the AI from depending on one oversized prompt, keeping your QuestSmith adventure sharp and coherent for hundreds of turns.