Start Writing

    How do you write a dungeon core story?

    Updated · By the PlotWrite team · 60-second read

    To write a dungeon core story, make a sentient dungeon your point-of-view character, give it a hard resource budget, and let its growth depend on the adventurers it also has to survive. The reader's pleasure is in design choices: floors, traps and monsters that each cost something. Keep a ledger of what the dungeon has built, because readers will check it.

    Start 7-Day Free Trial — No Card

    Key takeaways

    • Dungeon core is a LitRPG subgenre where the protagonist is the dungeon itself.
    • Decide what your dungeon is.
    • Give it one resource and make it scarce.

    Dungeon core is a LitRPG subgenre where the protagonist is the dungeon itself. LitRPG Critic describes the lead as "a sentient magical entity that designs rooms, spawns monsters, sets traps, and manages resources" (What is Dungeon Core?, read November 17, 2026). Dakota Krout defines it as novels where at least one main character is a sentient dungeon, as quoted by author Woah77 (Dungeon Core, November 10, 2021). The genre has no formal rulebook, so treat these as working definitions.

    Decide what your dungeon is. Most cores in the guides I read are minds bound to a crystal, though some get an avatar or a golem body. Pick one early. A mind with no body can only act through what it builds, which keeps every scene about design.

    Give it one resource and make it scarce. The guide I read names mana as the core resource, with a cost on every monster, trap and room. Choose what the dungeon spends, how it earns it back, and what happens at zero. Then keep to the numbers.

    Build the central tension in. LitRPG Critic names the central bind: the dungeon needs adventurers to grow, and if they clear it, it dies. Write scenes where your core wants visitors and fears them in the same chapter.

    Make the dungeon fair. Woah77's rules for a good dungeon include difficulty that rises from easy at the entrance, and a way to bypass or beat every trap. Readers who like design want to see the logic. "Rocks fall, everybody dies" breaks that trust.

    Give the core someone to talk to. A mind with no body has no dialogue. Woah77 lists a fairy or other companion as a common trope, a guide who doubles as a sounding board. Another option is a visiting adventurer, a rival core or a merchant. Choose a voice that can disagree with the core.

    Show the adventurers as people. If invaders are only XP, the tension goes flat. Let some of them have goals, parties and reputations that outlast one floor.

    A planning list for the first arc:

    1. Write the core's starting state: size, resource pool, abilities and its one big weakness.
    2. List the first three rooms or floors and what each costs.
    3. Name the first adventurer wave and what it wants.
    4. Decide what the dungeon learns from that wave and spends on in response.
    5. Set the first outside threat that is bigger than the dungeon, since the genre often has one.

    Pace the growth. A dungeon can go from a cave to dozens of floors, so give it a limit at each stage and a reason to hit it. Spend a few chapters at each size. If every chapter ends with a bigger dungeon, nothing feels earned. See how to avoid power creep in progression fantasy for the same problem in a hero-led serial, and how to format LitRPG system messages for the status screens a core will read.

    What readers will check. Floor count, room names, monster types and spawn costs, who has died inside, and what the core knows about each visitor. After a hundred chapters, a trap that cost 20 mana in chapter 12 and 50 in chapter 90 gets a comment. A running page per floor, with monster list and costs by chapter, saves you from that. How to track LitRPG stats shows a layout that works for any numbers-heavy story, and the dungeon core genre page collects more about the form.

    PlotWrite keeps this ledger. It holds a page for every floor, monster, item and skill, with what is true at each chapter, and its Check chapter flags contradictions before you post. Memory, checks and planning write no story text.

    Frequently asked questions

    Does a dungeon core protagonist need a body?

    No. In the guides I read, most are disembodied minds bound to a crystal or core, though some get an avatar or golem. Pick one early and keep to it.

    What is the main conflict in a dungeon core story?

    LitRPG Critic describes the central bind: the dungeon needs adventurers to grow, but if they clear it, it dies. Your plot lives in how the core balances that.

    How do I stop a dungeon core story from becoming repetitive?

    Vary what each wave wants, give adventurers goals of their own, and bring in threats bigger than the dungeon. Fights alone will wear thin.

    Do I have to use mana?

    No. The guide I read names mana as the usual resource, but any scarce resource with a clear earning and spending rule does the same job.

    Sources

    1. LitRPG Critic: What is Dungeon Core? (read November 17, 2026)(litrpgcritic.pages.dev)
    2. Woah77: Dungeon Core, In the eyes of an Engineer (November 10, 2021; read November 17, 2026)(woah77.substack.com)
    7-day free trial

    Answer was helpful? See how plotwrite.ink helps with your story.

    plotwrite.ink learns your writing style, keeps track of your characters and world rules, and can draft the next chapter in your voice with your Claude or ChatGPT plan or your own AI key. Built for Royal Road, Wattpad, and serial authors who post weekly.

    Start 7-Day Free Trial
    • No credit card
    • Cancel anytime
    • Full Architect access
    • Works with your Claude or ChatGPT plan or your own AI key

    Read the full guide

    The LitRPG writing guide

    Built into plotwrite.ink

    Runs inside your project once you connect your own AI provider key (OpenAI, Anthropic, OpenRouter and others).

    Auto Story Bible
    Canon Sync contradiction checks
    Chapter hook scoring (in Canon Sync)
    Progression tracking

    Want all of these running on your serial? Start your free trial →

    Related quick answers

    What is LitRPG and how is it different from Progression Fantasy?

    LitRPG (literary role-playing game fiction) shows explicit game mechanics on the page: visible stats, levels, skill panels and system messages. Progression fantasy is any story built on measurable character growth, with or without a visible game system. All LitRPG is progression fantasy, but most progression fantasy is not LitRPG.

    How do you write LitRPG stat blocks readers actually enjoy?

    Good LitRPG stat blocks are short (under 15 lines), formatted in a consistent code-style box, appear no more than once every 3–5 chapters, and always reveal a story-relevant change. Show only what changed plus 3 to 5 reference stats, and hide everything that did not move.

    What is the best way to plan a LitRPG progression curve?

    Plot the protagonist's main stat or tier against chapter number and aim for a curve that slows over time, not a straight line. A workable rule of thumb is that each tier takes about 40% more chapters than the one before. Record every stat change against the chapter it happened in, so you can see where the curve really sits.

    How do you outline a 7-arc progression fantasy from scratch?

    Plot seven arcs of 25-40 chapters each. Give every arc four ingredients: one power tier transition, one new or escalated faction, one personal stake that resolves inside the arc, and one mythic stake that moves toward the series climax. Lay the skeleton on a board, then stress-test each arc before you write it.

    Does NovelMage work for LitRPG and progression fantasy?

    Partly. NovelMage works for LitRPG worldbuilding and visuals (maps, character portraits, class art), but it is not built to track stats, skills and promises across hundreds of chapters. For that, PlotWrite's Story brain (facts timed by chapter, stat sheets as of any chapter) and Canon check are a stronger fit. You write; PlotWrite remembers.

    How do you format LitRPG System messages so they stay consistent?

    Give every type of System message its own fixed format, such as one template for level-ups, one for skill gains and one for quests, and reuse the exact wording and punctuation every time. Keep each message short, show only what changed, and make sure every number matches your character sheet. Readers learn the format once, so any later change in it reads as a story event.

    What is the difference between LitRPG and GameLit?

    In LitRPG, the game mechanics are visible on the page: stat screens, levels, skills and System messages that the characters can see. GameLit is the looser, wider label for stories that borrow game settings or ideas without making the numbers part of the reading experience. Most writers and publishers treat every LitRPG as GameLit, but not every GameLit story as LitRPG, though the line is still argued over.

    Should a LitRPG be written in first person or third person?

    A LitRPG can be written in first or third person, and neither is required. First person gives the tightest immersion and a strong voice for reacting to System screens, while close third person keeps most of that and makes extra viewpoints easier. Pick first person if the hero's voice is the hook and you never need a scene they cannot see, and close third if the plot needs other viewpoints.

    What is a System apocalypse story?

    A System apocalypse story is a LitRPG subgenre in which a game system, with levels, classes and status screens, suddenly appears on modern Earth during a world-ending event. The hero stays in their own world, which is what separates it from isekai. The system gives the apocalypse a built-in power ladder, which separates it from ordinary post-apocalyptic fiction.

    Built for serial fiction writers

    plotwrite.ink auto-tracks your story bible, progression, and canon — so you can stay consistent long enough to actually earn from your serial.

    Start free — 7 days, no card needed