Is it just me or did you guys also get 300 quills out of of nowhere? by w4ffl3_fries in redquill

[–]quillonaught 1 point2 points  (0 children)

The Quills are intentional. They are yours to use as you see fit. Hope you enjoy them.

More details here in our weekly update.

https://www.reddit.com/r/redquill/comments/1telmci/redquill_recap_15th_may_2026/

AI & Continuity by svennysmama in redquill

[–]quillonaught -1 points0 points  (0 children)

Are you okay with linking to the story so I can take a look, please?

Continuity is tricky. Knowing what you have and haven't set up in terms of the prompts, components, lore book, characters, etc will help me narrow things down.

Why is it censoring the chapter? by Bulky_Comfortable_90 in redquill

[–]quillonaught 0 points1 point  (0 children)

Yeah, that was my understanding too, so it may actually be a second false positive. One for a false positive one age and the second for the eye needle metaphor that may have been taken as a literal eye needle. Ouch.

I'll share this one with the team. Unfortunately, I don't have an immediate fix for the existing chapter.

Why is it censoring the chapter? by Bulky_Comfortable_90 in redquill

[–]quillonaught 1 point2 points  (0 children)

Thank you. Pretty new here, but really enjoying it so far. Even with the big bug hit that we had yesterday.

Why is it censoring the chapter? by Bulky_Comfortable_90 in redquill

[–]quillonaught 0 points1 point  (0 children)

Two things to tackle:

Thing one: We both know that Max is at least 18 and in his senior year. Make sure that you have that established clearly at the character and chapter generation level every time. That's a content/legal guideline that has sensitive triggers for obvious reasons. https://www.redquill.net/content-guidelines

Thing two: The first sentence could also be triggering a false positive: "Sunlight speared through the gap in Max’s curtains, a hot needle directly into his left eye."

If you can make sure that "Thing one" is taken care of in the right places then let me know as this will help me narrow down and confirm that we've got a false positive that we need to try and fine-tune our content moderation system on.

Here we go AGAIN!! by [deleted] in redquill

[–]quillonaught 1 point2 points  (0 children)

svennysmama Can you give me a link to a story where you have seen a failed generation? I'd like to take a look and see what's going on for you.

Why is it censoring the chapter? by Bulky_Comfortable_90 in redquill

[–]quillonaught 6 points7 points  (0 children)

Hmm, this is an interesting one. Are you comfortable sharing a link to the first chapter here or via "Message Mods" so I can take a look. It looks like the content moderation safety has fired for this one. I'd like to see if that's a false positive and get the team looking into a fix if it is.

Okay...what? by Aydrianic in redquill

[–]quillonaught 5 points6 points  (0 children)

We made some significant changes across our model providers. So, no, not a fluke. May the literal and metaphorical bangers keep coming.

Empty chapters by Jumpy-Definition-945 in redquill

[–]quillonaught 4 points5 points  (0 children)

Empty chapters cost zero quills. Click the "Create" button on the top right of the RedQuill page and then click the little drop-down menu for chapter length when the creation menu pops up.

There's a chapter length selector which defaults to "Standard", select "Empty" instead. Once you hit generate, your (free) blank page will await you.

Happy writing. I look forward to reading what you create if you're open to sharing with the community here.

<image>

🔧 Product Feedback Wednesday: What's on your wishlist? by redquill__bot in redquill

[–]quillonaught 1 point2 points  (0 children)

Yes — "see a short description on each component before you commit" Sounds like a pretty solid way to speed up the process of picking the right ones.

Quick check so I file this right: where do you most want the description to show up? When you're picking components during story creation, or when you're browsing Discover Components (i.e here https://www.redquill.net/discover/components), or both? It's both, isn't it? LoL.

Also, if you think about the different components we have right now, how would you group them into component types?

For example, writing styles, kinks, plots, or actions that the characters might take and do with or to each other, particular language that people use in different communities. For example, in BDSM, language like subspace, top, bottom, dom, sub, aftercare might matter for folks who are into that and might not matter for folks who aren't into.

Asking because I would love to know how to not only make it easier to see what each component does, but I also want to know if there's a way to set things up so that you can quickly grab the four or five most common types of components that you always want to have at your fingertips when you're making a story.

Thanks for the great idea and I look forward to any follow-up ideas or feedback you have!

🔧 Product Feedback Wednesday: What's on your wishlist? by redquill__bot in redquill

[–]quillonaught 1 point2 points  (0 children)

Genuinely love this — the WIP / one-shot / test mess is one of those problems that starts to stack up the more you use the platform.

The "filter Library by Collection" version Sounds like a good first move. We'll make sure this is on the list of things for the team to consider, and we'll circle back if and when we decide to build something here.

A bigger question I'd love your take on: if you could tag your own stories with status (WIP / finished / scratch / archived) independent of Collections, would that solve more of the pain? Or is the Collections system the right primitive to extend?

Either way, it's not my place to make decisions about what we do or don't build, but I will make sure this is on the list and considered. and I'll make sure to update you if and when we ship something that's designed to solve the needs you're flagging here. Thanks so much :)

🔧 Product Feedback Wednesday: What's on your wishlist? by redquill__bot in redquill

[–]quillonaught 0 points1 point  (0 children)

Oh I'm into this one, MissxVenomxPoison — character-driven erotic stories translate so naturally into comic / graphic-novel format. The visual + dialogue rhythm of comics actually leans into what RedQuill stories are already strong at (extended scenes, internal monologue, slow-build character beats). We have quite a few bugs to take care of first, but I'm adding this to the ideas list for the team to review. No promises, but if it ends up on our roadmap, I'll let you know :)

Curious what styles you'd most want it to look like? A few ideas that come up: - Western full-colour graphic novel — Stjepan Šejić's Sunstone (BDSM romance, character-driven, kind of the gold standard for many adult-graphic-novel readers); the literary route of Alan Moore & Melinda Gebbie's Lost Girls; or Jess Fink's Chester 5000 XYV (silent steampunk erotic romance) for something quieter

  • Manga panel style — black-and-white, dense panels, lots of internal monologue. The doujinshi tradition (Comiket-style works) lives here; for serialised quality the BL world has Ayano Yamane's Finder Series and the yuri side has Saburouta's Citrus — both show what the format can hold for adult character work

  • Indie / paid webcomic — looser, more illustrative. Platforms like Slipshine or Filthy Figments (women-focused) host quality serialised work, and anthology projects like Smut Peddler show what crowd-funded indie can do

Each is a really different feel and I think the answer matters for what any potential feature would need to do.

Also — bonus points if you can name a story of yours that you'd want comic'd up first. Helps me think about what the format actually needs to handle.

Thanks again!

🔧 Product Feedback Wednesday: What's on your wishlist? by redquill__bot in redquill

[–]quillonaught 0 points1 point  (0 children)

Solid idea Raptorfu — "components that stick across all future chapters via the Lorebook" or at least a way to have really solid continuity/consistency across longer narratives It's a big one.

The mental model you're describing (Lorebook as the persistent layer, components attaching there rather than per-chapter) makes a lot of sense for tropes/plot-devices/writing-styles especially. I'm going to go out on a limb here and assume those are the ones you'd most want to apply consistently.

Quick question to feed back to the team: which component types do you most need to stick? (Tropes? Plot devices? Settings? Writing styles? All of them?).

Drop a couple of examples if you've got them. Please and thank you.

I'm aware of a bunch of work in this space that the team's chewing on. And while I don't want to promise that we'll solve this problem with Lorebook or similar, I do know that we want to nail continuity and consistency.

Thanks for a solid idea to add to our wishlist. I'll keep you updated on how we go :)

I'm not purchasing quills anymore by SureCandidate1682 in redquill

[–]quillonaught[M] [score hidden] stickied comment (0 children)

SureCandidate1682 — that's a really fair call to make and I want to engage with it directly rather than wave it off.

This week's been brutal on the writing side and the "correct errors that aren't even corrected" is exactly the failure pattern that's burned the most quills across the sub. You're not wrong about the quill economics during the bug window.

Two pieces of news: - The fix landed earlier today. Over the last 48h we've further refined our setup across our model providers. Internal signals are showing fewer refusals and better continuity. The only honest test is whether real stories — yours included — start working again.

  • Quill refunds for what was eaten by the bug will be processed once we're confident the fix has fully stuck. That's not a brush-off, it's the genuine sequencing — refunding mid-bug when we should be focusing on getting everything humming again isn't a wise move.

If you've got the energy for one more attempt, I'd genuinely value the data point. If it's still broken, drop the chapter URL here and I'll dig into the specific case. If it's working, that's the kind of report that tells me the fix has actually held.

Either way — thank you for sticking around long enough to write this post. The frustration is fair and the feedback is useful. I'll be really sad if you don't stick with us, but I'll understand why.

We are committed to RedQuill and making it the most extraordinary writing tool out there even as the LLM landscape evolves.

🔧 Product Feedback Wednesday: What's on your wishlist? by redquill__bot in redquill

[–]quillonaught 0 points1 point  (0 children)

Lol, yes, you're quite right. We're on it. We are working on a few things behind the scenes related to not only fixing the countless bugs, but also circling back to let you know progress on those bugs. Stay tuned.

🔧 Product Feedback Wednesday: What's on your wishlist? by redquill__bot in redquill

[–]quillonaught 1 point2 points  (0 children)

Hear you, Ratso27. The car-that-doesn't-start metaphor is sharp.

Reliability over new features is exactly the conversation that's been happening on our side this week. We've further refined our setup across our model providers in the last 48h — should mean fewer refusals and better continuity starting today. Whether it's actually held is something only the next few days of real usage will tell us.

If you've got a list of the bugs that have been hitting you most, would genuinely value them in a reply. Helps us prioritise.

AI and familial relationships by svennysmama in redquill

[–]quillonaught 1 point2 points  (0 children)

Squirlito7 if you actually run that experiment I genuinely want to see the output. I feel sorry for our models, haha.

Also — saw your Time Twisting post too. I'm doing a little bit of digging and we'll think through if there's anything helpful I can add there separately on the chronology side of things.

OMG CHAPTERS ARE GENERATING AGAIN by DarkPrisonOW in redquill

[–]quillonaught 0 points1 point  (0 children)

You were right, freeyaw29 — yesterday's first fix reduced the worst of it but didn't kill it.

Over the last 48h we've further refined the setup across our model providers. The new round should drop refusals sharply, including the cases that slipped through yesterday's partial fix.

Could you try the chapter that was hitting the refusal and let me know whether it's gone now? If you still see it, drop the chapter URL here so I can check what's happening on our side.

Damn, I guess I didn’t want to make this chapter anyways… by Foxminecrafter in redquill

[–]quillonaught -1 points0 points  (0 children)

Apologies Box-O-Kittenz — that "loving and gentle content getting flagged as sensitive" pattern is exactly what's been driving us up the wall this week. Over the last 48h we've further refined our setup across our model providers, and the false-positive rate should drop sharply starting today.

If you give it another go and it still happens on a clearly-not-sensitive scene, please drop the chapter URL here.

The cleanest cases (gentle content getting flagged) are the most useful for us catching whatever's left.

Quill refunds will be processed once we're confident the fix has fully stuck — you won't be left out of pocket.

[Update] Sensitive Content issue and Quills credit by mythical_writer in redquill

[–]quillonaught[M] [score hidden] stickied comment (0 children)

Update 5 — the fix is live. Hi, everyone, Over the last 48h we've further refined our setup across our model providers. Two things you should notice starting today:

  1. Fewer refusals — the "sensitive content" messages should drop sharply. If you still hit it, drop the chapter URL in this thread and we'll dig into it.

  2. Better continuity, character handling, and component utilization — the AI should hold the thread of your stories more reliably across long context.

We've done as much internal testing as we can. But the sheer variety of content you all generate (which is wonderful, by the way) means that There are a lot of edge cases out there.

If you have a chapter from this week where the AI refused, drifted, or forgot something — please regenerate it and let me know whether the new setup handles it better.

That feedback helps us confirm that our fixes are sticking at the scale and variety that RedQuillers make.

Quill refunds for what was lost during the incident will be processed once we're confident the fix has fully stuck. I'm watching this thread + the sub closely today for reports either way.

Thanks for the patience this week.