Back to Markbound

Comparison

Markbound vs ChatGPT for solo roleplaying

I built Markbound, so treat this accordingly — but a comparison that pretends a general chatbot is bad at solo RPGs would be useless to you and obviously false. ChatGPT is very good at some of this. Here is the actual line.

What ChatGPT is genuinely better at

  • Any system, any setting, right now. Markbound plays Ironsworn. If you want Blades in the Dark tonight, or a system you invented this afternoon, a general model is the correct tool.
  • Free-form improvisation outside the rules. Long conversations with an NPC, worldbuilding tangents, "what would the trade routes look like" — no engine needed.
  • Cost, if you already pay for it. You have the subscription. That's real.

Where it reliably breaks down

These aren't prompt problems. They're structural, and if you've run a long solo campaign in a chat window you have already hit all four.

  • The dice aren't dice. A language model asked to roll produces a number that fits the sentence it wanted to write. It will confirm it rolled fairly. It did not.
  • Continuity decays with length. Around the point where a campaign gets good, the earliest context is being crowded out. Dead NPCs come back. Vows get quietly dropped.
  • It doesn't know your sheet. Unless you re-paste it every turn, momentum, supply and conditions drift out of the fiction entirely.
  • It plays your character. The default behaviour of a helpful assistant is to move the story forward — including deciding what you do next.

Side by side

 General chatbotMarkbound
DiceGenerated as text by the modelRolled in code in your browser, crypto-grade randomness
Who decides outcomesThe modelThe dice. The narrator only describes what already happened
MemoryA context window that fills upA structured Codex of every named entity, persisted to a database
Character sheetWhatever you last pastedLive, applies its own consequences, always in the prompt
Canon controlNone — inventions become factSetting truths sealed before play; off-canon inventions are rejected
SystemsAll of them, looselyIronsworn, precisely
Your record of the campaignA chat logA journal with the dice log, exportable as Markdown or a bound PDF

The honest recommendation

If you want a flexible improv partner across many systems, use a general chatbot — and roll real dice yourself, keep the sheet in a text file, and re-paste your entity list every ten turns. That works. It's just work.

If you want to play Ironsworn specifically, over many sessions, and you want the dice to actually mean something without doing the bookkeeping, that's the thing Markbound was built to be. Two turns of it run on the front page with no account, and a full nine-turn session with every roll printed is on the sample saga page — including the misses.

And the free Ironsworn tools?

Iron Journal, Iron Fellowship, Pocketforge and Iron Vault are good, free, and made by people who care about this game. If what you need is a digital sheet, oracle tables and a dice roller, use them — genuinely. Markbound overlaps with them on those surfaces and its actual reason to exist is the narration layer sitting on top: a narrator that reads the dice and the Codex and cannot contradict either.

Try it without an account.

Two turns of real play — real dice, real sheet, no signup — run on the front page. Or read a full nine-turn session with every roll printed.