
Morndur
A reader-run dark fantasy RPG where each cycle’s canon is shaped by public submissions.
Tagline
The story survives what readers submit.
A canon-making RPG with rules, not chaos.
The story continues when the cycle closes.
For readers who want votes to become canon.
The canon is crowdsourced, but the world still has rules.
This is the cleanest category-defining angle: Morndur is not a free-for-all forum, and not a normal serial novel. The fixed cycle, canonization, cast pages, and continuity controls make it distinct from generic collaborative writing.
An alternative to live RP and play-by-post forums that never die between sessions.
The asynchronous cycle solves the biggest failure mode of RP communities: scheduling. The page explicitly says no accounts, no slots, and anyone can submit, which makes it a strong replacement for forum RP and Discord threads.
For people who want audience participation without the fake choice of polls.
Unlike choose-your-own-adventure tools, submissions directly affect what survives into canon. The page emphasizes that the narrator weighs voices, amplifies consensus, and can even color-code individual contributions in email.
Primary user
Fans of collaborative dark fantasy fiction who want to influence a shared world without roleplaying live
ICP #1
Discord-based dark fantasy RP regular who already writes 100-500 word scene posts
Pain
They want to contribute to a living world, but live sessions, GM coordination, and strict character ownership make participation brittle and exhausting.
Why this solves
Morndur removes scheduling and account overhead, lets them submit in their own voice, and turns small scene ideas into canon on a daily cycle.
ICP #2
Indie fiction reader who follows serialized webfiction and likes voting on what happens next
Pain
They enjoy narrative participation, but most interactive stories are shallow polls with fake choice and little continuity.
Why this solves
Morndur treats submissions as source material for the next chapter, preserves continuity with cast/timeline/recap pages, and makes audience influence visible in the resulting canon.
ICP #3
Tabletop GM or homebrew worldbuilder running a gritty low-magic campaign
Pain
They need inspiration that feels earned by the setting, not random prompt garbage that breaks tone or lore.
Why this solves
The site’s own rules enforce tonal constraints, specific prompts, and consequences; the narrator folds off-tone submissions into the world instead of rejecting them, which is useful inspiration for GMs.
Strengths
- +The concept is immediately legible once you read the first few sections: cycle-based collaborative canon creation with no accounts.
- +The page does a great job of showing living activity with a current chapter, countdown timer, cast, and prompts, which proves the product is real.
- +The writing is distinctive and on-brand; phrases like "The Hold remembers" and "folds your impulse gently downward" create memorable identity.
Weaknesses
- −The homepage is overloaded with lore before it clearly explains the user action and payoff; a new visitor has to work too hard to understand the mechanic.
- −The product positioning is muddled by calling it an "MMORPG," which will confuse most people because this is not a traditional game loop, not a multiplayer combat system, and not obviously massive in the standard sense.
- −The CTA stack is repetitive and slightly noisy, with multiple near-duplicate submit/watch/read links competing for attention.
- −There is no crisp proof of community scale or contribution volume beyond the current cycle state; a skeptical visitor may wonder whether this is a novelty project with no traction.
- −The rules are interesting but buried; the best differentiators like no accounts, canon permanence, and contribution coloring should be surfaced much earlier.
Fix these
- Rewrite the hero to say exactly what happens in one sentence, then add one concrete example of a submission turning into canon.
- Replace or soften "MMORPG" with language like "asynchronous collaborative fiction game" or "reader-written narrative RPG" to avoid category confusion.
- Add a simple three-step explainer above the fold: submit a voice, cycle closes, narrator publishes the next chapter.
- Show social proof and activity signals more aggressively: total voices per cycle, recent contribution counts, or a live example of a colored email result.
- Create a sharper onboarding path for first-time contributors with one sample submission template and a strong example of what "specific" looks like.
- Reduce duplicate navigation and focus the primary CTA on one action: Add your voice.
Drop-in replacement copy
Headline
Readers write the canon.
Submit a voice during the cycle. The narrator publishes what survives.
Turn reader input into story
Anyone can submit a character action, rumor, scene, or wish while the cycle is open. When it closes, the next chapter is written from those voices.
Keep the world coherent
Cast pages, timelines, and recaps keep the story from becoming noise. The world remembers names, consequences, and loose threads.
Join without friction
No account, no slot, no live session. People can add a voice fast, then follow the result by email or RSS.
Stay on tone
The prompts and rules keep the fiction dark, specific, and usable. Even off-tone submissions get folded into the world instead of breaking it.
FAQ
Is this a game or a story?
Both, but it behaves more like a reader-run narrative RPG than a standard game. People influence the canon, and the result is a published chapter.
Do I need an account to submit?
No. You can submit without creating an account. Email is optional if you want delivery and contribution tracing.
What happens to my submission?
It goes to the narrator for the current cycle. The submitted text is not shown publicly; only the resulting story becomes canon.
How do you keep it from becoming chaotic?
The cycle structure, timeline, cast pages, and prompt scaffolding keep the world coherent. The narrator also decides what survives into the next chapter.
Who is this for?
People who like dark fantasy, collaborative fiction, tabletop lore, play-by-post RP, and serial stories where audience participation actually matters.
Polls are fake. Canon isn't. Morndur is a dark fantasy RPG where anyone can submit a character action, rumor, or scene during a cycle. When the cycle closes, the narrator turns the submissions into the next chapter. The story survives what readers submit.
No accounts. No slots. No waiting. Morndur lets readers add a voice to an ongoing dark fantasy story, then the narrator canonizes what matters at the cycle close. If you ever wanted to shape a world without joining a live RP session, this is for you.
Built a story engine that listens. Each cycle has a countdown, open submissions, recap pages, cast tracking, RSS, and email delivery. The hard part wasn't shipping the form. It was making sure the story feels like a world with memory.
The hardest part was continuity. If readers can influence the canon, the world has to remember names, wounds, grudges, and loose threads. So Morndur has timeline pages, cast pages, and recaps baked in. Otherwise it would just be decorative chaos.
Live RP dies for one reason: scheduling. People miss sessions, threads fragment, and the good ideas never land. Morndur keeps the ritual asynchronous. You add a voice when you have one, and the world moves on its fixed cycle.
Most interactive fiction cheats. It calls itself participatory, then hides behind shallow polls and fake branching. Morndur makes reader input part of the source material. No fake choice. The next chapter is built from what people actually submitted.
Watch a rumor become canon. A reader submits: "The chapel bells ring for the dead before dawn." The cycle closes. The narrator folds it into the chapter. Now it's part of the world's memory, not just a comment lost in a thread.
This is what participation looks like. 1. Submit a character action, rumor, scene, or wish. 2. Wait for the cycle to close. 3. Read the next chapter and see what survived. No account. No queue. Just a living dark fantasy story.
Readers keep asking for more cycles. That’s the signal I trust: not hype, not empty clicks, but people returning to see what the world does next. Morndur works because it gives fans a real way to leave a mark without breaking the tone.
People are already shaping the canon. Some send grim whispers. Some send names. Some send entire scenes. The narrator chooses what survives, but the raw material comes from readers. That’s the whole point.
Angle: Why I built an alternative to live RP
I built Morndur because live RP keeps breaking on the same thing: scheduling. People are busy. Discord threads drift. Great ideas die because the group never gets back in the same room. Morndur is an asynchronous dark fantasy RPG. Anyone can submit a character action, rumor, scene, or wish during an open cycle. When the cycle closes, the narrator reads the submissions and publishes the next chapter as canon. What mattered to me was not "interaction" in the shallow sense. It was continuity. If readers can shape a world, the world has to remember them. So the product includes: - cycle countdowns - cast tracking - recaps and timelines - email delivery - RSS - prompt scaffolding for people who want to add something fast The important rule: submitted text is never shown publicly. Only the resulting story is. That keeps the focus on the fiction, not the comments. If you care about collaborative storytelling, dark fantasy, or any kind of audience participation that doesn’t feel fake, I’d love feedback.
Angle: Audience participation without fake polls
Most interactive stories are not interactive. They ask readers to vote between two options, then quietly force the outcome the author wanted anyway. I wanted something more honest. Morndur treats reader submissions as source material for the next chapter. People can add a character action, a rumor, a scene, or a wish. The cycle closes at a fixed time. The narrator turns the submitted voices into canon. That means participation changes the actual story, but the story still has rules. It stays dark. It stays coherent. It stays readable. I think that distinction matters. A lot of “community storytelling” tools are really just polls with nicer typography. Morndur is trying to be a living narrative system. If you’ve ever wanted your audience to matter without letting the world collapse into chaos, this is the experiment. I’d especially love feedback from people who read serial fiction, run tabletop campaigns, or build world lore for fun.
Angle: What makes the world feel real
The thing I kept obsessing over while building Morndur was this: How do you let strangers influence a story without making it feel random? The answer was rules. Not heavy rules. Just enough structure that the world feels like it remembers. So Morndur has: - a fixed submission cycle - a visible countdown - cast pages - timeline and recap pages - prompt suggestions when people don’t know what to add - email delivery so contributors can follow what happened next That structure does two jobs. It helps first-time readers understand what to do. And it helps the fiction stay disciplined. I don’t want “anything goes.” I want a dark fantasy world where reader voices can leave marks that survive. If you’re building for a niche audience, I think this is the lesson: clarity beats cleverness. Make the mechanic obvious. Make the output worth returning for. That’s what I’m trying to do here.
Tagline
Reader-written dark fantasy, canonized by cycle
Description
Morndur is an asynchronous dark fantasy RPG where readers submit character actions, rumors, scenes, or wishes. Each cycle closes, the narrator turns the best voices into canon, and the next chapter is published.
Maker's first comment
I built Morndur because I kept seeing the same failure mode in collaborative fiction and RP spaces: the ideas are good, but the format gets in the way. Live sessions depend on schedules. Discord threads disappear. Polls feel like fake choice. I wanted a story system where people could contribute on their own time and still feel like they actually changed the world. So Morndur lets anyone submit a voice during an open cycle, then the narrator folds those submissions into the next chapter as canon. The submitted text never gets posted publicly; only the resulting story does. I also added cast tracking, timelines, recaps, RSS, and email delivery because once people care about a world, they need memory. I’m launching this for readers who like dark fantasy, tabletop GMs, webfiction fans, and anyone who wants audience participation without turning the story into a mess. If you try it, I’d love to know whether the mechanic feels clear and whether the world feels worth returning to.
Pinned maker comment
I’d love feedback on the first-time experience: does the mechanic make sense in under 10 seconds, and does the homepage make it obvious what a reader should do next?
Meta
Live RP keeps breaking on schedules.
Targeting Discord RP players and tabletop fantasy fans. Hypothesis: people who already write scenes will participate more if they can submit asynchronously and see their words turn into canon. Morndur lets readers add a voice during a cycle, then publishes the next chapter from those submissions.
Google Search
Asynchronous dark fantasy RPG
Targeting searchers looking for collaborative fiction, play-by-post RPGs, and audience participation in stories. Hypothesis: users want a real mechanic, not a poll. Morndur accepts submissions, closes on a timer, and turns reader voices into the next chapter.
Reddit Promoted
Polls are fake. Canon isn't.
Targeting r/SideProject, r/indiehackers, and fiction/RP-adjacent readers who like weird experiments. Hypothesis: a clearer mechanic plus visible continuity will beat generic interactive fiction. Morndur is a reader-run dark fantasy story where submissions become canon at the cycle close.
Subreddits
r/SideProject
Show the product as a weird but real shipped experiment: reader submissions becoming canon in a dark fantasy story.
Rules: Lead with what you built and what you learned. No obvious promo; include screenshots or a demo gif and ask for feedback.
r/indiehackers
Write about the problem of building for a niche audience with a mechanic-driven product, not a SaaS dashboard.
Rules: Share the build and the validation process. Avoid pure marketing copy; frame it as a lesson or experiment.
r/worldbuilding
Ask for feedback on continuity systems, cast tracking, timeline design, and how to keep collaborative lore coherent.
Rules: Be genuinely useful to worldbuilders. Focus on the system and examples, not on pushing signups.
r/fantasy
Share the concept as a new way for readers to influence an ongoing dark fantasy serial without fake branching.
Rules: Keep it story-first. Mention the mechanic briefly and emphasize the fiction experience.
r/RPGdesign
Discuss the asynchronous narrative loop as a game design problem: cycle, submission, canonization, continuity.
Rules: Make it about design tradeoffs. Show structure, feedback loops, and what makes it different from a forum or poll.
Communities
Post the build story, not a product pitch. Share how you validated a niche fiction mechanic and what happened when you stopped treating it like a normal SaaS.
Discord servers for OSR / tabletop worldbuilding
Join as a contributor first. Share one useful prompt system, one continuity trick, and one example of a reader submission becoming canon before mentioning Morndur.
Post short, evocative updates with a chapter link and a one-line mechanic explanation. Engage with serial fiction writers, not growth accounts.
Cold outreach template
Hi {firstName} - saw your {context} and thought of Morndur, a dark fantasy story where readers submit actions/rumors/scenes and the next chapter becomes canon from those voices. If you like collaborative fiction or RP that doesn’t depend on live scheduling, I’d love for you to try one cycle and tell me if the mechanic makes sense.
Product Hunt timing
Launch on Tuesday at 12:01am PT. PH skews U.S.-centric, and Tuesday gives you a full weekday of visibility after people catch up from Monday; for this ICP, it also avoids weekend drop-off and gives fantasy, indie, and maker communities time to react throughout the day.
Indie Hackers post ideas
- 01I built a dark fantasy RPG where readers submit canon
- 02Why polls are the wrong mechanic for interactive fiction
- 03What I learned building for a tiny, obsessive niche
Competitor alternatives
Current tone of voice
Mythic, ominous, and ritualistic, with a very deliberate literary voice; e.g. "The narrator listens. The story is what survives."
Your kit is ready. Sign up free to unlock, takes 10 seconds.
7 more X posts · 2 LinkedIn · Product Hunt copy · ad hooks · 100-user playbook · landing critique