Solo TTRPG Notation
A downloadable game
Ever tried to capture the flow of solo RPG play without killing the momentum?
You're rolling dice, consulting oracles, tracking NPCs, and suddenly you're lost in messy notes. Free-form journaling gets cluttered. Pure prose loses the mechanics. Bullet points become impossible to parse later.
Solo TTRPG Notation offers a lightweight, flexible system that captures everything that matters without slowing you down. Whether you're playing Ironsworn, Thousand Year Old Vampire, or a homebrewed system with Mythic GME, this notation gives you:
- Five core symbols that mirror the natural flow of play: action, question, roll, result, consequence
- Optional layers for tracking NPCs, locations, progress clocks, and story threads
- Universal compatibility with any solo RPG system or oracle
- Format flexibility for both digital markdown files and analog notebooks
- Searchable tags that make finding that crucial detail from three sessions ago effortless
Start with just the basics, or layer in the full suite of tracking tools for complex campaigns. From minimal shorthand to rich narrative logs, the system scales to match your play style.
This is the shared language for solo play. Record what happens. Share your sessions. Pick up where you left off without missing a beat.
Modular. Searchable. System-agnostic. Your solo adventures, finally organized.
| Updated | 16 days ago |
| Published | 24 days ago |
| Status | Released |
| Category | Physical game |
| Rating | Rated 4.8 out of 5 stars (24 total ratings) |
| Author | Loreseed Workshop |
| Tags | Solo RPG, tools, Tabletop role-playing game |
Download
Development log
- Minor correction16 days ago

Comments
Log in with itch.io to leave a comment.
Hi,
thanks you so much for all the work you have clearly put into this. I have an issue in section 3.3 - Obsidian won't parse it correctly and I see an error:
Dataview (inline field '>'): Error: -- PARSING FAILED -------------------------------------------------- > 1 | > | ^ Expected one of the following: '(', 'null', boolean, date, duration, file link, list ('[1, 2, 3]'), negated field, number, object ('{ a: 1, b: 2 }'), string, variableIs this an issue with my Obsidian setup? Any idea?
Thanks in advance!
With Obsidian, the
>character is a quotation block. So, it seems your DataView query is not expecting that. Without knowing the query, it’s hard to tell.Hello! Maybe my answer is in the book but I’m struggling to find it. I’m trying out The Triple-O Player Emulator which requires players come up with three options before rolling for one. How would I go about annotating this?
I’d use notes right after the ? line and before the answer I can’t recommend anything more specific, I don’t have access to that specific oracle
This is really helpful in terms of what to journal and distill, and a great gift to the community. I've been using this for battletech alpha strike wargame battle reports, and using with a mobile markdown editor for on-the go RP scenes.
Edit: one technical issue is the use of > in my markdown editor at least generates a code block, so I have to keep escaping all the time e.g. \>
I usually embed the notation in a code block to prevent this!
I've been using your notation system since a couple of days for my campaign and I am loving it! Now journaling my game sessions feels more streamlined and more like i am playing the game.
Thank you! That’s what I was aiming for!
Awesome! I love the idea of solo journaling rpgs, but struggle with the journal part. I can't wait to give your method a go. Thanks for putting this together!
Thank you!
This looks great! My half-baked notation (if you can call it) I intuit into is similar but, as I said, half-baked so I found it tiresome at some point. Also I needed that bit of advice on keeping the flow.
I have started to write down combat and notable events at each session I have with friends, because it's hard to remember all epic moments, when we have problem with scheduling... I hope this notation will help.
I would change --- blocks to === or some other since at least in pandoc markdown --- is meant for YAML blocks.
Thanks for making this, it will be very useful. You are rapidly becoming my preferred solo games creator :)
I really love it, thank you so much!
To make it more practical for analog use, I printed and bound it. It turned out really well and will be a faithful companion for my gaming sessions.
Nice!
This is great and thanks for publishing it.
It does a good job of showing that solo play doesn't require an exhaustive journaling session. I know there are those who like it that way, but for others (like me) it can feel like a self-imposed homework assignment, and it can turn into an OCD slog when the point is to have fun. Your unified and simple notation system really works in that sense.
I also like that you can get a snapshot of numerous sessions with a quick look. With your examples, in just a couple seconds I could get a rich sense of what happened over minutes or even hours of play.
Nice work!
Thank you!
This looks really useful, thanks for sharing! I’ll try to adapt my set of templates on Obsidian to it.
I have some notes and questions:
Thanks for the detailed feedback! Really appreciate you taking the time to read through it carefully.
1. Links in the doc - I’m not quite sure I understand what you mean here. Could you clarify what kind of links you’re looking for and where? The doc is meant to be standalone and system-agnostic, so I want to make sure I understand the suggestion before considering it.
2.
+/-notation for tag changes - I like that! Using[N:Jonah|+captured]or[N:Jonah|-wounded]is definitely clearer than just[N:Jonah|captured]when you want to show incremental changes. That’s a nice extension of the notation—feel free to use it! As with everything in the system, if it makes your logs clearer, adopt it. The notation is flexible, so anyone can adapt it as they see fit.3. Mythic GME random events (doubles below Chaos Factor) - Are you asking how to record the random event when it triggers, or how to track whether it’s likely to trigger? Just want to make sure I understand before I give you a good answer!
If you mean recording the event itself, I’d use:
4. PC stats tracking - In my logs, I only track variable stats in tags (HP, ammo, status conditions). Static stuff like your Strength score or skill bonuses I keep in a separate character sheet.
That said, you can absolutely track everything if you want! Some people do
[PC:Alex|STR 16|DEX 14|HP 20|Gear:Sword,Shield]on first mention. It’s really about what serves your play—the notation is flexible and anyone can adapt it as they see fit to match their specific needs.Let me know if I can clarify anything else!
Thanks for taking the time to answer me, all you said makes perfectly sense and it’s indeed easy to customize the notation to your own needs.
By adding links I mean for example a link to this itch.io page.
This looks great for adventure games with oracles; I'm having trouble figuring out how it works with prompt-based journaling games like Wretched & Alone games or Carta games.
Great question! Prompt-based journaling games like Wretched & Alone and Carta work a bit differently, but the notation adapts well. I see two main approaches:
Option 1: Using the mechanics symbol
d:to note the prompt drawThis treats the prompt as a mechanical element that triggers the journaling:
Option 2: Using a custom symbol like
gen:ortab:For systems where the prompt IS the core mechanic:
For Carta-style games (map exploration):
Both approaches work! The first keeps everything within the existing notation, the second makes prompt draws visually distinct if your game is heavily prompt-driven.
The key is: use what serves your play. If you develop a format that works well for you, I’d love to see it. Prompt-based games are definitely an area where the community could help expand the examples!
Thanks! That helps a lot. :)
This is without a doubt one of the nerdiest things I've ever seen in my life and it's simply brilliant and I fully intend to spread the word about it.
This is an amazing utility, I say it's as revolutionary as programs that automate oracles like RanDM Solo and Tayruh's toolkit.
I’m flattered to be compared to such big names, so thanks!
Great toolbox! I've been doing the core notation using colored text (digital player) and it has always been a pain to format without losing track of my narrative. Will totally try to adopt your notation and spread the word!
Thank you!
will immediately start using this
Fantastic toolbox! It’s a great minimalist but powerful notation format that could even help keeping the log of a multiple player session.
A quick note, though, I’ve noticed that, I’m the “4.1.3 Events & Clocks” section, there are the Location examples from the block just above. Probably a copy-paste error, me guess.
Thank you! I’ll inspect the issue asap
Thank you for this! I just started an Ironsworn campaign for the first time in a couple years, and I'm using Iron Vault in Obsidian to run it, so having a markdown friendly system to adapt is awesome!
I like it. This is very much better than markdown, so I just chose my own fileextension and added some syntax highlighting in my text editor.
This is amazing! Thank you so much for adding some cohesion to our scattered approaches!
Looks very useful.
Love this!
This is great!
Very useful! Thanks for making this!