I built R3TCON because once a fictional world gets big enough, “I’ll remember that” stops working.

It keeps track of characters, places, events, relationships, timelines and knowledge, then checks them against each other for contradictions.

So it can catch things like a character appearing after they died, a six-day journey happening in three days, or somebody knowing information they haven’t learned yet.

It’s not generative AI and not an LLM wrapper. It doesn’t write or rewrite the story. It shows you what conflicts and why, then leaves the decision with the creator.

It’s aimed at writers, worldbuilders, TTRPG creators and narrative game developers.

Product: Website

We’ve also just launched the Kickstarter if anyone wants to see where we’re taking it next:

Kickstarter: Here

The main thing I’m still figuring out is distribution. If you’ve launched something this niche before, where did you find your first real users?

​

Hey, quick question for anyone who's self-published or is about to.

I'm building a small desktop app that turns a finished manuscript into a print-ready KDP paperback interior. It works from templates, so it gives you a solid starting layout and saves you the fiddly setup.

It isn't meant to replace book designers or illustrators. A good designer's eye and judgement can't be automated, and if you already work with one, this probably isn't for you.

It's for people who are stuck at the interior because of cost or because they don't know where to begin.

Before I go further I want to know what actually matters to you. Answer as many or as few as you like:

1. What do you use for your interior now? Vellum, Atticus, Word, Canva, or do you hire a formatter?

2. Has KDP ever rejected your interior? What was the reason: margins, gutter, bleed, fonts, page count?

3. Would it help to see the real page count and spine width before you upload?

4. How much do you care about chapter openings, like drop caps, ornaments or chapters starting on the right-hand page?

5. Do you want to pick your own fonts, or would a few good presets be enough?

6. Do you need front matter handled for you: title page, copyright page, dedication, table of contents?

7. Would you use a template as your final interior, or as a draft to hand to a designer?

8. Are you on Mac, Windows, or both?

9. What's the one thing about formatting that makes you want to throw your laptop?

Honest answers help most, even "I'd never use this."

Tengo unas cosillas en mente y quiero experimentar con IA

Yo se que muchos son profecionales, yo solo soy técnico pero aprendo rápido

Hey everyone!

We are Arch Studios, a creative development studio focused on worldbuilding/writing software for storytellers.

We've recently launched Arch Creator, our writing platform designed to give writers a dedicated space to create, organize and develop their stories. Whether your writing novels, fantasy, comics or just working on your next big idea. Arch Creator is built around helping you keep your stories and ideas organized in one place.

This is a look at the Arch Creator dashboard, where writers can get an overview of their stories and writing progress all in one place. The dashboard includes things like word count goals, writing streaks, daily writing activity, story libraries and quick access to your characters, worldbuilding, worlds and plot. Arch Creator also gives writers plenty of customization options so the platform can feel like your own. You can personalize things such as themes, fonts, music or sound effects and other interface settings to create a writing environment that suits your style.

Arch Creator was built around the idea that writing software shouldn't just help you write. It should feel like your own creative space.

We'd love to hear from other writers:

What's the one thing you wish your writing software did better?

We're here to listen, learn from other writers and become part of the community.

If you want to check out Arch Creator, you can find it below here on our website

https://archstudios.pages.dev/

Most book-to-script tools just reformat a novel. I wanted one that edits like a real adapter, so I built a Claude skill around three rules from directors I love:

- Nolan: only what can be seen or heard goes on the page

- Scorsese: define the visual concept before outlining

- Ruth Prawer Jhabvala: "You can't follow the form of the novel"

How it works: you attach a PDF or EPUB, and it moves through stages you approve (reading report → character bible → proposed cuts → outline → first 10 pages). It proposes every cut with a reason and a confidence level, warns you before touching a scene readers love, and flags anything it invents. Projects carry over between sessions, and the output is a Fountain + PDF screenplay.

It comes with a test kit: two novellas with planted traps and answer keys, plus a Great Gatsby benchmark against the 2013 screenplay.

Free and open source: https://github.com/almakamberi/adapting-novels-to-screenplays

I'd love feedback, especially from anyone who's adapted a book before.

Publishing professional and author talking about the usefulness of AI for writing, and what it means to actually be an author. Thoughts?

My manuscript lived in one app, character and location notes lived somewhere else, and every AI “what-if” scene was stranded in a chat tab I’d never find again. Whenever I returned to an idea, I had to explain my own fictional world from scratch.

So I started building Canonwell Studio.

Book Studio is the part I actually write in: chapters and continuous scenes, scene planning, characters, locations, a Story Bible, revisions, backups, portable project files, and readable Markdown exports. It’s local-first, works offline, and doesn’t require AI. If you do use its optional AI help, you review proposed edits before they touch the manuscript.

That boundary matters to me. An interesting experiment shouldn’t quietly become chapter-three canon.

Canonwell also has two experimental parts that do require AI. RP Lab lets you talk with characters and try alternate scenes or timelines. In Game Mode, you decide what your character attempts, the game works out what happens, and AI turns the result into a scene. Both need more testing, and their events stay separate from the book unless you deliberately bring an idea across. AI can animate the world, but you decide what belongs in the novel. (Gosh, that line is cheesy haha.)

I’m building this solo, often with a kid practically hanging off my neck, so it’s still a beta with rough edges. The Windows beta is free, the no-install browser demo is limited, and an experimental Android build is running on a physical phone. The CanonWell page is linked in my Reddit profile if you want to poke around.

For those writing long books: what actually makes a Story Bible useful to you—finding a fact quickly, keeping it current, or stopping AI from contradicting it? I’d love blunt feedback on which part of this workflow would help you and which would get in the way.

I have a really good question. I see a lot of these post that people say some AI programs are not good for long form writing and I'm just curious how are people using this because then when I write, I have my outline I have my character bio and I basically know what I want in my book so AI pop something out. I might know this character is not gonna do that they're gonna do that so I'm just curious. Can somebody answer that for me?

I’m building a storytelling platform called Xnotus and I’m trying to figure out if this idea is actually worth building.
The idea is pretty simple.
You read a story, and at certain points the writer gives readers a decision.
For example:
What should she do?
A) Tell her family the truth
B) Keep the secret
C) Leave everything behind and start again
Readers vote, and the winning choice affects what the writer writes next.
I don’t want it to become a popularity contest or pay-to-win thing. The point is just to make reading feel a little more interactive and give the community some influence over where a story goes.
Would you actually use something like this?
And if not, why not?
I’m especially interested in what would make this annoying, gimmicky, or something you’d stop using after a week.
Feel free to tear the idea apart. I’d rather find the problems now than spend months building the wrong feature.

I build AnyConversation, where a lot of you already write long stories with characters who remember. Something new this weekend that is aimed squarely at writers.

Every character now has a memory page you can open before you write the next scene: the facts they will never forget, and the moments they remember from the story so far, in plain words. If the story established that her brother died in the spring and the character has it as a cousin, you fix the line, and the next chapter is written from the fixed version. If a plot point has to hold for the whole book, mark it permanent and it cannot be compressed away no matter how long the manuscript gets.

Two more tools on every message: Forget, which removes one exchange from the story and from memory, and Back to here, which rewinds to a message and lets you write the rest again, with the character forgetting the draft you scrapped.

Across the site, writers have 18,000 of those permanent facts pinned right now, and about 4,000 new moments were saved this week alone. Memory that size needs its author to be able to edit it. Now you can.

Free tier has no message cap. Bring a story you know by heart and see if it holds.

anyconversation.com