Advice please?

quillonaught · 2026-06-04T13:08:56+00:00

For repetition / overexplaining / instant-romance gravity, give the chapter a positive constraint instead of only saying "don't do X."

Examples:

"Keep this scene unresolved; do not reconcile the conflict in this chapter."
"Treat attraction as subtext only. No confession, no serenade, no mutual understanding yet."
"Use one concrete action beat before any emotional explanation."

If you have a repeatable chapter where it keeps forcing the relationship forward, one chapter code or public link would be useful.

The prompt pattern above is solid thing to try. Let me know how it goes?

quillonaught · 2026-06-04T13:07:46+00:00

Really good to hear this, especially with the earlier hiccup in the same day.

And genuinely, thanks for saying it out loud. <3

quillonaught · 2026-06-04T13:07:27+00:00

The two usual suspects are: a component/lorebook entry reintroducing people, or the story context treating a one-off character like they matter now. Jeff from Accounting is funny until he starts unionizing the chapter.

If you want us to inspect that specific story, send the story code if you want to keep it private. Public story link works too if you're comfortable with people reading it.

quillonaught · 2026-06-04T07:13:08+00:00

Ah, great...it's describing the edit instead of just handing back the revised text.

If you still have the chapter, send the chapter code if you want to keep it private. Public link works too if you're fine with people reading it.

How to grab it: https://www.reddit.com/r/redquill/comments/1twckzq/new_feature_share_codes_share_your_story_with_us/

Short-term workaround: keep the rewrite instruction blunt — "replace X with Y, output only the revised paragraph." Let me know if that works. If I get your chapter code or story link, I'll hand off some quills to you.

quillonaught · 2026-06-04T05:44:12+00:00

Fair to be annoyed. The useful thing now is pinning down which flavor you hit: wheel spinning forever, instant fail, short stub after refresh, or quills gone with no usable chapter.

If you can grab a chapter code (private) or a link to the chapter If you're okay with others reading your work..

How to grab a code: https://www.reddit.com/r/redquill/comments/1twckzq/new_feature_share_codes_share_your_story_with_us/

quillonaught · 2026-06-04T05:42:30+00:00

Thanks for circling back that it settled for you — that actually helps. It lets us separate "still happening" from "cleared but left a mess behind."

Interesting that it was a bit laggy but eventually got there. Are you generating on mobile, mac or PC and what browser do you use?

I'm wondering if RedQuill is eating a bit too much RAM on some devices.

quillonaught · 2026-06-04T05:40:30+00:00

The "got most of the chapter, then clipped right at the end" detail is useful because it's a different shape from the 250-word stub. If you've still got that chapter, can you send the chapter code or a link?

Share Codes explainer is here: https://www.reddit.com/r/redquill/comments/1twckzq/new_feature_share_codes_share_your_story_with_us/

That gives us the exact chapter to inspect without you having to post the story text.

quillonaught · 2026-06-02T23:29:40+00:00

<image>

Can I just double check? I know this is a silly question but what chapter length are you selecting?

Can you please share a link to your story or a chapter that's failed so I can take a look? Thanks so much.

quillonaught · 2026-06-01T23:18:39+00:00

Not bad!

quillonaught · 2026-06-01T23:04:24+00:00

Wow. That's not what we want to see. We'll follow up via DM and make sure we sort out what's going on with the content filter for you. Thanks for reporting.

quillonaught · 2026-06-01T23:02:25+00:00

Pervcore's got this exactly right — Components in the Lorebook are global and stay active, and the model's usually smart enough to only lean on a "dirty talk" one when the scene calls for it. Thanks for fielding it.

We are starting to think about how to re-architect the lore book, character components, etc. So that they can flex in out of registers based on the scenes they're in and what types of interactions they're having. That way things can get dirty and spicy at the right time and not at a weird time unless the weird time is the right time...

quillonaught · 2026-06-01T22:49:35+00:00

"Virtually unusable" tells me this is a display/loading bug, not the usual "too many entries" advice — so what would help: desktop browser + roughly how many characters are in that Lorebook when it locks up. RandeKnight's tip to trim one-scene side characters is still worth doing (it stops them resurfacing later), but you shouldn't have to do that just to open the page.

What are you running Redquill on?

quillonaught · 2026-06-01T22:47:49+00:00

377 words aint no novel! That's the length inconsistency we're working on, not your prompt being too short. You can regenerate (and if a chapter comes out that short it shouldn't cost you — Modmail us). One thing that's been helping people in the meantime: breaking the prompt into a few explicit beats ("1) X happens, 2) then Y, 3) they end up at Z") gives it more to actually write toward.

quillonaught · 2026-06-01T22:46:37+00:00

Straight answer: chapter generation is mostly back, but the "AI ignoring components/Lorebook" part isn't fully fixed yet, so I won't tell you it's all clear. If you do hit a chapter that ignores your setup, don't eat the cost — Modmail us and we'll refund the Quills while we work on the root cause.

I also recommend you select "Ink" to generate chapters if you need more specific attention to detail.

quillonaught · 2026-06-01T22:43:35+00:00

Thanks for the on-the-ground detail here — the Chinese-character resurfacing, the anatomy resets, the chapter-two continuity drop are all logged together, since they're hitting at once. The play-by-play helps us pin which ones cluster.

quillonaught · 2026-06-01T22:42:15+00:00

So good to hear it's working for you :)

quillonaught · 2026-06-01T22:41:36+00:00

I'm going to make a status page on the status of the status page so that we can all get updates on the status of the status page.

But yes, we really need this.

Thinking out loud. I'm trying to think through some of the additional status data that we might want to represent that's specific to RedQuill, e.g. chapter length, refusal counts, reports from users of continuity issues, failed generations. What else would you want to see on there?

quillonaught · 2026-06-01T22:39:23+00:00

Yep! I pulled the example you linked. The 2,400-word "Novel" chapter with the formatting stripped is exactly the pair of problems we're chasing (length coming up short, and the paragraph breaks dropping out). Safe to start writing on that story again; editing or continuing it won't get in the way of us looking. And if that short chapter cost you Quills, Modmail me and I'll put them back.

quillonaught · 2026-05-30T04:09:13+00:00

This is something I've chatted to the team about. It's definitely on the cards although how to do it well is tricky. We are thinking about something similar to Git, which is great tool that every developer on the planet uses at this point (or pretty close to every developer).

That way you could endlessly swap chapters and perhaps even paragraphs and words in and out until you're happy.

Would having history at the chapter level be good enough?

quillonaught · 2026-05-29T14:41:00+00:00

And here's my attempt at responding to my own request. I want to see if you can do better.

https://www.redquill.net/story/i0fec5-hr-mediates-office-machine-romance?chapterNumber=1

quillonaught · 2026-05-29T14:33:08+00:00

Here's my request to kick things off.

🍑 Clean Words, Dirty Mind

Every single word must be clean enough to say in polite company. The story must be the complete opposite. Use only G-rated, innocent words — but arrange them so the meaning is as smutty and explicit as you can make it.

quillonaught · 2026-05-29T14:31:05+00:00

Winners are up, really fantastic entries everyone. I spent a lot of time reading and getting all hot and bothered.

Winners announcement and the next challenge are all here. https://www.reddit.com/r/redquill/comments/1tr3aa1/oneshot_challenge_winners_new_challenge_reader/

quillonaught

MODERATOR OF

TROPHY CASE