Introducing Grimoire: A Solo Roleplaying Game

This is an old post that introduced the original idea for GRIMOIRE. You can find the released version of GRIMOIRE at itch here.

As discussed, I have been developing a solo roleplaying game that has the player take the role of a wizard. By the end of the game, the player will have several randomly generated spells in the form of a grimoire and a brief journal detailing the life of the wizard that created it. It is my hope that this will be an enjoyable way for game masters to create new spells or entire grimoires for their campaigns. I have tentatively settled on the name: Grimoire.

Figure 1. Thousand Year Old Vampire by Tim Hutchings and The Wretched by Chris Bissette: Two of my favourite solo RPGs.

During the development of Grimoire, I have been scouring the internet to find similar titles, adjacent subsystems, and more solo roleplaying games with the hopes to expand my palette. Today I found a gem, Sigils in the Dark by Kurt Potts, that does something similar to my fantasy spell generator I released a few days ago. There are several key differences, namely the manner in which the graphics representing the spell are created where mine has a penchant for more detail and variety. In spite of this, I have had a great deal of fun using Sigils and I recommend checking it out – though the journaling aspect of it is quite minimal.

This week I have also been exploring Thousand Year Old Vampire by Tim Hutchings and The Wretched by Chris Bissette. Wretched was a quick dip in to explore some more solo RPGs, however I have found that its clarity of the rules to be helpful and it is making me consider whether or not I should reduce the thematic of the layout and design of Grimoire, as seen in the spell generator, in place of something more minimal that allows for greater reader comprehension. Vampire is whole other beast. It is a phenomenal game with a great deal of replay-ability and it is a huge inspiration for Grimoire. The system of multi-level journal prompts leads to interesting side plots throughout the course of your vampire’s life. In Grimoire I am now working on 166 different journal prompts. This is not as much as in Vampire but is a significant number that should allow for suitable replay-ability of this game.

The first draft of the rules for Grimoire is almost complete. Once I have created most of these journal prompts then I can begin playtesting and tinkering. As it stands, the game functions like other journalling RPGs with a management of resources such as Coinage, Wounds, and Corruption – what is magic without a healthy dose of twisting manifestations of magic? As cards are drawn, they provide journal prompts while allowing the player to generate spells but the game will also drive players to undertake a variety of quests to change how spell generation works and to support the management of the aforementioned resources.

I hope to begin playtesting next week which means that I will hopefully be able to release a public playtesting draft for people to have a tinker with. After that, I will likely release it onto


Interested in reading more?

One-Page RPG: Collaborative Taskforces

Collaborative Taskforces is such a tacky and cumbersome title but that is the exact reason it is so fitting for my first attempt at a GMless one-page RPG. My day job has been throwing around some buzzwords of late and in spite of my shown cynicism in this one-page RPG, I believe it is leading to something good. However, I still found that I needed to vent some of my frustrations with “office talk” so I made an untested one-page RPG that makes a mockery of it!

Figure 1. I think I had a nightmare like this

In this game players will be “luckily” chosen to participate in a new initiative at their corporate office job. It has them involved in working with people from other departments while tackling tough problems on top of their regular duties and to top it off, the employees that do not perform will be fired at the end of the day.

I am sure this kind of work may be suited to some people but I do not find any joy in it. I believe you will find this reflected in the primary resolution mechanic which has players on a downward spiral unless they can risk the whole project or ensure that they are seen when they do something positive. Is it bleak? Yes. Am I cynical? Sometimes.

I also thought this might be a good opportunity to practice using some graphics and laying out the page. I think it worked out okay though it was something slapped together. I had one issue with a particular image becoming jagged around the edges after export. I tried everything except changing the image but no amount of messing with DPI or rasterising settings seemed to fix it. I think it may have been caused by me inadvertently changing the size of the image when it was grouped with some other layer. Whoops.

Anyway, I hope you find joy in this whether that is snickering as you read the wonderful job title generator or if you play it with your pals and laugh about being fired at the end of the day. Let me know what you think!

This link will take you to where you can preview the game and download it for free: Collaborative Taskforces Download

Interested in reading more?

Fantasy Spell Generation

Spells that are esoteric, wizards that are deranged and corrupted by magic, and mysterious magical symbolism are all features of some of my most enjoyed fantasy in roleplaying games. For this reason, I have been working on a solo RPG that, by the end, will have the player in possession of a grimoire of spells and a brief history of the wizard that created them. I think this could have great results when porting the grimoires into other fantasy games, however I have yet to finish designing the game. In the meantime, I wanted to show off the spell creation process as it currently stands. WARNING: Some of the spell offerings here depict violent or aggressive acts.

Figure 1. A spell randomly generated using the process I developed for a solo RPG I am also working on.

The above image demonstrates the type of spells that can be created using my process. The spells are referred to as Opus Phenomena Vicissitude because I thought it sounded neat and mystical. Each Opus Phenomena Vicissitude includes a spell name to provide just enough information as to what it might do, a requirement of the spell that must be offered to cast the spell, and finally the glyph which is mostly just for show in the grimoire. Imagine handing a scroll or a whole tome of these to a player! I know I would be excited to delve into it.

To create spells like the one depicted in figure 1 you can use the process described in the download at the bottom of this post. It should be noted that I have taken aspects of the design out that related to the solo RPG for your convenience of generating spells without becoming bogged down in other details. For this, you will need a set of playing cards with both Jokers removed, some paper, a pencil, and a mind for the dark arts.

I know elements of this process can be a tad vague but that is by design to allow flexibility in the interpretation of spell names and glyph-making. Hopefully, I can find the sweet spot before releasing the solo RPG. In the name of the RPG community, I hope you find this helpful and I would be happy to receive some feedback as I do know that these things can be difficult to describe to someone else who has not been working on it and some of those tables are large which can make them difficult to read.

This link will take you to Dropbox so you can download the document: Opus Phenomena Vicissitude

Interested in reading more?

Using Tanglegrams for Planning RPG Sessions

As I facilitate more roleplaying games, I find myself leaning more towards sandbox experiences with a large cast of NPCs. I establish a starting scenario to introduce these characters over the first few sessions without much of an idea of what the narrative is going to be. This is not to say that I do not plan any story – I often like to have something happening at the forefront in a session but it is determined by player and NPC actions instead of pulled from a plan. To do this I maintain session notes to remind myself of who interacted with who and how it went but this becomes painful when I need to trawl through notes from multiple sessions. Here is where I believe a tanglegram could benefit my and your campaigns.

A tanglegram is like a mindmap except it focuses on the interconnections between people and things. It was originally proposed by Ian Hodder in his 2012 book, Entangled: An Archaeology of the Relationships between Humans and Things, where he argues that humans live to sustain a material world. I believe this could be used to track the many NPCs, objects, factions, and PCs in a roleplaying game between sessions to aid with identifying story seeds and generating initial session situations.

Though untested, here is how I may approach this in future campaigns that I facilitate.

  1. Create a cast of characters (including PCs)
  2. Map the connections between the NPCs and PCs by using colour-coding or labelling to identifying the type of relationship and whether or not it is one-sided or not
  3. Add in various objects, locations, and factions of significance as independent entities
  4. Review the map and make necessary changes after each session and then use this in the planning process before the next session

Create a Cast of Characters

We all develop and create NPCs in a variety of manners and with varying degrees of depth. For the purposes of illustrating the use of Tanglegrams I am leaving each NPC at a single, brief sentence and only including a few.

  • Newt, an ancient witch preparing a blood ritual to revive her long dead sister and using Dr. Patella to gather bodies
  • Eye, Newt’s long dead sister who leaves the streets of Amberbrooke bloody
  • Residents of Amberbrooke who are working hard to establish a new life here
  • Meretah, a self-proclaimed detective who is often found nose-deep in a book or other people’s business
  • Chaypin Patella, a world-renowned doctor in the recent employ of Lord Amber
  • Rose, a local herbalist that tries to watch over Amberbrooke and its residents

Initial Mapping

To make use of these more easily then identifying the type of relationship between two entities is crucial but it is best to keep these brief. As you can see the relationships between each character is known and those who do not have knowledge of others is easily visible.

Figure 1. The initial map of the tanglegram demonstrating the relationships between various characters.

Adding in the Rest

In this step the locations, objects, and factions should be added in as separate entities with attached relationships. As you can see below, I colour-coded my blocks to distinguish between characters, objects, and locations. It may look something like this:

Figure 2. A tanglegram demonstrating the relationships between characters (yellow), locations (blue), and objects (purple).

Review and Planning

Over time these tanglegrams could become monstrously large but by displaying the relationship between all entities within a sandbox campaign it may be easier to identify story seeds or situations that players find themselves in. For example, the players may be out strolling at night and may see Chaypin Patella at the ruins or Meretah at the tavern. One evening the players may visit the doctor to find that Rose is banging angrily on his door and asking him to leave the healing to her. This could be left as a brief scene to introduce characters or it could blossom into something more.

An obvious limitation of this visualising method is that it represents a tangled web of relationships – I suppose that is the point. With the understanding that we do not require to understand or see every relationship at once, just those relevant, it becomes less of a problem. Some software could also reduce this problem by allowing a use to click on an entity and have the relationships to it highlighted or to select multiple and have the pathways between them highlighted. I do not know this exists, but it could support the use of tanglegrams well. In the end, this is nothing more than a tool to facilitate the generation of ideas and note-taking that I thought might be interesting to try out the next time I facilitate a game.

Interested in reading more?