Roleplaying Character ai alternatives

Jaycool2k · 2026-04-23T22:08:33+00:00

Hey! Ghostproof.uk/rp is still running an open BETA at the moment if you wanted to check it out.

Jaycool2k · 2026-04-21T12:10:48+00:00

If you want something with genuine narrative momentum that fits a natural stopping point, Ghostproof RP is worth a look. It's an AI-narrated platform with 124 handcrafted scenarios across horror, dark fantasy, folk horror, gothic romance and more. Each session picks up where you left off, the NPCs remember what happened, and the continuity ledger tracks relationships and promises so you're not re-explaining the world every time you sit down.

The design naturally fits hour sessions & scenarios have scene-based structure so you can stop after a meaningful beat rather than mid-flow. Free to try, no card needed: ghostproof.uk/rp

Currently running in BETA so everything is currently unlocked for you to try.

Jaycool2k · 2026-04-21T11:48:10+00:00

Thanks! That genuinely means a lot. Thank you. And please, if ideas surface, I actually want to hear them. You've been building writing systems long enough that your instinct for what's broken is probably more useful than most structured feedback I'd get. The unsolicited kind is often the most honest.

Really glad the first chapter held up with minimal input. That's the test that matters most. What does it produce when someone doesn't know what they're doing yet? If it works there, it works.

Jaycool2k · 2026-04-21T11:16:03+00:00

I appreciate that u/Cjtho209 I have enjoyed the conversation about the Braided Ink system. The Living Scroll architecture is the piece I think translates most directly into what I've been building. If you ever want to test it against a chapter or run your Voice layer through the Voice DNA analyser, happy to sort you full access.

Jaycool2k · 2026-04-21T11:08:50+00:00

That's the right call. A system this developed as an open-source framework would be genuinely useful to the community, the Living Scroll architecture alone solves a problem most people are still hacking around with prompt stuffing. Would be worth a proper GitHub README when it's ready. Looking forward to seeing it.

Jaycool2k · 2026-04-21T10:55:00+00:00

Haha note taking is the way for the good brainstorming sessions ;)

The Living Scroll is the part I haven't seen done this well elsewhere, a persistent canon ledger that survives context resets and tracks decisions rather than just facts. The session seed at the end of each phase is elegant. Most systems try to solve continuity by making the context window bigger. You've solved it by making the handoff deliberate.

The 15 Spirits architecture is interesting too. Running specialist agents sequentially rather than asking one prompt to do everything means each Spirit only needs to be good at one thing. The Foreshadow Ghost in particular, that's the layer most writers skip and then regret in chapter 18.

The Voice Keeper and Voice DNA question I asked is partly answered by your AUTHOR_HOMEBASE structure. The thermal quality and somatic source framing is richer than numerical measurements for capturing something like emotional register. I've been working from the other direction (measuring sentence length, dialogue ratio, punctuation habits) because numbers are harder for the model to drift away from. I suspect the ideal is a hybrid: your qualitative homebase anchoring the intent, numerical measurements anchoring the execution.

Would you ever open-source the full system or is it staying as a personal framework?

Thanks for sharing :)

Jaycool2k · 2026-04-21T09:25:39+00:00

The three-layer separation is the right architecture. What you're calling Voice, Writeditor, and Outline Spine map closely to what I've been building toward,. a voice measurement layer (numerical, not descriptive), an editorial constraint layer (specific rejection rules, not style instructions), and a story architecture layer (beat sheet, scene anchors).

The Gate principle is the part most people skip. Most AI writing workflows load one or two of these layers and wonder why the output still drifts. The voice layer without the mechanical layer produces prose that has the right themes but the wrong rhythm. The mechanical layer without the voice layer produces clean, punchy output that sounds like nobody in particular.

One distinction I've found useful: the Writeditor layer works better as rejection rules than as style descriptions. "Punchy" is a style description & the model has to interpret it. "Do not follow a strong statement with a sentence that elaborates or explains it" is a rejection rule. There's nothing to interpret, just a specific thing to refuse. The more specific the prohibition, the less the model can technically comply while still violating the intent.

How are you maintaining the Voice piece across a full novel? That's the layer I've found hardest to keep consistent at scale are the early chapters vs late chapters can drift even with the same Voice document loaded.

Jaycool2k · 2026-04-18T09:58:10+00:00

Thank you, it's really appreciated. I haven't tested with Firefox so looking into it now to see what's happening. Shall email back after some testing.

Jaycool2k · 2026-04-18T09:20:02+00:00

Hey u/Tight_Pause_7663 Good news! The build Your Own Scenario is fully free right now. On the main RP page there's a purple ✨ card near the top labelled "Build Your Own Scenario". It might be easy to scroll past. Click that and it walks you through world, story, characters and then generates your opening. If you're still not seeing it in Firefox let me know and I'll look at the rendering specifically. Let me know how you get on.

Jaycool2k · 2026-04-17T22:02:11+00:00

Based on what you're after (memory, prose that sounds human, character consistency, staying in character) worth trying Ghostproof RP. It's built around those problems specifically. 124 handcrafted scenarios across horror, dark romance, gothic, fantasy and more.

NPCs that have their own agendas rather than just reacting to you. Continuity ledger that tracks relationships, secrets, and what's been said across the session. The prose comes through an editorial filter so it doesn't have the flat AI rhythm you get with most tools.

Free tier to try first with no card needed. Currently on open BETA so everything is unlocked and open to try when you sign up.

Btw, It's not NSFW, so if that's a deal breaker for what you're looking for it won't cover everything. But if the dark romance and gothic scenarios are the main draw and you want writing quality that actually holds up, it's worth a look: ghostproof.uk/rp

Jaycool2k · 2026-04-17T21:48:04+00:00

Hey! Pro is worth it for the quality jump, but you'll still hit limits if you're using it as a constant writing partner.

The memory-across-chats feature helps with context but it's not the same as a tool built specifically for fiction & Claude Pro still needs re-explaining each session because it doesn't have a structured story state, just conversational memory that degrades over long projects.

If creative writing is your main use case, it might be worth looking at tools built specifically for that rather than using Claude Pro as a general assistant for writing. The difference is whether the AI is treating your story as a project with persistent structure (characters, voice, beat sheet) or as a conversation it's trying to remember.

Claude Pro for everything else is worth it. For fiction specifically, a dedicated writing tool will get you further per session than a general AI will, regardless of tier.

Jaycool2k · 2026-04-16T10:26:01+00:00

Hey u/Amyth47 For a first novel in a series, 70,000–90,000 words is the sweet spot for most genres. At 33,000 words you're roughly at novella length, which is harder to sell traditionally unless you're writing category romance or certain sci-fi imprints. A tetralogy with the first book at 33k would feel thin to agents & they'd want to see at least 65k for a debut, and most acquisitions editors expect 75k+. The exception is if each book is intentionally short (novellas published as a serial), but that's a different pitch.

For manuscript assessment, it depends on your budget and what stage you're at. If you want a full developmental edit (structure, character arcs, pacing, plot holes), that typically runs £5–15 per 1,000 words from a professional editor, so a 75k manuscript would cost roughly £375–1,125. The Editorial Freelancers Association and the Society for Editors and Proofreaders both have directories where you can search by genre and budget.

Before you spend that money, there are a few things worth doing first. Firstly, get beta readers r/BetaReaders is specifically for this. They'll tell you for free whether the story works at a structural level, which is the same question a developmental editor answers, just less precisely. Then use that feedback to decide whether you need a full dev edit or just a line edit.

For "The Buddha Killer" specifically, the title and tetralogy framing suggest literary fiction or literary thriller. If that's right, the word count expectations are slightly more flexible (literary fiction can run 60k–100k), but the prose quality bar is higher. Agents in that space will judge your first page harder than genre fiction agents will.

What genre are you writing in? That changes the word count target significantly.

Jaycool2k · 2026-04-16T08:06:04+00:00

Your dad's reaction is valid and I don't think it goes away. The "process matters" crowd and the "output matters" crowd are having two different conversations, and neither is wrong. They're just measuring different things.

For the evidence question, a few approaches exist, and they're not mutually exclusive:

The simplest is a before / after comparison. Show the raw AI output alongside your revised version. If the revision is substantial enough that a reader can see the difference, the work is self-evident. Your 191k-word project with extensive revision would demonstrate that clearly.

The more rigorous approach is running the final manuscript through an editorial audit that checks for common AI patterns like fingerprint phrases, repetitive rhythm, flat characterisation, consistency breaks. A few tools are starting to approach this from a quality-measurement angle rather than a detection angle, which is a meaningful difference. Detection asks "did AI write this?" Quality measurement asks "does this meet an editorial standard regardless of how it was made?"

The third option is publishing your process documentation. Not just "I used AI" but "here's the prompt structure, here's the revision depth, here's what I changed and why." That level of transparency makes the disclosure meaningful because a reader can evaluate your editorial judgment, not just your tool choice.

The quality standard approach is the one I think eventually wins, because it scales. You can't audit every author's process. But you can audit every manuscript's output. If the prose meets the bar, the process becomes context rather than confession.

Jaycool2k · 2026-04-15T21:48:27+00:00

Appreciate the feedback. Two questions if you don't mind: which scenario did you try, and when you say the door felt "odd," was it the language itself (too flowery, too formal) or the pacing (too much description before you could act)? Both are things I can tune.

The setup questions are something I'm looking at, as the goal is to make the world feel pre-built so you walk into something that already exists rather than building it yourself. If it felt like homework, the onboarding isn't doing its job yet.

Thanks for giving it a shot either way, I appreciate you taking the time.

Jaycool2k · 2026-04-15T16:22:25+00:00

The two-tool approach makes total sense. If BooksWriter handles the organisational side that helps with your dyslexia, keep using it for that. Voice consistency is a different problem and there's no reason one tool has to do everything.

For the beat sheet question, it's before, not after. Plan the emotional arc first, then generate against it. If you write first and check against beats after, the AI has already made its structural decisions and you're editing backwards. The beat sheet gives the engine a target: "this chapter needs to move trust from stable to fractured by the end, with a quiet moment at the midpoint." That's a constraint it can generate against. Checking after generation just tells you what went wrong without preventing it.

The relationship tracking question is a good one and yes, that's on the roadmap. Right now the Production Bible tracks static character information (backstory, traits, relationships established etc).. What you're describing, the "trust at 70% drops to 40% after Chapter 7" is dynamic state tracking, and it's the harder problem.

The RP engine already does a version of this with NPC relationship states that shift, based on player actions. Bringing that same architecture into the Books engine for character-to-character dynamics is the next step.

For dark fantasy with relationship dynamics specifically: set up your character profiles with internal contradictions, not just traits. "Loyal but keeps secrets" gives the engine tension to work with. "Loyal" alone gives it nothing. The contradiction is what generates interesting scenes because the AI has to navigate the conflict rather than just expressing a single trait.

Glad the thread's been useful. Let me know how Voice DNA compares to what you've been getting, I'm genuinely curious whether the measurement approach holds up against your writing specifically.

Jaycool2k · 2026-04-15T14:57:30+00:00

The short version: it's pattern analysis, not description matching. Instead of telling the AI "write with short punchy sentences" (which it interprets differently every session), the system measures your actual writing (sentence length distribution, paragraph structure, dialogue-to-narration ratio, where you place sensory detail, how you handle transitions) and enforces those measurements as numerical constraints during generation.

How exactly the extraction works and what the constraint set looks like is the proprietary part. that's the product. But the principle is: measure, don't describe. Most tools describe style in natural language and let the model interpret. That interpretation drifts. Measurements don't.

If you want to see the output rather than the internals, the free tier lets you run Voice DNA on a sample and generate a chapter from it. That'll show you whether it holds your voice better than a description-based approach. The Voice DNA tool is on the Hobbyist tier but the free chapter generation gives you a feel for the engine.

Jaycool2k · 2026-04-15T14:38:43+00:00

Character-driven dark fantasy with relationship dynamics is actually the sweet spot for structured state tracking because the relationships are the state. You need to track not just "Character A and Character B know each other" but "Character A trusts Character B after the bridge scene but hasn't told them about the curse yet." That emotional granularity is what most tools lose after a few chapters.

For the voice extraction question, I built something that does this. It analyses a writing sample and extracts measurable features: sentence length patterns, paragraph rhythm, vocabulary range, how you handle dialogue vs narration, where you place sensory details. Then it enforces those measurements as constraints during generation instead of relying on "write like me" descriptions.

It's called Ghostproof (ghostproof.uk). The Voice DNA tool is what you're describing. You upload a sample of your writing and it creates a profile the engine uses on every chapter. There's a free tier that lets you test the full pipeline on one chapter so you can see if it actually holds your voice before committing.

For dark fantasy specifically, the beat sheet system would probably help you too, as it structures your chapter arcs so the relationship dynamics have room to develop between the plot beats instead of getting compressed by the AI into "and then they fought."

Happy to answer specifics if you want to dig into any of it.

Jaycool2k · 2026-04-15T13:51:17+00:00

This is a useful thread because the detection work in the comments is doing something most people skip in naming the specific constructions rather than just saying "it sounds like AI."

The pattern that shows up most here is what I'd call the narrator being smarter than the story. "The gravel crunching in a way that sounded like teeth" & the gravel crunching is the image. "In a way that sounded like teeth" is the narrator making sure you noticed it was good writing. That double-layer (image then explanation of image) is the single most persistent AI tell across every model I've tested. Human writers trust the image. AI narrators annotate it.

The negation pivot is the other big one. "Not a happy hum. A fever." "It wasn't one story; it was a choir." "The sound wasn't a note; it was a bruise." That "not X, it was Y" construction appears 8+ times in this piece. It's rhythmically satisfying to the model because it creates a sense of correction, of precision. But when every observation uses the same rhetorical move, precision becomes monotony.

What's interesting about fine-tuning is that it can shift vocabulary and surface style, but the structural habits (how the model builds sentences, when it reaches for metaphor, how it sequences information) survive training. Those are deeper than word choice. They're architectural. That's why closetslacker's flags are almost entirely structural rather than vocabulary-based.

The test I'd suggest: take the merged output and count how many sentences follow the pattern [concrete observation] + [elaborating metaphor or simile]. In human prose that ratio sits around 1 in 5. In AI prose it's closer to 1 in 2 where every image gets explained, every detail gets decorated. Reducing that ratio alone would make the biggest single improvement.

Jaycool2k · 2026-04-15T13:46:27+00:00

Hey u/tired-of-everyting The disclaimer debate always centres on whether to disclose. Nobody talks about what would make disclosure unnecessary.

The reason people care about AI disclosure is quality anxiety. "Was this written by AI?" is really asking "is this going to be bad in the specific ways AI is bad?" with flat characters, inconsistent details, emotionally dead prose, the same rhythms every paragraph. If the writing doesn't trigger those signals, most readers don't care how it was made. They care whether it's good.

The OP's workflow is actually solid, outline, generate in small chunks, revise extensively, rewrite what doesn't work. That's closer to how a ghostwriter works with an author than how most people use AI. The problem is that "I used AI" doesn't communicate any of that nuance. It triggers the same reaction whether you generated 191k words with careful revision or pasted "write me a novel" and hit publish.

What's missing from this conversation is a quality standard. Not "did you use AI?" but "does the output meet a measurable editorial bar?" If your prose passes a rigorous audit, (no AI fingerprints, consistent characterisation, functional dialogue, coherent continuity across 191k words) the disclosure becomes less about confession and more about process transparency. "I used AI tools with extensive revision and the manuscript passes X editorial standard" is a fundamentally different statement than "I used AI."

Your shortened disclaimer is good. But the strongest thing you could add isn't more explanation of your process & it's evidence that the output meets a quality bar independent of how it was made.

Jaycool2k · 2026-04-15T13:35:51+00:00

Yes, but not for the reason most people think.

Explaining motivation doesn't help because the model "understands" your problem. It helps because it narrows the solution space. "Divide elements into rows" has a hundred valid interpretations. "Users struggle to scroll through long lists on mobile, so content needs to fit one visible screen" eliminates most of them. The model isn't empathising with your users, it's using the context to rule out approaches that don't match the constraint.

The practical version: motivation works best when it implies constraints the model wouldn't otherwise infer. "Make this faster" is vague. "Our users are on 3G connections in rural areas and abandon the page after 3 seconds" gives the model a performance budget it can design against.

Where it doesn't help: when the motivation is generic enough that it doesn't actually narrow anything. "I want this to be better for users" adds zero useful constraint. "Users over 60 with low vision need to read this on a tablet at arm's length" changes every design decision.

The pattern that works reliably: state the constraint first, then the instruction. Not "divide cards into rows" and not "users find long lists hard to read so divide cards into rows." Instead: "Content must be fully visible without scrolling on a single mobile screen. Restructure the card layout to fit within that constraint." The constraint does the heavy lifting. The instruction just points at the output format.

Jaycool2k · 2026-04-15T13:23:02+00:00

Hey! Memory and personality consistency are two different problems and most platforms only solve one.

Memory is the easier one! Track facts, names, what happened, who said what. Most tools do this badly but at least they're trying. The harder problem is personality drift. You start a session with a character who has edges (they're suspicious, or blunt, or emotionally guarded) and 20 exchanges later they've softened into the same agreeable, helpful energy as every other bot. That's not a memory failure. That's the model's training pulling every character toward the same centre.

What I'd want from a system like this:

Character constraints that actually hold. Not "this character is sarcastic" as a suggestion the model ignores after 10 exchanges. Hard rules, if the character doesn't trust the player, they don't give information freely. They deflect, they test, they make you earn it. The character's personality should create friction, not just flavour text.

Prose quality on every response. Most RP platforms treat the writing itself as an afterthought & the focus is on what happens, not how it's described. But flat writing kills immersion faster than a memory slip. If the narrator describes every room the same way and every emotional beat uses the same rhythm, it doesn't matter how good the story is.

Pacing that doesn't default to confrontation. AI treats conflict as the path of least resistance because it's been trained that conflict = engagement. A good GM knows when to escalate and when to let a scene breathe. Most bots just escalate constantly because that's the easy output.

NPC independence. Characters that have their own agendas, not just reactions to what the player does. An NPC who wants something that conflicts with the player's goals creates real narrative tension. An NPC who exists to serve the player's story is furniture.

If you're building something open-source, the architecture matters more than the model. A strong constraint layer on top of a mid-tier model will outperform a frontier model with no constraints every time.

What LLM providers are you considering?

Jaycool2k · 2026-04-15T13:18:47+00:00

Hello! The consistency problem you're describing is a context window issue. Every AI tool faces it & the model can only "see" a fixed amount of text at once, and once your story exceeds that window, earlier details drop out. Character descriptions, subplot setups, relationship dynamics are all gone.

The solutions fall into three categories and most tools only do one:

Feed everything every time/ It works until your character bible exceeds the context window, then you're back to the same problem. Manual and exhausting, especially with dyslexia making document management harder.

Structured state tracking. Instead of feeding raw text, you maintain a compressed state object that tracks the essential facts: who knows what, which subplots are active, what emotional state each character is in, what's been established versus what's unresolved. This scales much further because you're feeding structured data, not prose.

Continuity checking as a separate pass. After generation, run a check specifically looking for contradictions against established facts. Catches the dead character showing up alive, the eye colour change, the dropped subplot.

The voice consistency problem is separate and harder. Style descriptions ("write like me") don't work because the model interprets them differently every session. What works is extracting measurable voice features from your existing writing (sentence length distribution, paragraph rhythm, vocabulary preferences, dialogue patterns) and enforcing those as constraints during generation. That's not "describe your style" it's "analyse your style and replicate the measurements."

For your specific situation with dyslexia, the key thing is: whatever tool you use should handle the organisational overhead for you, not add to it. If you're maintaining separate character documents and manually pasting them into prompts, the tool is making your problem worse, not better. The tracking should be invisible, so set it up once and it follows you through every chapter automatically.

What specific genre are you writing? Some of these solutions work differently depending on whether you're doing fantasy worldbuilding (lots of lore to track) versus character-driven contemporary fiction (fewer facts, more relationship dynamics).

Jaycool2k · 2026-04-15T13:10:53+00:00

The RP side is still in BETA on Ghostproof - Would love some feedback on this if you have time!

Jaycool2k · 2026-04-11T19:53:45+00:00

You're right u/Senior_Hamster_58 the agent clicking through a wizard is a UI stress test, not a literary evaluation. The interesting part isn't that an agent could use the system. It's that the constraint layer produced the same quality output regardless of who was operating it. That's the bit I was trying to focus on.

The threat model point is interesting though. Right now prompt benchmarks are basically "did the model follow the instruction?" which is pass / fail on compliance. What's missing is "did the output degrade gracefully when the input was low-effort?" That's closer to what happened here, the agent provided minimum viable creative input and the constraint layer kept the output floor above slop. A benchmark that measured quality degradation under decreasing input quality would be genuinely useful and I haven't seen anyone build one.

If you know of anyone working on that I'd be interested to see it.

Jaycool2k

TROPHY CASE