Web Novel Generator

Problem

Long-form web novels are hard to continue because outlines drift, chapter lengths vary, character voices break, and state files fall out of sync. Web Novel Generator targets male/female-oriented xuanhuan, system, isekai, urban, and other fast-paced long novels, and treats chapter-by-chapter progress plus persistent state as core constraints.

How It Works

It creates a new novel in two rounds: confirm title, genre, audience, one-line premise, cheat/system, and protagonist setup, then generate a 500+ chapter long-form outline with layered worlds, 12-15 major realms, 4-6 major arcs, volume-level highlights, and ending forecast. After chapter one is written, outline.md enters outline locking, and later changes require user confirmation.

Each chapter is constrained to 3000-10000 characters and must end with Character count: XXXX. After finishing a chapter, it updates:

• chapters/NNN.md: writes the new chapter
• state.json: syncs totalChapters, currentChapter, totalWords, lastUpdated, outlineLocked
• characters.md: records new or changed characters

Before continuing, it reads outline.md, characters.md, state.json, and the last 3 chapters to reduce context loss. It also handles common issues such as missing state files, missing chapters, missing outline, skipped chapters, character OOC requests, and under-length chapters, with confirmation or alternatives.

Boundaries

File operations are limited to novels/<book>/ and should not touch files outside that directory. It relies on plain text files and Node.js character counting, using UTF-8 and LF. Requests to change a locked outline, skip chapters, reorder chapters, or swap the protagonist are rejected or require double confirmation.