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.
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.
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:
I’d suggest to add some links for people that want to know better or follow for further versions in the docs themselves, as after reading it I almost forgot where I saw it (reddit), and wanted to see how people are taking it
In section 4.1.1 if you want to update NPCs tags (or tags in generals) when you want to to just show the changes it might be less ambiguous to add `+` or `-` {status}, e.g. `[N:Jonah|+captured]` or `[N:Jonah|-wounded]`
How would you track random events in Mythic GME when you ask a fate question and you roll double digits lower than Chaos Factor?
When tracking PCs with tags, are you specifying only variable stats like HP or are you tracking all the stats the first time you mention them?
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:
? Is the merchant trustworthy?
d: Fate chart d100=33 (Chaos 5) => Yes
(note: rolled doubles below CF - random event!)
gen: Mythic Event d100=45,78 => NPC Action / Betray
=> The merchant nods yes, but I notice him signal to someone in the back.
[N:Merchant|duplicitous]
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.
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 draw
This treats the prompt as a mechanical element that triggers the journaling:
S1 *Day 3, supplies running low*
d: Draw card: 7♠ - "A sound in the distance"
=> I hear scraping metal beyond the walls.
My hands shake as I write this.
The sound is getting closer.
d: Tower token check => FAIL (6 tokens placed)
[Tower:Stability 6/10]
Option 2: Using a custom symbol like gen: or tab:
For systems where the prompt IS the core mechanic:
S1 *Day 3, supplies running low*
tab: 7♠ - "A sound in the distance"
=> I hear scraping metal beyond the walls.
My hands shake as I write this.
The sound is getting closer.
d: Tower check => FAIL (6 tokens placed)
[Tower:Stability 6/10]
For Carta-style games (map exploration):
S1 *Entering the ruins*
tab: 3♦ - Forest tile - "Ancient stones"
[L:Stone Circle|mysterious|overgrown]
=> I discover a clearing with weathered standing stones.
Moss covers strange symbols I cannot read.
? Are there signs of recent visitors?
-> Yes, but... (low roll)
=> Fresh flowers at the base, but whoever left them is long gone.
[Thread:Mysterious Visitor|Open]
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!
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!
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 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!
← Return to game
Comments
Log in with itch.io to leave a comment.
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!