Learn NovelAI Practically
Configure story context and generation behavior deliberately, inspect what the model receives and revise every continuation for continuity, craft and originality.
What You Will Learn
Use NovelAI to manage model-facing story context, generation settings and retries while keeping continuity, authorship and final revision under human control.
Define the Story Mode and Intent
Choose Storyteller or text-adventure use, audience, genre, POV, tone, boundaries and intended generation behavior.
Build Efficient Layered Context
Separate persistent Memory, recent Author’s Note and conditionally activated Lorebook knowledge.
Inspect, Generate and Revise Deliberately
Use the Context Viewer, change one preset variable at a time, compare retries and rewrite chosen material yourself.
Review Responsibly
Inspect factual accuracy, authorship, citations, confidentiality, originality and every accepted change.
1What Is NovelAI?
Generation quality depends heavily on context, model and settings. The writer remains responsible for continuity, factual and cultural accuracy, originality, rights, privacy, storage and final language.
The L–O–R–E Method
Use this checklist to turn an idea into a reviewable sequence.
L — Lay Out Story Intent and Model
Choose story mode, model, genre, tags, POV, tone, content boundaries and desired behavior.
O — Organize Context Layers
Keep permanent facts in Memory, immediate guidance in Author’s Note and conditional knowledge in Lorebook.
R — Review Context and Generation Settings
Use Context Viewer and conservative presets to see what the model receives and how it behaves.
E — Evaluate Retries and Edit Yourself
Compare alternatives for continuity, craft and originality, then rewrite selected material.
Choose the Right NovelAI Capability
Names and availability can change by device, account and subscription.
| Capability | Best Use | Quality Check |
|---|---|---|
| Story Settings, Models and Presets | Choose model, story mode, genre or tags and generation behavior | Confirm current model support and change one setting at a time |
| Memory and Author’s Note | Supply persistent story facts and recent high-priority generation guidance | Keep entries concise, current, non-contradictory and placed in the correct layer |
| Lorebook | Activate character, location, object or lore knowledge through keys and context rules | Test keys, search range, placement, order, reserved tokens and accidental activations |
| Context Viewer and Context Settings | Inspect inclusion, order, token budget, trimming and source of model context | Confirm recent story text and essential entries are not displaced or truncated |
| Generate, Retry and Edit | Create continuations, compare alternatives and steer through prompt or context changes | Watch for loops, drift, repetition, broken POV, clichés and invented facts |
| Export, Storage and Recovery | Export story or scenario files, text or other supported formats | Understand local versus server storage, backup settings, retry trees and password-reset risks |
From Story Context to Controlled Continuation
Start only after story mode, genre, audience, POV, tone, boundaries, ownership, privacy and backup plan are clear.
1. Brief
Define story mode, genre, tags, POV, tone, scene goal, boundaries, privacy, storage and reviewer.
2. Create
Write the prompt, distribute facts across Memory, Author’s Note and Lorebook and save a baseline.
3. Refine
Inspect Context Viewer, select model and preset and generate several short continuations.
4. Finish
Compare retries, revise manually, export recoverable backups and document settings.
Learn through Controlled Editing Experiments
Keep a prompt-and-result log.
Experiment 1: Context-Layer Placement Test
Create one core premise, one temporary scene instruction and three character or location facts.
Place each item in Memory, Author’s Note or Lorebook according to persistence and activation needs.
Inspect Context Viewer and test whether intended information appears at the correct time.
Experiment 2: Lorebook Activation Test
Create entries with unique keys, overlapping keys and one deliberately risky common key.
Use controlled story snippets to trigger one entry, several entries and no entries.
Inspect inclusion, search range, order, token use and false activations.
Experiment 3: Preset Variable Test
Keep prompt, model, context and generation length fixed.
Change only one preset or generation setting across three trials.
Compare coherence, creativity, repetition, punctuation and edit effort.
Experiment 4: Retry-Tree and Recovery Test
Create a disposable story and generate several branches from one prompt.
Edit one branch, undo or retry where supported and export story and raw-text backups.
Verify what settings, context, Lorebook and retry history each format preserves.
Protect Facts, Rights, Privacy and Audience Trust
Sources and Permission
- Use text, data, images, logos and files you created or may legally use.
- Verify every important claim against authoritative sources.
- Do not expose confidential files, personal data or restricted brand material.
- Keep a source and permission record for client or public projects.
Access and Disclosure
- Set view, comment and edit permissions deliberately.
- Confirm tool, account and document-sharing settings before submitting sensitive text.
- Disclose AI assistance when context or policy requires it.
- Use specialist review for medical, legal, financial or other high-stakes content.
Create a Context-Controlled NovelAI Story
Produce an original scene using deliberate context layers, controlled generations, manual revision and recoverable backups.
Assignment: NovelAI LORE Sprint
Write a LORE plan covering mode, model, preset, genre, POV, tone, Memory, Author’s Note, Lorebook, privacy, storage and reviewer.
Create a 700–1,000 word original scene, distribute context deliberately and save a baseline before generation.
Test Lorebook triggers and one preset variable, compare retries, revise manually and verify exports.
Selection Questions
- Are mode, model, genre, audience, POV, tone and scene goal clear?
- Is each fact placed in the correct context layer?
- Do Lorebook keys activate only when intended?
- Were preset tests and retries compared under controlled conditions?
- Are continuity, originality, rights, privacy and backups verified?
Quality Score
- Brief alignment: ___ / 5
- Context control: ___ / 5
- Continuity and craft: ___ / 5
- Technical QA: ___ / 5
- Responsible use: ___ / 5
Mistakes Learners Should Avoid
Wrong Habits
- Overloading Memory and Author’s Note with duplicate or stale details
- Using broad Lorebook keys that activate accidentally
- Changing model, preset and context simultaneously
- Ignoring Context Viewer, token pressure and truncation
- Trusting retries without checking continuity and originality
- Relying on one copy without understanding storage or exports
Professional Habits
- Keep each context layer concise, current and purpose-specific
- Test Lorebook keys with controlled passages
- Inspect Context Viewer before important generations
- Change one generation variable at a time
- Compare retries and rewrite selected material yourself
- Export recoverable backups and document settings
Quick Quiz: NovelAI
Answer all ten questions and submit.
1. What is NovelAI primarily designed to support?
2. What does L mean in LORE?
3. Why should the Context Viewer be checked before generation?
4. What should be verified after creating a Lorebook entry?
5. What should a responsible creator protect?
6. What is the safest NovelAI workflow?
7. What should happen before sharing a NovelAI project or export?
8. What belongs in NovelAI project QA?
9. Should a retry be accepted automatically?
10. Why should current NovelAI plan and feature details be checked before production?
Remember These Four NovelAI LORE Rules
Review before moving to Tool 67.
1. Lay Out Intent
Define story mode, model, genre, POV, tone, goal and boundaries.
2. Organize Context
Separate persistent Memory, immediate Author’s Note and conditional Lorebook knowledge.
3. Review Before Generation
Inspect Context Viewer and settings, then change one variable at a time.
4. Evaluate and Edit
Compare retries, rewrite yourself and preserve recoverable exports.