How to Use Components Without Overloading

You've discovered components and gone all in. 15 characters. 8 settings. A handful of tropes and writing styles. Your story has 30+ components attached and suddenly the AI is writing generic mush that ignores half your carefully crafted descriptions.

Here's what's happening and how to fix it.

What Happens When You Overload the AI

Every component you attach sends its full description to the AI alongside your chapter prompt, your Lorebook summaries, and the last chapter's text. The AI reads all of it and tries to honor everything at once.

When you stack too many components, you're giving the AI competing priorities. It can't focus on any single character or setting because it's trying to juggle 30 descriptions at the same time. The result: it defaults to surface-level writing that technically touches everything but does nothing well.

Aim for 3-5 Components Per Story

3-5 well-written components per story is where most users get the best results. That's usually:

• 2-3 characters (your main cast)
• 1 setting
• 1 writing style or trope

This gives the AI enough context to write with personality and depth without drowning in instructions.

"But My Story Has 10 Characters"

That's fine. Not every character needs to be a component attached to the story from the start. Think about who matters right now.

Active cast vs. full cast: Your story might have 10 characters total, but any given chapter probably focuses on 2-3. Keep your main cast as permanent Lorebook entries with detailed descriptions. For supporting characters, give them shorter descriptions that cover the basics.

Introduce characters as they appear. You don't need to load everyone at story creation. Add new characters to the Lorebook when they enter the story. Remove or simplify entries for characters who've left the stage.

Trim Your Lorebook as You Write

Your Lorebook is where you manage the active cast. Open it and look at what's there:

• Characters with thin descriptions that the AI isn't writing well? Beef up their entries or cut them if they're not needed.
• Characters who haven't appeared in 10 chapters? Consider removing their Lorebook entry. You can always re-add them later.
• Multiple settings described? The AI only needs the one your characters are currently in.

Think of the Lorebook as a spotlight, not a filing cabinet. Point it at what matters now.

One Rich Description Beats Five Thin Ones

One 200-word character description will outperform five 30-word descriptions every time. The AI does its best work when it has rich detail about a few things rather than shallow detail about many things.

If you have a character described as "tall, dark, dominant," the AI has almost nothing to work with. If you have one described with specific behaviors, speech patterns, physical tells, and emotional reactions, the AI writes them as a real person. For tips on writing strong character descriptions, see Characters 101.

Invest your detail budget in the characters and settings that carry your story.

Component Stacking That Works

Some combinations amplify each other:

Combo	Why It Works
2 characters + relationship dynamic in both descriptions	The AI picks up on the tension between them
Character + Setting	A character described as "uncomfortable in crowds" in a setting described as "a packed nightclub" creates natural conflict
Character + Writing Style	A brooding character paired with a "raw and visceral" writing style reinforces the mood
Trope + Writing Style	"Enemies to lovers" trope with a "slow burn" writing style gives the AI both the arc and the pacing

Component Stacking That Doesn't

• Multiple writing styles that contradict each other ("literary and poetic" + "raw and blunt")
• 10+ characters all attached as components with thin descriptions
• Redundant components that say the same thing (a setting component and the same setting described in your prompt)

Cut It or Improve It

If you can't tell the AI is using a component, it's either too vague to make a difference or it's getting lost in the noise. Cut it or improve it.

Less is more. A focused story with 3 great components will always read better than a crowded one with 20 generic ones. Browse ready-made components on the Discover page.