Sākums Izpētīt Palīdzība
Pierakstīties
nonvioce
/
inkos
1
0
Atdalīts 0
Faili Problēmas 0 Izmaiņu pieprasījumi 0 Vikivietne
Koks: 6a2eb5c9a6
Atzari Tagi
inkos
/
docs
/
raw-genre-profiles.md

raw-genre-profiles.md 52 KB
Vēsture Neapstrādāts

Perfect. I now have comprehensive research across all the major genres. Let me compile the complete report:

COMPREHENSIVE GENRE PROFILES: ENGLISH WEB FICTION CONVENTIONS

EXECUTIVE SUMMARY

This research synthesizes conventions, rules, tropes, and reader expectations across seven major English web fiction genres. The analysis draws from Royal Road communities, author blogs, Reddit forums, publishing data, and successful case studies to establish what readers expect and what breaks reader engagement.

1. LitRPG (LITERARY ROLE-PLAYING GAME)

Core Definition

LitRPG is a literary genre combining computer RPG mechanics with narrative fiction, where game-like elements form an essential part of the story. Visible RPG statistics (strength, intelligence, damage) and explicit progression systems are significant parts of the reading experience.

Reader Contract

"I want to watch a character grow stronger through quantified, visible progression. I expect clear game mechanics, consistent system rules, and the satisfaction of seeing numbers improve. The system itself should be a character—rule-based, logical, and internally consistent."

Hard Rules (Break These and Readers Leave)

  1. System Consistency: Once established, rules cannot change arbitrarily. Readers will catch violations more reliably than you know your own system.
  2. Visible Progression: Stats, levels, and skill acquisitions must be apparent. Hiding them frustrates readers.
  3. Meaningful Power Curves: Progression that feels earned, not arbitrary. Too-fast progression bores; too-slow frustrates.
  4. No Unexplained Power Jumps: Character growth must follow established system logic.
  5. Respect Reader Game Knowledge: Many readers have played actual RPGs and will identify broken mechanics immediately.

Sub-Types and Their Distinctions

Crunchy vs. Lite LitRPG

  • Crunchy: Data-heavy, detailed stat sheets, complex skill trees, spreadsheet-like stat presentation. Appeals to seasoned gamers who want to understand the mathematics.
  • Lite/Creamy: Minimal mechanics, narrative focus over numbers, accessible to non-gamers. Mechanics serve story, not vice versa.
  • Reader self-selection is stark: some readers only read "Crunchy Town-Builders" or "Progression Fantasy with light LitRPG elements."

VR vs. Real-World LitRPG

  • VR: Characters enter game worlds via headsets/pods. Clear separation between real and virtual.
  • Real-World/System Apocalypse: Game mechanics invade Earth. All survival has mechanical weight.

Solo vs. Guild vs. Town-Building

  • Solo: Single protagonist grinding and growing alone (e.g., Dungeon Crawler Carl).
  • Guild: Focus on party dynamics, team progression, faction politics.
  • Town-Building/Settlement: Base-building as primary mechanic. MC builds and manages structures, NPCs, economies.

Other Sub-Types

  • Crafting-Focused: Blacksmithing, alchemy, cooking, enchanting as primary class.
  • Deckbuilding: Characters collect and duel with card decks.
  • Harem: Romance subplot with multiple love interests (contentious subgenre; readers pre-select based on "harem/no-harem" tags).

System Design Fundamentals

Stat Architecture

  • Systems typically include core stats (Strength, Dexterity, Intelligence, Constitution, Wisdom, Charisma) or custom variations.
  • Derivative stats (Health Points, Mana, etc.) should depend on primary stats logically (e.g., HP = CON × Level).
  • Successful systems maintain numerical consistency across the entire narrative using spreadsheets or system documentation.

Skill Acquisition and Progression

  • Skills progress through tiers: Apprentice → Journeyman → Master, unlocking higher-tier abilities.
  • Experience requirements can follow exponential decay (like WoW) or linear progression with milestone spikes.
  • Successful stories: each skill unlock feels earned, tied to genuine risk/sacrifice/problem-solving, not free gifts.

Progression Curves The four main patterns observed in successful LitRPG:

  1. Linear Progression: Steady, slow growth. Feels grounded and realistic but can feel grindy (e.g., Dungeon Crawler Carl).
  2. Exponential Decay: Fast early levels, slowing dramatically. Matches MMO expectations.
  3. Milestone-Based: Clear stages (Beginner → Base Class → Advanced Class → Tiers). Each transition has power spike.
  4. Ranked Tiers: Discrete jumps between ranks (Iron → Bronze → Silver → Gold → Diamond) with exponential gains at each step (e.g., He Who Fights with Monsters).

Critical Progression Rule: Too-fast = boring. Too-slow = readers abandon. Test pacing by ensuring Book 3 MC decisively defeats Book 1 version but not so overwhelmingly that challenges feel trivial.

Presenting System UI in Prose

Blue Box Method (Most Common)

  • Use Royal Road's table formatting (blue boxes by default, can customize color).
  • Appears after action/revelation, not mid-scene.

  • Example:

    [Status: Level 12 acquired]
Strength: 14 → 15
Dexterity: 12 → 13

System Voice/Personality

  • Give the system character: formal, archaic, playful, or clinical tone.
  • Consistent phrasing and formatting becomes part of worldbuilding.
  • Example: System always says "Quest Accepted" vs. "Task Logged" signals flavor.

Narrative Integration

  • Describe stats in narration first (audiobook-friendly, immersive).
  • Include full stat sheet for readers who want details.
  • Avoid info-dumping during action scenes.

Key Principle: Stat blocks should interrupt narrative tension minimally. Use them to punctuate moments of achievement, not mid-combat confusion.

Common Mistake: "Blue Box Madness"—stats every chapter, stat dumps pages long. Readers resent this. Save reveals for meaningful moments.

Beloved Tropes

  • Underdog rises to power.
  • Unique class/skill only protagonist can access (subverted if the item/skill is obviously available to others).
  • Mentor relationship with skilled NPC.
  • Discovery of hidden skill/talent.
  • Breaking through level caps and power thresholds.
  • The "first level feels weak but rewarding" curve.

Tired Tropes to Avoid

  • Instant Mastery: Character acquires skill and immediately excels. Readers want struggle and failure first.
  • Secret Ancient Power: Protagonist finds item/skill lost to history that no one else has thought to use. Readers spot this immediately as contrived.
  • Overpowered Main Character: Starting too strong removes tension. The genre is about growth from humble beginnings.
  • Harems: If included without careful character work, feel tacked on and devalue romance subplots.
  • Chosen One Narrative: Especially when tied to destiny/prophecy rather than earned power.
  • System Message Overload: Too many stat dumps, too many notifications. Breaks immersion.
  • Poor Female Character Portrayal: Women as "perfect girlfriend" or "sickly daughter to protect." Female readers are significant LitRPG consumers and notice shallow characterization.

Pacing and Chapter Structure

Typical Royal Road Pacing

  • Chapter Length: 2.8k–3.5k words is the sweet spot (depends on stat density).
  • Release Schedule: 2–5 chapters/week (2k word chapters) or 1/week (4–8k chapters).
  • Chapter Structure:
    • Opening hook/recap
    • Action, exploration, or character moment
    • System interaction/stat gain
    • Cliffhanger or transition

Progression Pacing

  • Early chapters: frequent level-ups and stat increases (every 1–3 chapters).
  • Mid-story: level-ups every 5–10 chapters, harder to achieve.
  • Late story: tier/rank transitions spaced further apart, each representing massive growth.

Common Mistakes That Tank LitRPG Stories

  1. Author Doesn't Know the System: Making up mechanics as you go. Readers will spot inconsistencies instantly.
  2. Info-Dump Syndrome: Explaining system rules at length instead of revealing them organically.
  3. Stats ≠ Character Development: Numbers going up on a spreadsheet is satisfying but hollow without emotional/narrative weight.
  4. Poor Editing: Grammar and typo errors "absolutely KILLING this genre" per reader surveys. Professionalism matters.
  5. Uninteresting MC vs. Detailed World: Elaborate system but bland protagonist. Readers' comment: "Everyone BUT the MC keeps me reading."
  6. Lack of Stakes: Progression without risk/difficulty. Wins feel unearned.
  7. Unexplained Power Scaling: Character gets stronger but readers can't track why or how much.
  8. Boring Skill Descriptions: Abilities need flavor, not just mechanical output. "Slash does 30% more damage" vs. "Rending Slash tears through material, leaving jagged wounds that bleed profusely."

Examples of Excellent System Design

Dungeon Crawler Carl (Matt Dinniman)

  • Linear progression with slow, grounded growth.
  • Stats matter tangibly to survival. Player must understand system to survive traps and enemies.
  • Stat blocks are sparse, purposeful, and tied to dramatic moments.
  • Acquired 280,000+ ratings on Royal Road; published by Ace Books in 2024; reached #2 on NYT Audio Fiction list in 2025.

He Who Fights with Monsters (Shirtaloon/Travis Deverell)

  • Ranked tier system (Iron → Bronze → Silver → Gold → Diamond) with exponential power jumps.
  • Unique hybrid cultivation/LitRPG mechanics that surprise genre-savvy readers.
  • Strong character voice and cultural clash (laid-back Australian in serious magical world) makes MC memorable despite divisive personality.
  • Books published by major houses; strong reader retention.

Awaken Online (Travis Bagwell)

  • VR LitRPG with villain-protagonist (Jason raises undead armies, becomes antagonist).
  • System allows player freedom and moral ambiguity.
  • Nearly 1 million copies sold; invested heavily in professional audio production, which drove mainstream success.

The Wandering Inn (pirateaba)

  • Portal fantasy/isekai LitRPG.
  • System focuses on Classes, Skills, Levels in service of human/character storytelling.
  • System messages highlight emotional beats, not just mechanical ones.
  • 16+ million words, twice-weekly updates, comic adaptation in development.

Primal Hunter (Zogarth)

  • System Apocalypse subgenre.
  • MC is an archer/hunter with specific identity (not generic "guy with powers").
  • Clear differentiation and character specificity helped reader retention (11,000+ monthly patrons).

2. PROGRESSION FANTASY

Core Definition

A fantasy subgenre centered on the protagonist's intentional and quantifiable increase in power, skill, or magical ability. The journey of growth is the primary narrative driver, not a subplot. Unlike LitRPG, explicit game mechanics (stats, levels) are optional; the focus is on structured, visible advancement.

Key Distinction from LitRPG

  • Progression Fantasy: No game UI required. Power growth happens through mystical training, cultivation, martial arts advancement, or internal magical cultivation. System may use words like "Rank," "Stage," "Cultivation Level" rather than "Level."
  • LitRPG: Game mechanics and notifications are essential parts of the reading experience.
  • Overlap: All LitRPG is technically progression fantasy, but not all progression fantasy is LitRPG.

Reader Contract

"Show me a protagonist learning, training, struggling to grow stronger. I want clear milestones, earned power gains, and visible transformation. The protagonist should feel fundamentally different between Act 1 and Act 3."

Hard Rules

  1. Progress Must Be Quantifiable: Readers need measurable advancement, even without explicit numbers. "Stage 3 cultivator" or "Master swordsman" markers work.
  2. No Power Loss (Critical): Progress loss scares off more readers than virtually anything else. A character losing abilities mid-series creates abandonment.
  3. Clear Power Tiers: Readers use these to understand world power levels. Once established, tier progression must follow logic.
  4. Earned Growth: Power gains must connect to effort, sacrifice, or problem-solving. Free power is unsatisfying.
  5. Book-to-Book Comparison: A useful test: Book 3 protagonist should decisively defeat Book 1 version. If not, progression feels stalled.

Three Major Styles

Eastern-Style (Xianxia/Wuxia Foundation)

  • Cultivation through meditation, qi manipulation, internal energy.
  • Heavy emphasis on philosophy, enlightenment, Buddhist/Taoist concepts.
  • Often includes immortality seeking, heavenly tribulations.
  • Examples: Cradle (western interpretation of eastern concepts).

Western-Style Progression Fantasy

  • Borrows cultivation mechanics but strips traditional Chinese cultural trappings.
  • Magic systems with Western naming conventions (Copper → Iron → Jade → Gold instead of Qi Condensation → Core Formation).
  • Academy settings, mentorship, adventuring parties.
  • Examples: Cradle (hybrid), Warformed: Stormweaver.

LitRPG-Adjacent

  • Uses explicit game mechanics but emphasizes growth journey over system mechanics.
  • Blurs the line between progression fantasy and LitRPG.

Power System Design Principles

Tier/Rank Systems Common patterns:

  • Color Tiers: White (beginner) → Yellow → Orange → Red → Gold (master).
  • Metal Tiers: Copper → Iron → Bronze → Silver → Gold.
  • Cultivation Stages: Foundation → Golden Core → Immortal Ascension.
  • Letter Ranks: F (weakest) → E → D → C → B → A → S → SS.

Each tier should represent meaningful power difference. Characters at different tiers shouldn't be able to compete directly. Physical transformations signal mental ones: eye color changes, hair color changes, wings, horns manifest at specific tiers.

Quantifiable Advancement Methods without explicit numbers:

  • Technique mastery (bronze-level sword strikes vs. silver-level).
  • Capacity increase (can hold more mana, sustain spells longer).
  • Spiritual attribute development (sensitivity to magic, intuition).
  • Combat capability (can fight and win against tier X enemies).

Training Arcs vs. Individual Breakthroughs

  • Montage Risk: Training montages are tempting but can feel rushed. Readers want some individual training scenes showing struggle, failure, epiphanies.
  • Breakthrough Scenes: When protagonist achieves tier advancement, this deserves a scene showing struggle, breakthrough, and transformation.
  • Best Practice: Mix montages (covering weeks of training) with 1–2 detailed breakthrough scenes per advancement tier.

Maintaining Tension as MC Gets Stronger

Problem Scaling

  • As protagonist grows, introduce enemies/challenges that scale faster or introduce different threat types.
  • Strongest threat need not be physical: political, magical, spiritual, temporal.
  • Example: Cradle - as Lindon grows, new factions and cultivation sects present equal or greater challenge despite personal power gain.

Internal Struggle Escalation

  • Power doesn't solve everything. New power unlocks new problems (pride, responsibility, temptation, enemies attracted by strength).
  • Emotional stakes must rise with power stakes.

Shifting Power Hierarchies

  • Early story: MC is underdog among peers.
  • Mid-story: MC becomes formidable but others advance too.
  • Late story: MC among strongest but faces tier-transcending threats.

Beloved Tropes

  • Underdog from weak background.
  • Mentor relationship and eventual transcendence of mentor.
  • Breakthrough moments with dramatic transformation.
  • Accumulation of techniques and power combinations.
  • Rivalry with peer who also progresses.
  • Discovery of unique cultivation path/technique.
  • Facing the impossible and barely succeeding through growth.

Tired Tropes to Avoid

  • Instant Power-Up: Finding an item that grants instant power.
  • Bloodline Awakening Without Buildup: Protagonist suddenly has latent power that explains past weakness. Feels unearned without foreshadowing.
  • Training Montage Only: Readers want at least some detailed training scenes.
  • Arbitrary Advancement Blocks: "You can't progress past this tier until..." rules that feel like artificial gates.
  • Power That Doesn't Solve Problems: Protagonist gains power but narrative problems remain unchanged. Progression should open new story paths.

Pacing Expectations

  • Tier Advancement: Every 2–4 chapters early (rapid growth, high-stakes breakthroughs).
  • Mid-Story: Every 8–15 chapters (growth slowing, advancement harder).
  • Late-Story: Every 20+ chapters (major tier jumps, rare and climactic).

Chapter Structure

Similar to LitRPG but with less mechanics:

  • Training/learning moment
  • Application/combat testing
  • Breakthrough trigger
  • Advancement scene or cliffhanger

Examples Defining the Genre

Cradle (Will Wight)

  • Western cultivation fantasy with clear tier system: Copper → Iron → Jade → Gold → Underlord → Overlord → Archlord.
  • Lindon starts as "runt of the litter," cast out by his clan for weakness.
  • System gives "enough information to imagine solutions but not so much a min-maxer could determine perfect strategy mathematically."
  • Inspired by xianxia/wuxia but fully Western in approach; New York Times bestseller; massive indie success.

Defiance of the Fall (TheFirstDefier)

  • System Apocalypse progression fantasy with xianxia elements.
  • MC starts alone in wilderness after system integration.
  • 20+ million views on Royal Road; books published on Amazon/KU/Audible.

He Who Fights with Monsters (Shirtaloon)

  • Hybrid cultivation/LitRPG progression system.
  • Ranked advancement with ranked tier jumps creating exponential power gains.
  • Character-driven progression with strong voice.

3. SYSTEM APOCALYPSE (LitRPG APOCALYPSE)

Core Definition

A game-like system appears in the world during an apocalyptic event, forcing characters to adapt to new reality where magic, levels, quests, and game mechanics are real. Combines LitRPG mechanics with survival fiction.

Reader Contract

"The world has changed fundamentally. I want to see how people adapt to supernatural/magical reality, balance survival with power fantasy, and build new society from collapse."

Hard Rules

  1. Day Zero Must Matter: The inciting incident (system arrival) should change everything permanently. No reverting to old world.
  2. Survival Pressure Early: Early chapters must establish genuine danger. Readers want to feel stakes, not power fantasy without context.
  3. System Integration Logical: System arrival should have in-world explanation (however vague). "It just happened" is acceptable but feels thin.
  4. Real-World Consistency: If system arrives on Earth, maintain real geography, real consequences. Readers will notice if you ignore physics.

The "Day Zero" Opening and Conventions

Common Patterns

  1. Sudden Integration: System appears with notification. Protagonist suddenly sees HUD, stats, quests. World immediately transforms.
  2. Tutorial Phase: First days/weeks are "tutorial," gentler challenges, gradual escalation.
  3. Societal Collapse: Governments fall, infrastructure breaks, civilization shatters. Survivors must organize.
  4. Factions Form: Within hours/days, groups form: government remnants, criminal networks, cults worshiping the system, military consolidation.

Critical Moment: First 1–3 chapters establish:

  • How normal person reacts to system appearance.
  • First death or near-death (establishes real stakes).
  • Understanding that old rules are gone.

Balancing Survival with Power Fantasy

Early Story (Chapters 1–30)

  • Focus: Survival, resource gathering, learning system mechanics.
  • Power fantasy is muted; MC is still weak, struggles with level 1–5 monsters.
  • Readers want desperation, not dominance.

Mid-Story (Chapters 30–100+)

  • Focus: Growing stronger, claiming territory, power politics.
  • MC becomes formidable but faces tier-scaled challenges.
  • Power fantasy increases; survival becomes strategic rather than desperate.

Late-Story

  • Focus: Societal rebuilding, faction wars, world-scale threats.
  • MC is powerful but not unstoppable; challenges are existential/political.

Key Balance Technique: Introduce new threat types as MC grows. Example: MC defeats zombies/low-tier monsters but discovers intelligent predators, rival factions, interdimensional invasions.

Societal Collapse Portrayal

Essential Elements

  1. Infrastructure Failure: Food, water, electricity, medicine stop.
  2. Government Vacuum: Official structures collapse or fracture. Martial law or warlordism emerges.
  3. Human Behavior Spectrum: Some help, some exploit, some break. Avoid binary good/evil; people are survival-driven.
  4. Resource Scarcity: Water, ammunition, medical supplies, safe shelter drive conflict.

Tropes

  • The Safe House: Temporary refuge offering physical safety and mental reprieve. Often marks turning points in narrative.
  • The Journey: Group traveling through devastated landscape toward goal. Allows full-range encounters with post-collapse society.
  • Survivor Guilt/Hope Tension: Characters wrestle between despair and reason to rebuild.

Faction Building and Politics

Faction Types

  • Military/Government Remnants: Organized, disciplined, might be authoritarian.
  • Criminal Networks: Exploit chaos, control black markets, prey on weak.
  • Cults: Worship the system, may sacrifice followers to it.
  • Survival Communities: Towns banding together, often democratic.
  • Warlords/Strongmen: Charismatic leaders claiming territory.
  • Isolationists: Avoid society, set up hidden communities.

Political Complexity

  • Factions should have competing interests, not all evil/good.
  • MC becomes political player: making alliances, enemies, navigating complex webs.
  • Readers enjoy intrigue and political depth.

Integration of Real-World and Fantasy Elements

Grounding Techniques

  • Name real locations (if MC is in USA, mention states, cities).
  • Acknowledge real infrastructure (highways, power lines, hospitals are now dangerous/ruined).
  • Use real weapons/survival skills: firearms, first aid, agriculture, carpentry matter.
  • Maintain daylight cycles, weather, seasons.

Tech Integration

  • Survivors try to use old-world tech: vehicles (fuel issues), weapons (ammo), medicine.
  • Show why tech fails in magical world: magic interferes with electronics, or doesn't; internal consistency matters.
  • Hybrids interesting: magic-powered vehicles, guns enhanced with spells, etc.

Examples

  • Defiance of the Fall (TheFirstDefier): System apocalypse with cultivation elements. MC alone in wilderness. Survival, power-up, faction discovery arc.
  • The Primal Hunter (Zogarth): Office worker thrust into system apocalypse tutorial and thrives. Minimal base-building, focus on character development and progression.

Pacing and Chapter Structure

  • Early (Chapters 1–15): Integration, confusion, first dangers. Shorter chapters (2–3k).
  • Mid (Chapters 15–50+): Learning system, power-up, establishing base. Varied length.
  • Late: Expansion, war, existential threats. Can sustain longer chapters.

4. DUNGEON CORE

Core Definition

Protagonist is a dungeon, dungeon core, or magical construct bound to a location. Cannot leave but can reshape surroundings, create minions, set traps, grow stronger. Often pseudo-LitRPG with base-building management gameplay.

Reader Contract

"I want to experience strategic base-building and optimization. I accept non-human POV and limited mobility in exchange for interesting economic systems, trap design, and creature management. The dungeon itself is the protagonist."

Hard Rules

  1. Immobility is Feature, Not Bug: Dungeon can't go on adventures. Tension comes from what threatens the core, not what MC chases.
  2. Consequence for Strategic Failure: If dungeon designs trap poorly or creates weak minions, adventurers will punish it. Dungeon must learn from failure.
  3. Core is Vulnerable: The core itself (dungeon's heart/mind) must be protected. This is central tension.
  4. POV Clarity: Reader must understand dungeon's sensory/cognitive limitations and how it perceives the world.

Non-Human POV Challenges

Sensory Limitations

  • Dungeon can't leave. Limited direct sensory input.
  • Often "feels" through mana flows, monster senses, vibrations in dungeon structure.
  • Dungeon learns about outside world through adventurers, scouts, or other means.

Solution: Split POV or relay POV. Example:

  • Primary POV: Dungeon core (strategic, omniscient within dungeon).
  • Secondary POV: Adventurer, NPC, or dungeon minion exploring dungeon (reader's ground-level perspective).

This 50/50 split helps readers stay grounded in familiar human experience while experiencing dungeon's alien perspective.

Cognitive Differences

  • Dungeon thinks slower (no human-speed consciousness).
  • Dungeon might experience time differently (seasons pass in what feels like days).
  • Dungeon has no human emotions (or slowly develops them through story).

Base-Building Narrative Mechanics

Resource Management in Prose Instead of showing spreadsheets:

  • Describe dungeon's mana reserves and regen rate.
  • Show cost/benefit of spawning creatures or enchanting rooms.
  • Create scarcity: dungeon must choose between defense, expansion, or treasure hoarding.

Example Progression

  • Early: Simple dungeon, 3–4 rooms, basic traps, weak monsters. Dungeon learns system.
  • Mid: Expanding territory, specialized rooms (library, forge, breeding chambers), sophisticated trap combinations.
  • Late: Sprawling complex, hundreds of minions, political relationships with other dungeons/factions, economic impact on region.

Trap and Creature Design

  • Readers enjoy reading about creative dungeon design.
  • Each room/trap/creature should feel purposeful, not random.
  • Show dungeon learning: "Adventurers bypassed the arrow trap by..." → "Next dungeon iteration adds reinforced walls."

Creating Tension When MC is a Building

External Threat

  • Adventurer parties seeking treasure or to kill dungeon.
  • Rival dungeons competing for territory/resources.
  • Natural disasters threatening dungeon stability.
  • Government/military wanting to control dungeon.

Internal Tension

  • Resource scarcity: not enough mana to do everything.
  • Minion rebellions or dissatisfaction.
  • Dungeon's own curiosity/ambition creating danger.
  • Moral conflicts (dungeon kills adventurers; is dungeon evil?).

Progression Tension

  • Dungeon can grow stronger, but with vulnerability windows.
  • Dungeon evolution/tier advancement creates periods of weakness.
  • New abilities come with new risks.

POV Management Best Practices

Single Dungeon POV (Harder)

  • Keep readers inside dungeon's perspective only.
  • Show external events through dungeon's limitations (hearing screams, sensing mana disturbances).
  • Risk: readers feel trapped/limited.
  • Successful example: internal monologue and dungeon learning from observer NPCs.

Split POV (Easier for Beginners)

  • Alternate: Dungeon core chapters → Adventurer/NPC exploration chapters.
  • 50/50 split works well.
  • Adventurer chapters ground reader in familiar human perspective and build suspense (readers know dungeon's plan; adventurers don't).

Relay POV

  • Dungeon learns through minions' senses/reports.
  • Requires clear communication/understanding mechanism between dungeon and creatures.
  • Creates filter between dungeon and reader: sometimes dungeon is uncertain what minions experienced.

Avoiding Common Pitfalls

  1. Lone-Wolf Dungeon: Dungeon interacts only with adventurers and doesn't form relationships with NPCs. Add interaction and dialogue.
  2. Overemphasis on Adventurer POV: If 70%+ is adventurers exploring, it's not really dungeon core; it's fantasy with dungeon setting.
  3. No Consequence for Design Failures: Every trap should be disarmable; every creature should be defeatable. Make dungeon learn and adapt.
  4. Reader Annoyance with Inability: Some readers resent dungeon's immobility. Address this by making dungeon's strategic position interesting, not frustrating.

Examples

Dungeon Born (Dakota Krout, 2016)

  • First in Divine Dungeon series, extremely popular.
  • Dungeon learns and grows, creating increasingly sophisticated challenges.

Rise of a Rogue Dungeon (Royal Road)

  • Dungeon in fantasy world with dragons, titans, various races.
  • Focuses on dungeon's relationships with creatures and region.

A Dungeon Core (Royal Road)

  • Core-focused dungeon narrative.
  • Explores dungeon's perspective and growth.

Another Dungeon Core (Royal Road)

  • Variations on core mechanics and POV structure.

Chapter Structure

  • Dungeon POV Chapters: 2–3k words. Internal monologue, planning, resource management, strategy.
  • Adventurer POV Chapters: 2–3k words. Exploration, discovery, combat, adaptation.
  • Alternating Pattern: Works well. Ends dungeon chapter on suspense (adventurers approaching); ends adventurer chapter revealing dungeon's plan.

5. COZY FANTASY / SLICE-OF-LIFE

Core Definition

Fantasy fiction emphasizing hope, kindness, empathy, and community. Features characters in everyday magical routines, slice-of-life elements, and low-stakes conflict. Often single-location settings (small town, inn, shop). Focus on relationships: family, found family, friendship.

Reader Contract

"I want comfort, warmth, and emotional connection. I'm not seeking danger or high stakes. Show me characters helping each other, building community, experiencing wonder in small magical moments. This is a refuge, not a battlefield."

Hard Rules

  1. No Genre Bait-and-Switch: If you promise cozy, don't introduce world-ending threat or graphic violence in chapter 20. Readers come for comfort; betraying that feels violating.
  2. Low Stakes Can Still Engage: Conflict can exist (personal growth, community problems, small dangers) but avoid existential threats.
  3. Emotional Arcs Over Action Arcs: Character development happens through emotional breakthroughs, not combat victories.
  4. Community as Character: The setting and community are as important as individual protagonist.
  5. Hope Must Be Present: Even sad moments don't end in despair. There's always path forward.

What Makes Cozy Fiction Work

Essential Elements

  1. Comforting Details: Food (tea, baked goods), comfortable spaces, sensory warmth.
  2. Character Kindness: Characters help without extensive cost/trauma. Goodness is rewarded or at least acknowledged.
  3. Found Family: Whether biological or community, strong relationship bonds.
  4. Slow Pacing: Space for character moments, reflection, small conversations.
  5. Wonder Without Danger: Magic exists and is beautiful but not inherently threatening.

Tone

  • Conversational, intimate.
  • Humor is gentle, not cruel.
  • Authorial voice is warm, even when describing conflict.

Low-Stakes Conflict That Still Engages

Types of Conflict

  • Personal Growth: Character struggling with self-doubt, past trauma, learning to trust.
  • Community Problem: Town needs harvest before winter, shop is struggling, neighborhood conflict.
  • Relationship Tension: Misunderstanding between friends, unresolved feelings, communication breakdown.
  • Small Danger: Monster in the woods (not extinction-level threat), wild magic accident (not apocalypse).
  • Moral Dilemma: Choosing between loyalties, ethical quandary with no perfect answer.

Key Principle: Stakes are high emotionally but not existentially. Character failing matters because they care about outcome, not because world ends.

Slice-of-Life vs. Cozy Fantasy Spectrum

Slice-of-Life Heavy

  • Minimal plot. Emphasis on daily routines, small discoveries, character observation.
  • Some readers want no conflict at all (iyashikei/healing anime influence).
  • Risk: feels static or dull if no arc exists.

Cozy Fantasy with Plot

  • Clear character/community arc, gentle resolution.
  • Small conflicts woven through.
  • Most successful cozy fantasies blend both: slice-of-life texture with emotional throughline.

No-Conflict Rule Debate

Reader Divide

  • Some want pure slice-of-life with no antagonist.
  • Others want small conflict for narrative tension.
  • Spectrum matters: cozy fantasy can have conflict, just not violence/trauma/doom.

Best Practice: Define upfront what "cozy" means for your story. Advertise accurately to manage reader expectations.

Emotional Arcs in Cozy Fantasy

Character Arc Example

  • Start: Character isolated, grieving, or self-doubting.
  • Journey: Small community interactions, gradual opening to hope.
  • Climax: Emotional breakthrough (not battle).
  • Resolution: Character healed/transformed, integrated into community, found belonging.

Community Arc Example

  • Start: Community divided, struggling, or disconnected.
  • Journey: Characters working together on small problem.
  • Climax: Community rallies, realizes strengths in unity.
  • Resolution: Stronger bonds, shared purpose, renewed hope.

Beloved Tropes

  • Found family.
  • Small-town charm and quirky characters.
  • Magical apprenticeship/learning craft.
  • Healing through relationships and community.
  • Discovering hidden talents/purpose.
  • Cozy mystery elements (gentle puzzle-solving).
  • Holiday/seasonal celebrations bringing community together.

Tired Tropes to Avoid

  • Manic Pixie Dream Character: Quirky character exists only to change protagonist. Give characters depth.
  • Nostalgic Falseness: "Simpler time" romanticization that ignores real historical problems.
  • Conflict Resolution Without Work: Problems solve themselves. Readers want to see characters communicate and grow.
  • Shallow Diversity: Token diverse character with no depth.

Pacing Expectations

  • Slow, Meditative Pacing: 2–3k chapters, weekly updates.
  • Space for Reflection: Character has time to think, feel, process.
  • Seasonal/Cyclical Structure: Calendar-based (winter chapter, spring chapter) works well.

Chapter Structure

  • Quiet opening (character in routine or reflection).
  • Small event or interaction.
  • Character's internal response/growth moment.
  • Gentle transition to next scene.
  • Soft ending (not cliffhanger; sense of peace or hope).

Examples

  • The City We Became (N.K. Jemisin) - Urban fantasy with love and community at heart.
  • Indie cozy fantasy web serials on Royal Road emphasizing tea shops, bakeries, magical crafts.

6. ROMANTASY / ROMANCE

Core Definition

Fantasy fiction where romance is a significant/primary plot driver. Reader expectations depend on which of two types:

Fantasy Romance: Romance is the focus; HEA/HFN ending mandatory. Romantic Fantasy: Fantasy plot is primary; romance is significant subplot; HEA/HFN not guaranteed.

Reader Contract (Depends on Type)

Fantasy Romance: "The romance is the story. I want to see two characters fall in love against obstacles, with emotional depth and sexual/romantic tension. I expect a satisfying ending where they end up together."

Romantic Fantasy: "The story has a significant love arc, but the external plot is primary. I expect beautiful romantic moments and character chemistry, but the ending is determined by story logic, not romance requirements."

Hard Rules

Universal to Both

  1. Chemistry Must Be Earned: Readers need to understand why characters care for each other. Attraction must feel real, not convenient.
  2. Love Interest Must Drive Transformation: The love interest significantly causes/contributes to protagonist's growth.
  3. Emotional Honesty: Inner feelings must be shown, not told. "I love you" means nothing without demonstrated vulnerability.
  4. Conflict Must Be Real: Easy romance (no obstacles) is boring. Genuine reasons for relationship difficulty.

Fantasy Romance-Specific

  • HEA/HFN is required. Readers feel betrayed if romance ends ambiguously or tragically.
  • Romance scenes take significant page time (not just epilogue).
  • Internal conflict (emotional journey) is as important as external conflict.

Romantic Fantasy-Specific

  • HEA/HFN is not required. Story logic determines ending.
  • Romance thread is woven through but secondary to plot.
  • Reader cares about both relationship and external stakes equally.

Expected Tropes (Beloved)

Enemies to Lovers

  • Two characters start at odds: opposition, misunderstanding, or genuine enmity.
  • Forced proximity (war, quest, captivity) requires interaction.
  • Gradual understanding and attraction as they see past first impressions.
  • Slow-burn chemistry with banter and tension.
  • Works exceptionally well in fantasy: nations at war, spy dynamics, magical opposition.

Fated Mates/Chosen One

  • Characters magically bonded or destined for each other.
  • Internal recognition of connection.
  • Both resist, then accept fate.
  • Can feel contrived if not grounded in character choice and emotional growth.

Forbidden Love

  • Social/magical barrier preventing relationship: class difference, species difference, magic/no-magic, enemy factions.
  • Conflict comes from external pressure, not character incompatibility.
  • Relationship must prove worth the cost.

Second Chance/Forced Proximity

  • Characters separated or estranged, forced to reconcile through circumstance.
  • History adds depth and pain to reconciliation.
  • Excellent for character depth (readers see how much they've changed).

Love Triangle

  • Two love interests, protagonist must choose.
  • Risky: readers often resent love triangles; only works if both love interests are genuinely compelling and each relationship feels different.
  • Must be resolved decisively, not dragged out.

Character Chemistry Techniques

Show Attraction Subtly

  • Physical description notices: dimples, the way someone laughs, how they move.
  • Small touches that linger slightly longer.
  • Involuntary reactions: heartbeat increase, breath catching, blushing.

Banter and Wit

  • Clever dialogue showing mutual understanding.
  • Characters who make each other laugh or challenge each other intellectually.
  • Verbal sparring that masks attraction (enemies-to-lovers especially).

Vulnerability Moments

  • Characters showing weakness or fear to each other.
  • Sharing secrets or past trauma.
  • Comforting each other (non-romantic, then gradually romantic).

Shared Goals/Values

  • Characters discover common purpose.
  • Working together toward goal reveals compatibility.
  • Seeing how partner handles conflict/makes decisions.

Heat Levels and Reader Expectations

Heat Level Spectrum

  1. Sweet (Fade-to-Black)

    • Kissing, maybe embracing.
    • Sex happens off-page ("They spent the night together...").
    • Suitable for YA, general audiences, romance readers who prefer subtle.

  2. Warm (Mild Sensual)

    • On-page kissing with description.
    • Beginning of sexual activity described (clothing removal, touching).
    • Fades to black before or during explicit sexual content.

  3. Sensual (Moderate Heat)

    • Full sexual scenes on-page.
    • Language is flowery/poetic, not crude.
    • Euphemisms and indirect language ("their bodies joined").
    • 1–2 sex scenes, focus on emotion over mechanics.

  4. Spicy (Explicit)

    • Multiple explicit sex scenes.
    • Coarse language acceptable.
    • Clear anatomical descriptions.
    • Sexual tension and lust drive some scenes.
    • 2–4+ sex scenes per book.

  5. Erotic (Very Explicit)

    • Sex scenes frequent and detailed.
    • BDSM, kink, non-standard sexual activities.
    • Sexual content is primary plot driver alongside romance.
    • Readers specifically seeking high sexual content.

Critical Rule: Communicate heat level clearly in blurb/cover. Readers self-select based on expectations. Mislabeling causes reviews from disgruntled readers.

Romance Integration with Fantasy Elements

World-Building Strategy

  • Use fantasy setting to complicate romance (species difference adds real tension).
  • Or use setting to create opportunities for romance (war forces proximity, magic enables bonding, politics separates lovers).
  • World should not feel like afterthought to romance.

Magic and Romance Intersection

  • Magic systems can enable intimacy (magic bonds, soul connections, sensing mana intertwining).
  • Or prevent it (magic and romance are separate, magic warns of danger).
  • Cultural magic can influence relationship: some cultures encourage arranged bonds, others forbid cross-species love, etc.

Action Sequences and Romance

  • Action scenes should show relationship dynamics, not pause romance.
  • Fighting together reveals trust, compatibility, how partners support each other.
  • Sexual tension can heighten during/after action (adrenaline, relief at survival, protective instincts).

Examples

  • Swordheart (Elizabeth Bear) - Romantic fantasy with complex antagonists and emotional depth.
  • Indie romantasy web serials on Royal Road emphasizing enemies-to-lovers and character chemistry.

Pacing

  • Fantasy Romance: Heavy romance focus early, building to consummation/climax around 60–75% mark. Resolution after romance is established.
  • Romantic Fantasy: Romance subplot woven through action plot. Key romantic moments at act breaks. Romance resolution aligned with plot resolution.

7. SCI-FI / SPACE OPERA

Core Definition

Space-based or futuristic fiction with science-based worldbuilding. Hard sci-fi emphasizes scientific accuracy and explanation of mechanics. Space opera prioritizes epic scale and human drama over scientific accuracy.

Reader Contract

Hard Sci-Fi: "Explain the science. I want plausible physics, technology consistency, and logical consequences of scientific principles. Handwave nothing; build the world on real science (or clear extensions of it)."

Space Opera: "Give me epic scale, grand conflicts, and compelling characters. Science is backdrop; human drama is foreground. Don't worry about whether FTL is physically possible; focus on the story."

Hard Rules

Hard Sci-Fi

  1. Scientific Consistency: Physics and tech must follow established rules. No magic wand fixes.
  2. Logical Consequences: Technology has realistic limitations and side effects.
  3. Explanation Expected: Readers want to understand how things work, not just that they do.
  4. Accuracy Matters: Get the science right or handwave it clearly.

Space Opera

  1. Epic Scale: Settings spanning planets/systems/galaxies. Civilizations and empires clash.
  2. Human Drama: Personal stories matter; political intrigue, relationships, character arcs drive story.
  3. Science Can Be Soft: Faster-than-light travel, hyperdrives, teleports are "good enough" without explanation.
  4. Action and Grandeur: Epic space battles, first contact, exploration.

Tech Consistency Rules

Soft Sci-Fi Worldbuilding

  • Create internally consistent universe with its own laws of physics.
  • Allow divergences from reality (time travel, FTL) but rules must be consistent.
  • Focus on human experience of living with technology.

Example: If robots can't feel emotion, they don't aid protagonist out of principle. If AI can be enslaved, show the moral implications. Rules matter.

Tech as Extension of Rules

  • Every technology should have limitations.
  • Introduce problems that technology can't solve (corruption, emotion, nature, human greed).
  • Technology solves old problems; new technologies create new ones.

Space Opera Conventions

Epic Scale

  • Settings span star systems to galaxies.
  • Civilizations and empires with histories and politics.
  • Grand conflicts: nations at war, first contact, existential threats.

Political Complexity

  • Factions with competing interests.
  • Diplomacy as important as combat.
  • Intrigue and betrayal common.

Exploration and Discovery

  • Unknown worlds, alien species, new phenomena.
  • Sense of wonder and vastness.

Military/Adventure Focus

  • Space battles, starship crews, adventuring parties.
  • Character-driven action.

Examples

  • Of Blood and Stardust (Royal Road) - Military hard sci-fi space opera.
  • Final War: Hetairoi (Royal Road) - Progression + hard sci-fi + mecha space opera.

Reader Expectations

Hard Sci-Fi Readers Want:

  • Believable worldbuilding.
  • Accurate technology/physics explanations.
  • Logical problem-solving.
  • Science as character (challenges drive plot).

Space Opera Readers Want:

  • Epic scope and grand conflicts.
  • Memorable characters and relationships.
  • Sense of wonder.
  • Action and adventure.
  • Politics and intrigue.

CROSS-CUTTING INSIGHTS & PATTERNS

On System Design Generally

Readers' Test for Good System Design:

  1. Can I understand the system from reading naturally?
  2. Does the system have internal logic/consistency?
  3. Do the rules explain character capabilities and limitations?
  4. Do stat increases/power-ups feel earned through struggle?
  5. Can I predict how the system works without author explanation?

Reader Self-Selection

Readers actively select based on:

  • Crunch Level: Crunchy vs. lite preferences are stark (some readers only read one).
  • Harem/No-Harem: Significant portion of readers filter explicitly on this.
  • Dark/Light Tone: Dark themes with violence vs. lighter adventure.
  • Heat Level: In romance, clearly labeled.
  • Pacing: Fast/multiple releases vs. fewer, longer chapters.

Universal Hard Rules Across Genres

  1. Internal Consistency: Once rules are set, follow them. Readers will catch violations.
  2. Earned Growth/Change: Character power/status/relationships should feel earned, not gifted.
  3. Meaningful Stakes: Even low-stakes stories need consequences for failure (emotional, relational, or strategic).
  4. Character Over Mechanics: Readers care about people more than systems, even in system-heavy genres.
  5. Clear Genre Labeling: Advertise genre accurately. Bait-and-switch betrays reader trust.

On Editing and Professionalism

Critical Finding: Grammar, spelling, and editing quality are "absolutely KILLING this genre." Readers notice and leave for poor presentation, even if story is solid.

Professional editing is essential for success, especially in self-publishing.

Monetization and Format Trends (2024-2025)

  • Audio Success: Major success stories invested heavily in professional audiobooks (Dungeon Crawler Carl, Awaken Online).
  • Patreon Model: Web serial authors often monetize through Patreon (early access, bonus chapters).
  • KU/Amazon Publishing: Successful Royal Road stories often move to Amazon KU for revenue and wider reach.
  • Transmedia: Successful stories expand to comics, audio, merchandise.

BIBLIOGRAPHY & SOURCES

LitRPG & System Design

Progression Fantasy

Cozy Fantasy

Romantasy / Romance

Dungeon Core

System Apocalypse

Space Opera & Hard Sci-Fi

Royal Road & Community Insights

Popular Stories Cited

FINAL NOTES FOR PROMPT DESIGNERS

Critical Takeaways

  1. Genre is a Contract: Readers come with specific expectations. Violating them (genre bait-and-switch, unexplained rule changes, power loss) causes abandonment.

  2. System Matters, But Character Matters More: Complex magic systems are appealing, but bland protagonists kill engagement. Invest equally in character development.

  3. Consistency = Credibility: Readers will track system rules more carefully than authors. Internal consistency (even in soft magic systems) is paramount.

  4. Pacing and Structure Align with Genre:

    • LitRPG: Frequent power-ups, regular stat progression, blue-box stat reveals.
    • Progression Fantasy: Milestone breakthroughs, earned advancement, less mechanical presentation.
    • System Apocalypse: Survival urgency early, faction politics mid-story, existential stakes late.
    • Cozy Fantasy: Slow, meditative, emphasis on emotional beats over action.
    • Dungeon Core: Strategic resource management, split POV, learning through failure.
    • Romantasy: Chemistry building, relationship obstacles, HEA/HFN expectations depend on subgenre.
    • Space Opera: Epic scope, political intrigue, character relationships in grand setting.

  5. Reader Self-Selection is Real: Readers filter heavily on crunch level, harem/no-harem, heat level, darkness. Accurate labeling is essential.

  6. Editing is Non-Negotiable: Grammar and professional presentation directly impact reader retention in web fiction.

Research Completed: This report synthesizes data from Royal Road communities, author blogs, published research, Goodreads reader discussions, Patreon trends, and bestseller analyses to provide comprehensive genre profiles for automated novel-writing system development.