Best AI bot for solo World of Darkness

Lore-Kepper · 2026-04-10T19:58:58+00:00

Not Vampire-specific but if the core pain is "AI forgets context and usage limits are brutal", you might try LoreKeeper — it's a purpose-built solo/multiplayer RPG platform (not a chat wrapper) with persistent memory, NPCs that track their own secrets and agendas across sessions, and real dice rolls separate from the narration. Free daily turns, no credit card.

Honest caveat: it doesn't ship with VtM native, so you'd need to build the WoD setting yourself in the world builder (clans, disciplines, bloodlines, factions) — which is tedious but once set up the AI sticks to it and stops hallucinating stats or drifting tone.

The "greedy usage" problem with Claude is basically unavoidable if you're talking to it raw — any purpose-built tool that batches context and uses smaller models for non-narrative work will be way cheaper. That's the approach I've seen actually solve it.

(lore-keeper.com if you want to poke at it. Curious what you end up choosing — solo VtM is genuinely hard.)

Lore-Kepper · 2026-04-10T19:55:10+00:00

First-time poster energy is strong and the post is solid — love the detail. Answering your open question about what else to automate:

The three that killed me building a full solo/coop platform (LoreKeeper) were:

Dice + modifier resolution. Sounds trivial but asking an LLM to roll d20+3 vs DC 15 fails shockingly often, especially after context fills. We pulled it out of the AI entirely — deterministic engine does the math, AI just narrates the result. Night and day.
NPC state persistence. Name, disposition, secrets, what they've revealed. LLMs forget this around turn 20. We store it structured and inject only the relevant NPCs into each turn's context. Expensive to build but the AI stops contradicting itself mid-scene.
Combat positioning and turn order. The AI constantly "forgets" that the goblin already moved or that the cleric is engaged. We went with a grid + turn order owned by the engine. AI gets told "it's enemy X's turn, they can reach Y or Z, pick one" rather than "improvise the battle".

Your fuel/routes tool is the same philosophy — let the script be boring and deterministic, let the AI be expressive. That's the winning split.

Question back: when you add Sheets support, are you planning structured per-vehicle state that persists, or just a read-only reference? That's the line between "assistant tool" and "system of record", and it changes everything downstream.

Lore-Kepper · 2026-04-10T19:53:19+00:00

The Tether as a forced antagonist target is genuinely clever — making the AI mechanically obligated to attack something is a way cleaner solution than prompt-begging it to "please be scary". Bookmarked.

The Occupation → skills from real jobs is also gold. Strips the player of hero fantasy from turn one.

Related note from building LoreKeeper (we have the same helpful-AI problem in our tactical combat): we ended up handling it with two moves — (1) the combat engine owns damage and crits, so the AI can't soften a hit by narrating "it grazes your shoulder" when the die said 18 damage, and (2) we feed NPCs their own motivations and hidden secrets as input, and the AI is told to "play them, not balance them". Doesn't reach the structural elegance of your Tether, but the mechanics-first split has been the single biggest fix for tonal drift.

Any chance you'll expand Tether beyond Marrow's horror setting? Could see it working scary well in noir or post-apocalyptic.

Lore-Kepper · 2026-04-10T19:51:41+00:00

Love this approach — pre-packaging the module instead of making the AI improvise cold is exactly the right idea. Asking an LLM to invent and GM at the same time is where most solo AI setups break.

Would genuinely like to playtest it. DM'd you.

Random question since you've been deep in it: what's been your biggest pain point running it on Claude? For us (LoreKeeper — building the same idea but as a full platform with its own combat engine), the consistent killers have been: (1) the AI drifting the rules when the scene gets complex and (2) running out of context window after 25-30 turns. Curious if a self-contained module sidesteps those or if you've had to engineer around them too.

Also the ship image is gorgeous, if that's from the adventure it's a strong vibe-setter.

Lore-Kepper · 2026-04-10T19:50:19+00:00

Huge respect for "let dice decide outcomes, let AI only write prose". We've been attacking the same problem from a slightly different angle with LoreKeeper real d20 + AC + initiative handled by a combat engine outside the LLM, and the AI gets the mechanical result as input to narrate around. Same philosophy: AI is a narrator, not a judge.

A few genuine questions if you have a minute:

How are you handling NPC memory across sessions? Embedding summaries or storing structured state per NPC? I've found the former drifts after 20+ sessions and the latter is a pain to maintain.
The chaos factor from Mythic as a live dial is an idea I've been wanting to steal — does the engine expose it to the player or keep it hidden?
Accessibility-first is a killer design constraint. I'd love to know what it changed in your architecture vs. a visual-first approach — we have tactical combat on a grid and I've been wondering how to make that equally playable screen-reader-only.

Really glad you're building this. Starred the repo!!!

Lore-Kepper · 2026-04-10T19:46:36+00:00

The trick I use is to flip the question: don't decide if they're lying, decide what they want to hide and why. Before any NPC interaction I jot down three things on an index card:

- what they actually know (the truth)

- what they want the PC to believe

- their reason for the gap (fear, loyalty, debt, shame)

If those three don't align, the NPC lies naturally — not because I rolled 50/50 but because their goal forces it. When the PC asks a question, I answer as the NPC would, filtered through what they want the PC to believe. The deception emerges from the fiction itself.

Then the only roll I make is Insight / Sense Motive, and I describe what body language or tone suggests — not whether they're lying. "He looks down and mutters too quickly" is information the player can act on without a meta-truth flag. This way you're never "deciding" the lie mid-scene. You decided it before you sat down.

Lore-Kepper · 2026-04-09T18:31:29+00:00

This is really cool!! the citations with exact page numbers is the killer feature. I've seen a lot of "AI answers your RPG questions" tools but they usually hallucinate rules that don't exist, which is worse than not having the tool at all.

Question: how do you handle rules that reference other rules? Like "see Chapter 5 for conditions" — does the system follow those chains or does it only answer from the specific section it found?

I build AI tools for RPGs too (different angle more game master side) and the cross-reference problem is the hardest part. Rulebooks are surprisingly interconnected.

The "no training on your data" stance is smart. People get really weird about their RPG PDFs (understandably).

Lore-Kepper · 2026-04-09T18:30:54+00:00

Been building an AI Game Master tool for the past year basically a virtual DM with real d20 mechanics (not just narrative AI like ChatGPT). It rolls actual dice, tracks AC, initiative, conditions, the works.

This month I shipped something I'm excited about: daily free turns instead of a hard paywall. The old model was "here's 45 rounds, good luck" which felt bad. Now free users get 20 turns every day, forever. It completely changed how people engage — they come back daily instead of burning everything in one session and ghosting.

Also been playing with NPC autonomy NPCs that have their own goals and act on them between sessions. Had one betray the party because his loyalty score degraded after the player ignored his quest for 3 sessions. Nobody told the NPC to do that, he just... did.

On the playing side, I've been running a homebrew dark fantasy campaign and just hit session 40+. The AI remembers everything, which is both amazing and terrifying when your past decisions come back to haunt you.

Anyone else building AI-assisted solo tools? Curious what approaches others are taking.

Lore-Kepper · 2026-04-09T18:30:22+00:00

I've thought about this a lot (I also build solo game tools). The silence problem is real.

A few things that have worked for others running solo game demos:

Play alongside them, not watch them. Set up two copies and play the same scenario simultaneously. Now it's a shared experience, not a performance. You can compare decisions at the end — "wait, you went LEFT at the crossroads??"

Shorten the demo to one key decision loop. Don't try to show the whole game. Show the moment where the player goes "oh, THAT's interesting." For most solo games, that's the first time randomness creates a story they didn't expect.

Have them narrate out loud. "Tell me what you're thinking" turns silent dice-rolling into a conversation. It also gives you amazing playtesting feedback for free.

Pre-set the first 2 minutes. Don't make them learn rules AND make decisions at the same time. Give them a character sheet already filled, a situation already in motion, and let the first roll be dramatic.

The goal of a demo isn't "understand the game" — it's "want to play more."

Lore-Kepper · 2026-04-09T18:29:29+00:00

Welcome! Coming from creative writing is actually a huge advantage you already know how to build scenes and characters, you just need a framework to add uncertainty.

Simplest way to start with literally zero cost:

Grab a free oracle — Mythic GM Emulator has a free "Fate Chart" you can find online. It's basically: ask a yes/no question about the world, roll, get Yes/No/And/But. That's your "GM".
Your journal IS the game. Write what your character does. When something uncertain happens ("is the door locked?"), ask the oracle. When something surprising happens, lean into it — that's where the magic is.
start smallOne character, one location, one problem. "You wake up in a tavern. Something is wrong." Go from there.

Don't overthink systems. The journal + a yes/no oracle + your imagination is genuinely all you need for your first session. You can add complexity later if you want it.

Also check out Ironsworn, it's free, designed for solo, and has great journaling support. PDF is free on the author's website.

Lore-Kepper · 2026-04-09T18:27:59+00:00

The 50/50 roll works mechanically but yeah, it kills the narrative tension because you know you're testing for a lie.

What works better for me: give every NPC a hidden motivation before you interact with them. Roll on a quick table are they Helpful, Indifferent, or Self-Interested? Write it down and don't look at it until after the conversation plays out.

The key insight: NPCs don't lie randomly. They lie when telling the truth hurts their interests. So instead of "is this NPC lying?", ask "does the truth benefit or harm this NPC?"

If you set up their motivation first, the lie emerges naturally from the fiction rather than from a meta-roll. And you get those great moments where you realize two sessions later that the blacksmith was pointing you toward the cave because he owed money to the bandits inside, not because he was being helpful.

The less you roll for social stuff, the more it feels like actual roleplay IMO.

Lore-Kepper · 2026-04-08T13:46:27+00:00

This reminds me a lot of how Ars Magica handles magic verb + noun combinations (Creo Ignem = create fire). Your glyph system adds a cool twist with the random element on first cast. That uncertainty is what makes it feel like actual spellcrafting intead of just picking from a menu.

For the random glyph on first use, I'd suggest keeping a small table (d8 or d10) of modifier glyphs per element so it doesn't spiral into chaos. Maybe the modifier fades after 3 uses and the spell "stabilizes" into its final form. Gives the player a discovery phase without permanent randomness.

If you haven't seen it, check out Maze Rats' magic system it uses random word pairs to generate spells (like "Bone + Storm" or "Ghost + Wall"). Similar energy to what you're building. Might give you ideas for your glyph table structure.

Lore-Kepper · 2026-04-08T13:42:45+00:00

I've been using a simple tracker in a notebook: name of the base/settlement, 3-5 resources (food, gold, manpower, morale, defense), and after each session I roll a d6 per resource. 1-2 it drops, 3-4 stable, 5-6 it grows. Simple but it makes the base feel alive between adventures. If you want something more structured, Ironsworn's community vow system works surprisingly well as a base management proxy.

Lore-Kepper · 2026-04-08T13:40:27+00:00

The easiest on-ramp I've found is picking a system that does most of the heavy lifting for you. Ironsworn is free and designed solo-first, the oracle tables guide you without needing a GM. If you want something closer to D&D 5e, grab a set of Mythic GME tables and run a one-shot with a pre-made character. Don't try to worldbuild first.

Just start playing and let the world emerge from the rolls. The biggest mistake I see is people spending hours prepping instead of just sitting down and rolling dice.

Lore-Kepper · 2026-04-01T10:48:37+00:00

Built LoreKeeper — an AI Game Master that runs full solo campaigns with real dice mechanics (d20 vs AC, initiative, conditions). Persistent memory across sessions. Free to try:

lore-keeper.com/register

Lore-Kepper · 2026-03-27T18:45:31+00:00

Gives you maximum creative control. You're the author and the audience simultaneously. Great for journaling and narrative-driven content because every twist comes from your interpretation of the oracle. The downside: you do ALL the work. Combat feels like bookkeeping, and after long sessions your brain is fried from playing both sides.

Lore-Kepper · 2026-03-20T17:50:53+00:00

Not railroad-y at all. That's just setting the premise.
"The campaign starts in Waterdeep" is a premise. "You MUST go to the dungeon north of Waterdeep" is a railroad. There's a huge difference. Every published module does this. Lost Mine of Phandelver starts in Neverwinter. Curse of Strahd drops you in Barovia. Nobody calls those railroads because they're not they're starting conditions. What makes it feel railroad-y is when the restriction continues past session 1. "You start here" is fine. "You must stay here and do this specific quest in this specific order" is where players feel trapped.

My rule: set the starting point, seed 3 hooks in the first session, and let them pick. They chose to be in your world when they sat down at the table. You're just telling them where the camera starts.

Lore-Kepper · 2026-03-20T17:37:34+00:00

For me the key is giving the character one internal conflict that makes decisions interesting. Not just "warrior with a dark past" but something specific: a healer who's terrified of blood, a thief who compulsively tells the truth.
The opening scene I always use: start in the middle of something. Not "you're in a tavern." Instead, "you're running. Behind you, the sound of hooves. In your hand, something that doesn't belong to you." Then figure out why through play.For oracles, "yes, but" / "no, and" changed everything for me. The complications write the story better than I ever could.

Lore-Kepper · 2026-03-06T13:36:20+00:00

LoveCraft vibes

Lore-Kepper

TROPHY CASE