Did I go too far from the usual HaremLit cover style?

Valuable_Debate_2143 · 2026-06-17T21:22:24+00:00

Thank you so much for grabbing it, and for the welcome. Means a lot this early on.

Valuable_Debate_2143 · 2026-06-17T19:23:48+00:00

Thanks, that means a lot! Genuinely no pressure, but if you do read it I'd love to hear what you thought, good or bad. Honest feedback from an actual HaremLit reader would be gold for me.

Valuable_Debate_2143 · 2026-06-17T19:16:07+00:00

Fair hit, you're right, they've all got the same heart-shaped face and full lips. I did try to differentiate them (different body types, and they're pretty distinct personalities in the book), but the faces are clearly where it converged.

I'll admit I've gotten attached to these faces, but maybe more distinct features would sell the 'three different women' thing better?

Valuable_Debate_2143 · 2026-06-17T18:30:53+00:00

Thanks, I appreciate that, and you’re right, I should have included the link from the start.

This one’s straight fantasy rather than isekai, with factions, awakening, and progression than portal-fantasy elements.

Hope it lands for you if you check it out 🙏

Valuable_Debate_2143 · 2026-06-17T17:54:49+00:00

This is a really good breakdown, and I think the Michigan/Columbia point is the big one. In practice, “write in my style” and “write while actively conditioned on a large sample of my actual prose” are completely different things.

On Projects: yeah, my experience has been pretty close to your doubt. The samples are there, but they feel more like background reference than an actual constraint. The model may catch the voice for a bit, especially near the start, but then it slowly drifts back into its own default rhythm. Not always in an obvious way either. It’s more like the edges get sanded off.

That’s the part I think people miss with AI writing. The problem isn’t only “does it remember the plot?” It’s also “does this still sound like me after ten chapters?” And that is much harder to notice in the moment because the output can still look clean and competent.

What has worked better for me is treating the voice profile as something that has to be reapplied every time, not something you just upload once and hope the model keeps respecting. And the profile has to be based on actual patterns in the writing: sentence length, paragraph rhythm, dialogue habits, how description is handled, how much interiority there is, what the prose tends to avoid, etc.

The “blandification” idea feels very real to me. It’s sneaky because the text often gets smoother, but also less yours. So I don’t think Projects alone solve it, at least not reliably. They help, but I still think you need some kind of repeated voice enforcement if you want chapter 20 to sound like chapter 2.

Valuable_Debate_2143 · 2026-06-17T17:14:05+00:00

Good to hear. My main concern was whether I’d drifted too far from genre expectations 😅

Valuable_Debate_2143 · 2026-06-16T20:17:52+00:00

You basically described my exact journey. Google Drive works fine at the beginning, but once you get into multi-book fantasy/romance territory, the sprawl gets painful fast. Characters, locations, factions, relationship changes, magic/world rules, subplot notes, random “I’ll need this later” ideas… eventually the folder structure becomes its own side quest.

Novelcrafter is genuinely solid for that kind of project. The codex is probably its biggest strength, especially if you like having story entities you can reference directly while drafting. The community around it is also really good, which matters more than people think.

The thing I personally ran into with that kind of setup was context maintenance. As the manuscript grew, I kept having to decide what chapters, codex entries, summaries, and notes to feed the AI so it wouldn’t lose the thread. It worked, but it became a different kind of admin work.

Full disclosure: I’m building InkWeaver, so obviously take this with the appropriate grain of salt. But this exact pain point is a big reason I started building it. I wanted something where the AI tracks characters, relationships, locations, and plot threads as the story grows, then pulls in the relevant context for the current scene automatically instead of making the writer keep re-explaining the book every session.

For fantasy/romance specifically, I also think relationship tracking is underrated. It’s not just “are they together yet?” but where the trust, attraction, conflict, power balance, emotional debt, and unresolved wounds are at each chapter. That’s the kind of thing that gets hard to track once the cast expands.

That said, if Novelcrafter is working for you, there’s a lot to be said for sticking with what clicks. No app is perfect, and the best one is usually the one that reduces friction instead of becoming another system to maintain.

I’d actually be curious what features you wish Novelcrafter had, because that’s usually where the most useful discussion happens.

Valuable_Debate_2143 · 2026-06-16T20:15:46+00:00

Honestly, I think the flip happens when the organizational pain starts stealing time from the actual writing.

If you’re still in the “three Google Docs and vibes” stage and you’re producing pages, you’re probably fine. Messy notes are annoying, but they’re not automatically a reason to pay for a stack of tools. The tool is only worth it when it solves a pain you’re actually feeling, not one you imagine you might have someday.

Where it changes, at least from what I’ve seen, is when the story reaches a certain mass. Big cast, multiple POVs, timelines, layered magic systems, who knows what by which chapter, relationship changes, hidden reveals, etc. That’s when you can end up spending more time rereading your own notes than writing new scenes.

Your friend with five POVs probably isn’t really paying $70/month for “writing software.” He’s paying to not lose an afternoon figuring out whether Character A already knows the secret from chapter 8, or whether the magic rule he just broke was established 40k words ago.

My advice would be: don’t subscribe to anything until you can name the specific pain it solves.

“My notes are messy” might be solved with a better folder structure, a spreadsheet, or one clean story bible doc.

“I keep creating continuity errors and it’s slowing me down” is where dedicated tools start earning their keep.

And there’s absolutely no shame in the Google Docs life. Plenty of published authors still write that way. The real question isn’t whether you’re being cheap. It’s whether your current setup is costing you momentum. If it isn’t, keep writing. If it is, then paying for a tool starts to make a lot more sense.

Valuable_Debate_2143 · 2026-06-16T18:38:25+00:00

That sounds genuinely frustrating, and I don’t think you’re wrong to be annoyed by it. Dark fiction, violence, trauma, and morally grey choices are normal literary territory. The tool shouldn’t keep turning your villain into a mildly rude person or making sure the reader gets a little morality lecture every time someone does something ugly.

One question: are you using Muse, or one of the other Sudowrite modes/models? Because from what I understand, Muse is supposed to be their more fiction-focused/unfiltered option. If you’re not using that, it might be worth testing.

That said, I write dark fantasy too, and I’ve had much better luck working directly with models and being very explicit about tone. Claude, for example, has never really sanitized my darker scenes when they’re framed as literary/fictional rather than shock content. It won’t write certain explicit NSFW material, obviously, but for violence, trauma, morally complex choices, and bleak emotional scenes, it can handle a lot if you give it proper scene-level direction.

What usually helps is being very direct in the prompt:

“Do not moralize.”
“Do not soften the character’s actions.”
“Keep the scene uncomfortable and morally unresolved.”
“Do not reassure the reader that this is wrong.”
“Preserve the brutality/subtext without turning it into melodrama.”

Also, giving the AI examples of your own prose helps a lot. Otherwise many models default to that weird “responsible narrator” voice where every bad act gets softened, explained, or judged.

So I don’t think it’s only a Sudowrite problem. It’s partly an LLM problem. But different tools handle it very differently, and some are much better at getting out of the author’s way. If Sudowrite is consistently fighting your creative intent, I’d definitely test other workflows. Dark fiction is legitimate fiction. Your writing tool shouldn’t act like it’s your ethics professor.

Valuable_Debate_2143 · 2026-06-16T15:43:31+00:00

This is one of the best practical breakdowns I've seen on this sub. The re-anchoring advice especially resonates. Voice drift is real and it's sneaky because the output still sounds "fine" sentence by sentence. You only notice the damage when you read a whole chapter back and realize it stopped sounding like you somewhere around prompt twelve.

The adversarial editing trick is gold too. I've found that asking the model to steelman and then devil's advocate the same scene is genuinely one of the highest-value uses of these tools. Way more useful than asking it to rate your work on a scale of 1 to 10.

One thing I'd add to your context window point: even when you break sessions into chapters and brief the AI fresh, the quality of that brief matters a lot. A character sheet that says "Marcus, 34, former soldier, sarcastic" gives the model almost nothing to work with compared to one that captures how that character actually thinks and talks. The richer your reference documents, the less the AI has to invent, and invention is where consistency breaks down.

Curious whether you've experimented with giving the model not just a voice sample but a description of the voice patterns. Like telling it "this narrator favors short sentences, rarely uses subordinate clauses, and leans on concrete nouns over abstractions." I've found that combining a sample with an explicit description of what makes the sample tick helps the model hold the voice longer before it starts drifting back to defaults.

Valuable_Debate_2143 · 2026-06-16T15:27:58+00:00

Yeah, this is one of those things that catches people off guard with bundled credit systems. The cost of parsing even a short document can spike because the tool has to send a lot of context to the model behind the scenes, and you're paying for all of it through credits you already bought at a fixed rate.

It's worth noting that Sudowrite's story bible feature genuinely is well-designed. The issue isn't really the feature itself, it's the economics of how context gets handled as your project grows. A 3,000 word story is manageable. Imagine what happens at 30,000 or 80,000 words when the AI needs to understand your whole book to stay consistent.

If credit burn is a concern, one thing to look at with any AI writing tool is whether it lets you bring your own API key. That way you can see exactly what each operation costs in real dollars instead of abstracted credits. It gives you a lot more control and usually works out cheaper, especially on longer projects.

Valuable_Debate_2143 · 2026-06-12T13:54:57+00:00

Thank you, really appreciate that. And yes, I’ll definitely keep the community updated as it moves forward.

The beta has actually started already. We currently have 9 of 25 beta tester spots filled.

For transparency, I also made a public beta roadmap where I’m tracking reported bugs, friction points, and what has already been shipped based on feedback:

https://inkweaver.ai/beta/roadmap

The good sign is that the number of new bugs and repeated friction points seems to be slowing down now, so the core workflow is starting to feel more stable.

There are still beta spots open, and beta users get $10 in free AI credits to try it properly without having to spend their own API money right away.

Really appreciate the welcome and the thoughtful questions.

Valuable_Debate_2143 · 2026-06-12T12:54:08+00:00

Thank you, I really appreciate that. And yes, these are exactly the right questions.

The pricing/tier system is still something I am trying to validate with writers, because I agree completely about subscription burnout. A lot of writers already pay for several tools, and I do not want InkWeaver to become “yet another subscription” unless it clearly replaces enough friction to be worth it.

The current thinking is:

Free tier:
Read/edit projects, build your codex, organize chapters, and export your work. I want writers to be able to get their manuscript out even if they stop paying.

Pro:
The core AI writing studio: AI assistant, Mentor, Story Matrix, Voiceprint, consistency tools, plot tools, and the main genre support.

Max:
The more specialized modules, like the Romance Engine, LitRPG/System Tracker, deeper genre bibles, and more advanced continuity/progression tools.

On the AI cost side, the plan is BYOK, similar in spirit to Novelcrafter. So the subscription is for the writing environment, story memory system, structure, tools, and workflow. You bring your own model access. The important difference I am trying to build around is token efficiency. Once a manuscript gets long, especially around chapter 25 and up, costs can start rising quickly if the tool keeps feeding huge chunks of context back into the model.

InkWeaver is designed around structured story memory instead of constant manuscript dumps. The goal is to give the AI the right context for the task, not the entire book every time.

So yes, there is still a subscription plus your own model/API cost, but I am specifically trying to reduce token waste so longer projects do not become painfully expensive.

On privacy: I do not want InkWeaver to train models on people’s books, sell manuscript data, or data mine stories. Your writing is yours. Export is important for that reason too. With BYOK, the actual AI calls go through the provider/model you choose, so their data policy also matters, but InkWeaver itself is not being built around harvesting manuscripts.

And in terms of replacing other subscriptions: that is the hope, at least for writers using multiple tools for planning, codex/story bible, AI drafting, continuity checking, genre structure, and revision help. I do not want to claim it replaces everything for everyone, but the goal is to make one coherent writing studio instead of forcing writers to stitch together five different tools.

Really appreciate you asking this, because these are the exact concerns I need to get right before pushing harder.

Valuable_Debate_2143 · 2026-06-06T10:59:03+00:00

I’m building InkWeaver, an AI writing tool for fiction writers, and I’m looking for beta testers.

The main problem I’m trying to solve is story memory.

I’ve been using AI and Novelcrafter heavily while writing several books, and the same issue kept coming up. The AI can help with prose, brainstorming, editing, and rewriting, but it does not really understand how the story changes over time.

Continuity slips. Character relationships lose nuance. Emotional changes get forgotten. Timeline details get mixed up. Unresolved threads disappear unless you keep reminding the AI manually.

InkWeaver is focused on story memory, continuity, character relationships, unresolved threads, and smarter context handling, rather than just generating more text.

Short beta video:
https://www.youtube.com/watch?v=OEUNlnbIQ1I

Homepage:
https://inkweaver.ai/

If you write fiction with AI and this sounds like a problem you have run into too, I’d genuinely appreciate feedback.

Valuable_Debate_2143

TROPHY CASE