January’s Game Project: Adventure Town!
Adventure Town is a roll-and-write game about running a town that adventurers pass through, a type of thing that I seem to find really fascinating.
Gunna level with you: I had a lot of writing to do this month. I work on it a little bit at a time, trying to find time to make pushes to finish it, especially since it seems to me to be a really easy project to just get finished, but tell you what: I haven’t had the time in January. This is life, and part of my life in January was a combination of helping someone move, a convention, and a lot of writing for the most important project of my life.
Adventure Town suffered. But it didn’t get nothing done. Particularly, what got done was a very important thing, in my mind: I stopped trying to make perfect mechanics, and managed to instead, get some good mechanics down.
Continue Reading →Prototype 22.12 — The Wrapup
Well, time to take a loss.
Continue Reading →Prototype 22.12 — The 2022 Prototypeapalooza
Just wait someone’s going to tell me ‘palooza’ is racist or something.
This year each month I dedicated some time – varying in scope and effort – to prototyping a new game. Of these games, two of them got to what I consider ‘made prototype’ stage, where I have a physical game that I can hold in my hand and share with people for proper playtesting. And that’s cool!
But I decided what I wanted to do this month, this December, was to look at the games I got, in what stages they are at, and determine what can I do with them in this last month to place orders for the rest in the hopes they’ll be available and my decks will be clear for next year to continue this process.
Presented then is a list of the games, based on the order I want to talk about them.
Continue Reading →Prototype 22.11 – DIY Touhou
Doing something different this time.
I am first up going to tell you what I wound up making and show you some examples of it. I’m going to explain where it’s at, and that’s all going to come before the fold. The full diary, which is a repost of material written over on my Cohost, is going to follow after. And we’re going to talk about sites like Cohost at some point in the next month or so, wew lord.

What I made this month is a prototype game design for a simple card game with a homogenous play form, focusing on hand management built on a classic mathematical puzzle you might see in the games Spot It and Dobble. The game has room to expand mechanically if it needs it, with each card having room for a rule or game mechanic to add to each character.
The game is composed of a deck of functionally similar cards; each card has a unique front and back. Each front face shows an alchemical summoning circle that describes a reading of a calamitous time, and a description of that in a set of keywords. The back face shows a magical girl from a mystical other realm (with art from the Touhou AI art bot) who represen two of those alchemical symbols and two of those key words.
The first turn of the game, you deal a number of these cards so their summoning circle faces are visible to the table, then deal each player a hand of magical girls, back-face-up. The deck is passed around from player to player, who get to do things to manage their hands, while they try and build a hand of cards that lets them ‘claim’ one of the quests as done.
That’s the game play experience, and cycle. I like that this needs no special components, and if it’s put in to a tuck box, it won’t need tons of setup. I also like that this prototype has room to develop: Each card could have a unique mechanical rule, a flavour or name joke, and the list of adjectives and alchemical symbols gives a lot of room for non-meaningful differentation.
Good idea, I like it, I did not get the time to order a prototype, but thanks to practice on Straight Outta Tucson, I have a tool available to me that can make turning this from ‘list of filenames’ to the actual cards very conveniently.
Dev diary follows!
Continue Reading →Prototype 22.10 — Camp Osum!
You know how I write these things ahead of time?
I’m writing this like twelve hours ago. Or twenty four? I’m not sure, I am tired.
Continue Reading →Prototype 22.09 — Lane Chase
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
What I started with this month was this:
This little Y unit that creates, in a player space, and in the process created lanes.
I didn’t get much time to work on this prototype this month. Honestly, I didn’t really get any time — this project hit a wall early on because this month had other demands. I’m embarrassed by it but I’m also just admitting it. This month has to marking crushes and a pressure point on the non-fun bits of the PhD (you know, all the paperwork that is meant to build off this design).
But still, this idea yielded some thoughts.
Continue Reading →Update: RA-Nime
Hey, remember this game idea?

What have we learned about this game in a few months?
Continue Reading →Prototype 22.08 — Switch Stances
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
This month I got to the outline stage of designing a trick-taking game which is now firmly at the ‘make a prototype and see how it plays in person.’ And it’s about skateboarders, and I have a challenge now about aesthetic choices.
Continue Reading →Prototype 22.07 — Corner Hustle
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
This month has been busy. Not in a fun way. Nonetheless, any work on an idea is work on the idea, so let’s talk about that.

Prototype 22.06 — They Were Roommates
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
They Were Roommates (temporary name, change this) is a game about getting all your bags in order and finding a solution – any solution – to getting a room where you can all spend the night for a con, even despite any inconveniences.
You ever go to a convention? A travel-from-your-home, get-a-hotel-room, spend-the-weekend, indulge-and-experience-and-relate kind of convention? In my experience, every con has sort of more or less the same kind of stuff, even if there’s an emphasis. You’ll find videogames at an anime con and anime at a gaming con, if you know where to look (usually near my table where I’m selling it). The general mish-mosh of interests mean that even at non-furry cons, there are some furries.
I started this month looking at some avatars for a game design that I kind of liked. After consideration though I jumped through some hoops and put that design onto a backburner (in part because I have some ideas for a different game using those pieces).
Image
Continue Reading →Prototype 22.05 — Monster Line
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
It says a lot about the design this month that I’m looking at my mocked up preview cards from late in the month and quietly being annoyed that it’s going to take me a while to get a test print of this game delivered to my house to play around with it.

Prototype 22.04 — House Advantage
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
In 2016, I made a game playable with a deck of playing cards, a single session tabletop roleplaying game that was designed to get everyone in the experience of being a DM. I made it and did the graphics myself – these four pictures of the four types of character, Hitters, Fitters, Grifters and Lifters.
I’ve wanted to make a game based on this for a while now, something small, something that plays with pieces I didn’t get to play with for a while. I wanted to make a game you could slip into a little bag, which came with some tokens and some cards, and let you play out the fantasy of The Suits in a different way. Rather than telling a story, though, the idea this time around was something tactical, something about robbing a casino.
And something about poker.
Continue Reading →Prototype 22.03 — Sky Islands
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
In January, I started late and didn’t get it done. In February, I had four game ideas. One of them became focal, and I spent some time this month actually making a physical prototype. My plan this month is to have something that at the end of the month can be treated as a thorough plan for not just a prototype, but a game that’s ready to go.

That proved very stressful, with the whole design write-up being week to week, and publishing just before the end of the month. Instead, I’m going to talk to you about what the idea is and focus on the core ideas, rather than on every step of the process.
Let me know if you prefer the week-to-week explanation or this style of simplified version.
Continue Reading →Prototype 22.02 — RA-Nime
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
What game did I try to make this month?
Continue Reading →Prototype 22.01 — Adventure Town
Halfway through this month, I sat down with my supervisor and we discussed the idea of what this year is going to look like for the PhD. One of the things that we discussed was that large projects were slow and hard to move, and the material I had access to was harder to access thanks to the global shipping crisis. Services like Gamecrafter and DriveThruCards were unreliable, sometimes simply refusing to ship to Australia at all. Anyway, point is that I’m trying to make a print-and-play game each month this year.
But I decided this with ten days left in the month.
Hrm.
I was not going to get this done. Not properly done, not done in a way I’d be happy with. But I do have a game where the core idea of it is something I’ve been turning over and over in my head for years now in the idea of making a print-and-play game for the year.
Therefore, here, I am just going to provide an honest accounting of what I did, this month, to work on Adventure Town and how close it is to being complete.
Every month of 2022, I am trying, as part of both my PhD project and my all-purpose general game development, develop if not a whole game for game development, a project start, such that I can make playtest prototypes. This is a sort of report of the process throughout the month.
Continue Reading →
Working on Black Jack’s Dungeon
If you follow my twitter, and like looking at me making things, you may remember seeing me work on a card game that looked a bit like this:
This game was called Black Jack’s Dungeon, and it was created and tested and then I made a proper prototype to test it out more extensively. When it comes to really large games, it can be hard to do playtesting and prototyping with just myself and my small group, because it’s harder to make the proxies work well. An engine that works okay when it’s shrunk down may feel really dull when it’s scaled up.
I made the prototype and found that there were some problems that the game was having when it was scaled up to full size.
- It was really slow! The original design relied on players flipping cards until they were satisfied and chose to stop, or overdid it, and ‘went bust.’ This is a bit like how Sector 86 works, but there wasn’t a solid way to handle needing to ‘dismiss’ enemies. Originally, players could choose to take monsters other players flipped, which gave it a cooperative element. This design is still something I can do, but it needs simpler enemies.
- It was really uninspiring! The heroes all had simple mechanical abilities, meaning that building a party was just a matter of what art you liked. Since there was one character who had a very special ability (turning into a cow when she was hurt), that made her stand out in a weird way alongside the others.
- The actual resolution mechanic for the whole game was just a matter of finding one card of many, and that was kinda boring!
- With lots of heroes, but you only getting three a game, it was kinda a bummer to never get to play with most of them, especially when a lot were really dull by comparison. The art was nice, I should make these things desireable.
- I used pixel art very sloppily. In a pixel art game, all art should use pixels of the same size (I am led to understand), and I didn’t. This made some of the art extremely unsettling to people who are inclined to notice this kind of thing.
I went back to the drawing board. Obviously, it’s not been a high priority, but it has been on my mind more as of late, what with you know, the thoughts about games that are playable without a large group of people. Particularly, this game struck me as an interesting option to make as a strictly solo, big-deck game.
(Huhuh, big deck).
My current idea is to design a game where cards are adventuring parties – that you will have one card, with one to five heroes on it, and they have goals and types of prizes they will keep for themselves, when you send them into dungeons. Dungeons will be decks, set up around your little town. To send adventurers into a dungeon, you shuffle their card in, then, in another phase, you flip cards from the top of that dungeon until that hero card pops out – then you sort through the revealed cards and see what that means. Sometimes those cards are just smashed by the heroes; sometimes, they rout the heroes and you have to help the heroes recover.
This is the new mechanism in my mind, where you’re the town sending out and supporting the adventurers. It also gives more room for complex party mechanics, without needing to make 20 cards for all the adventurers.
Reaper Space
don’t go there
it’s reaper space.
Everyone warns you when you move through the ports and bases and outposts. It’s the big zone where ships don’t travel; trade routes route around it; no corporate rig will travel into Reaper space at all. Not any of the big ones, at least, not one of the superheavies. Reaper space is uninsured space. Nobody’s dragging you back out of that.
You haven’t seen a Reaper, of course. Nobdoy has, or if they have, they don’t know it. Nobody’s that sure about the way the Reapers look, though there are a few of their artifacts. You’ve seen one – hanging once in the foyer of a citadel, dangled from the roof, this immense machine that looked like a tank, with an entire assortment of blades on the front and an enormous engine out the back, seemingly made to do nothing but plow forwards; the blades were attached to a wheel, which was itself screwthreaded – so each blade flicked and clacked and dug into the air when they ran the machine –
Which they did, for a little bit.
For demonstration purposes.
Watching it turn an entire shuttlecraft into pieces with all that sound, the shredding and breaking.
Brr.
It’s not like you need to worry about Reaper space. Reaper space has barely any planets in it, and there’s only one outpost out near the dead zone that serves as a border to Reaper space. Maybe a few planets, sure, probably with some cultures on them that are probably not spacefaring, or if they spacefare it’s to do minor, small trades – the trades of a culture that doesn’t have an empire or corp yet – and when the talk of reapers happens they just shut down their satellites and pretend nobody’s home.
There are pirates, of course.
After all, uninsured space is unpatrolled space.
Gotta be careful out there. It’s Reaper space, but it’s full of scum and villains too.
Hunter’s Dreams – Handling ‘Race,’ Part 2
This is more work on Hunter’s Dream, a 4th Edition D&D-compatible mod made to enable a Bloodborne style of game, where players take on the role of hunters, who have to first research their prey before going out to the tactical combat stage of things where players get to have cool fights with werewolves and whatnot.
Last time I outlined some of the problems with ‘race’ as she is treated in the game of Dungeons and Dragons 4th Edition, the challenges of making settings through the ‘race’ option, and the potential, unconnected legal concerns with how to treat races so as to not invalidate the rules of making 4th edition D&D content.
Those are our parameters, the problems we need to consider. Now let’s talk about what I’m going to choose to overcome this.

Hunter’s Dreams – Handling ‘Race,’ Part 1
This is more work on Hunter’s Dream, a 4th Edition D&D-compatible mod made to enable a Bloodborne style of game, where players take on the role of hunters, who have to first research their prey before going out to the tactical combat stage of things where players get to have cool fights with werewolves and whatnot.
This time, he said, in the tone of voice of a breathless white boy who has just completed his first college course on the topic, I want to talk to you about race.
Race in D&D is a fraught topic, so going ahead, we’re going to talk about some things that are racist, and we’re going to talk about trope space and fantasy novels, and how those things are going to be racist too. Just be braced. This is before we talk about the choices I’m making in Hunter’s Dream as much as it is about me thinking my way through the problem and whether or not it’s good to address it in this.

Hunter’s Dreams – Trick Weapons, Part 3
This is more work on Hunter’s Dream, a 4th Edition D&D-compatible mod made to enable a Bloodborne style of game, where players take on the role of hunters, who have to first research their prey before going out to the tactical combat stage of things where players get to have cool fights with werewolves and whatnot.
Last time, I discussed how 4th Edition D&D’s weapon system works, and today, I’m going to lay out some basic ideas of actual mechanics for use in Hunter’s Dream.

Hunter’s Dreams – Trick Weapons, Part 2
This is more work on Hunter’s Dream, a 4th Edition D&D-compatible mod made to enable a Bloodborne style of game, where players take on the role of hunters, who have to first research their prey before going out to the tactical combat stage of things where players get to have cool fights with werewolves and whatnot.

Last time, I discussed the basics of what a Trick Weapon does in Bloodborne, and today, I’m going to talk a bit about how 4th Edition D&D can handle some of those ideas.One of the reasons wanted to do this in 4th edition D&D is because the weapon system in 4e is really good compared to every other edition of D&D. Without delving into why and how other systems were bad (but they definitely were), let’s look at the things the weapon system in 4ed D&D has.
A 4th edition weapon has the following basic stats:
- a proficiency type (simple, military, exotic)
- a handedness (one-handed or two-handed)
- a range (melee or distance)
- a damage range (one or more dice representing the damage the weapon does)
- a proficiency bonus (determining any bonus to hit the weapon has)
- a weight (for encumbrance rules, which I’m no fan of, but this is our life)
- a group (to represent what other types of weapons it’s like)
- properties (one of a set of keywords that give the weapon specific abilities)
The weapon properties are as follows:
- Brutal
- Defensive
- Heavy Thrown
- High Crit
- Light Thrown
- Load Free
- Load Minor
- Off-Hand
- Reach
- Small
- Stout
- Versatile
Some of these keywords are very specifically utilitarian – a thrown dart would have Light Thrown, while a throwing axe has Heavy Thrown. A light thrown weapon uses your dexterity, a heavy thrown weapon uses your strength. Some of these, like Load Free and Load Minor relate to the unifying mechanics of the set they’re in (Crossbows and how you load new crossbow bolts).
The main thing about these keywords is that when you’re using the weapon, these keywords are very light on your cognitive load. Consider Defensive. A defensive weapon is as follows:
A defensive weapon grants you a +1 bonus to AC while you wield the defensive weapon in one hand and wield another melee weapon in your other hand…
Now, this has a few things that relate to it – it could be seen as kind of ‘choice intense’. You get an AC bonus with the specific condition presented here, but you need to pair a weapon with the defensive type, and you need another weapon, which must always be wielded in one hand. So hypothetically, any time you put this weapon down, your AC changes, and any time the weapon in your other hand changes, that also has a chance to change your AC. In a videogame with things like disarms or throwing weapons, this could be pretty complex.
In 4e though, a character is not likely to be disarmed; they are likely to configure how their character works, the way they approach combat, and once that decision has been made, this defensive weapon bonus just folds into the way the character works.
Brutal is my favourite. Brutal N means that when you roll a value of N or less on the damage dice, you can reroll it. This is a great mechanic because it can be a small nudge, statistically (a 1d12 weapon with brutal 1, for example, is an increase on average of .5 damage per attack) but it can feel really fantastic to cash in a 1 for even a 4. What’s more, some brutal weapons prevent feel-bad low rolls on ‘big’ weapons like the Executioner’s axe (Brutal 2), or intriguing, exciting experiences with weapons like the Mordenkrad (which rolls 2d6 – but both dice are Brutal 1).
There’s also the weapon group and proficiency type. Proficiency types push characters towards a certain general type of weapon based on their class’ background; rogues and fighters are likely to be familiar with most swords, for example, but clerics and druids aren’t. That means that you can gate access to things mechanically, which you can use to set the tone for some characters. Shamans and druids use clubs and staffs and spears, which aren’t that good as pure weapons, but it’s okay, because they’re not as likely to need them. If a player wants to reach out of their proficiency group, that’s fine too.
Finally, there’s the weapon groups – that is, the kinds of weapons these things are, what they’re like, and what they do. In older D&D editions, there was a trend towards trying to put a weapon in a big group (simple, martial, exotic) and that’s it; special training may refer to a specific weapon, but then you got weird things like how the Bladesinger would refer to a character using a longsword or rapier or elven rapier. Instead, in this case, weapons fit into general groups, and weapon styles or feats can refer to doing attacks with types of weapons. Most interestingly, weapons can have multiple groups – so if you build a character who can do things with polearms and things with axes, a weapon that is a polearm axe represents an intriguing opportunity to do both.
These are good properties because the mean that the experience of using these weapons is qualitatively different than in other systems. You set the weapon up, and then you use it – Notably, there are a lot of things these weapon properties don’t ask you to do.
- They don’t include a lot of memory issues
- They don’t ask you to commit within the action economy
- They can handle choices made during the attack, like versatile
- They don’t want to be too specific
There aren’t any weapons that have a unique property; none of these weapons have a unique mechanic. That means a weapon property wants to exist on at least two weapons. That’s good – that suggests any weapon property invented needs to be made with a mind to being reused. Anything too specific probably doesn’t want to belong here.
Next time, we’ll talk about how these two idea spaces interact.
Hunter’s Dreams – Trick Weapons, Part 1
I started work on Hunter’s Dream back in January, with the basic idea being a way to play a Bloodborne style game set using 4th Edition D&D. The reasons are pretty easy to grapple with – starting with ‘I like it’ and moving on to ‘Bloodborne’s play experience is a tactical game of resource expenditure, not a story game of improvisation.’
Still, 4th edition D&D is a game of systems, and that means when you want to put something in the systems, you want to put in some rules. In Bloodborne, the trick weapons are a big part of the tactical experience, and they make the game feel that particular steampunky way. How then, do we bring that feeling into 4th ed D&D.

When looking at implementing these trick weapons in 4E, we want to consider what they do and how they do it. That sounds like basic stuff, but those questions are going to illustrate the difference between the two types of games and how I can make something that feels right in a different game.
Trick weapons in Bloodborne are weapons; you use them to attack opponents, destroy objects, and occasionally interact with environments in surprising ways – think about the times you cut a rope or knock down a hanging treasure. Broadly speaking though, the trick weapons are weapons, which you use to hurt people.
When you use them, you can change them from one form to another. Now here is where we can get a bit McLuahnish, and point out that medium and messages intertwine. See, Bloodborne is a videogame, and you play it with a controller. That controller has a number of buttons, and you, as a player, are expected to track maybe about seven to eight of those buttons at a time in combat. That means any mechanic you introduce, if it’s going to happen in combat, needs a button, and it needs a reliable button, because this combat is pretty high stakes. The game design is also what I call ‘fixed animation’ length – that is, when you commit to an action, you’re often stuck with it, and unlikely to be able to assert control over it along the way.
Following that, then, is that the trick weapons need to be weapons where your ‘trick’ doesn’t take a lot of buttons or fine customising. If you do those things, it’d take more time, and that might make it too inconvenient. With only limited inputs, then, the Bloodborne trick weapons are very binary. They’re either ‘on’ or ‘off’ – and you can swap them between one thing or the other in-combat. There are a few oddballs, of course, but generally, these weapons exist in form A or B, and in combat, shifting from A to B or vice versa results in a special attack.
Most of these weapons change in ways that reflect the technology of the setting. For some, the change is a big physical object shift; for others it’s turning on a special ability for the next hit. The weapons can’t be ‘normal’ weapons, even if they mostly resemble them – swords that become hammers, axes that become polearms, that kind of thing.
These two states want to be qualitatively different, in the context of Bloodborne; you’ll sometimes get different damage types, different speeds of attack, and different reach. In this game, those are very small spaces. Attack speed can be fractions of a second; Reach can be important down to similarly small units of distance.
To summarise:
- Bloodborne trick weapons are weapons
- They’re primarily used to hurt people and interact with the environment
- The trick of Bloodborne trick weapons is simple to use
- This differentiates them from conventional weapons
- There’s still room for mastery
- These weapons vary in how they attack
- Reach
- Speed
- Damage
- Special effects
This is our outline, the parameters we want to consider. Next time we’ll look at the challenges of setting this up in 4ed D&D.
Project: You All Meet In An Inn
The Pitch: You’re playing a quest-giver at a local tavern, trying to make sure you hand your quests to the idiots most likely to succeed at it. You’re not the only one, though, and all the other players are vying to lure these adventurers on their particular quests, like a sort of ambulatory workboard. You need to pull together adventurers, earn coin to incentivise more parties, and hopefully get your own ends met by the end of the game.

Details
You get a bunch of cards known as Quest Cards. Those Quest cards have some flavour on them, and then a set of symbols indicating what they need to be completed, and maybe have marks on them indicating things they ban (like maybe the quest to seduce the necromancer bans all ‘holy’ characters).
Those quest symbols are also on the Adventurers cards. These cards indicate the kind of thing they can do, and have a card back indicating if that adventurer is amenable to questing alone, in a pair, or as a full party. They’re arranged in a grid of three rows, like so.

When you use a quest card, the adventurer (or adventurers) head out, and sit on that quest until … some timer. Not sure. Whatever. It’s a turn-based game. When they finish the quest, they return to the bottom of the deck they came from, and you get some fraction of the rewards and quest objectives. You can spend the reward money (hey, you think quest-givers are giving you everything your work earns them) to add to other quests, which means other adventurers are more likely to get them.
This whole game is modelled on Splendour; the grid arrangement, and the sort of economy of opportunities. There may be something like Splendour’s investments, too – maybe some of your quests make all your quests later easier because you have a reputation to uphold.
Needs
This game is going to need art. Since I now have a fund of sorts from Patreon I’ve been considering comissioning a bunch of adventurer art, of characters hanging around in an inn, but there’s an added challenge here: I don’t think I have it in me to design some 100+ characters, let alone give them enough to be meaningfully personable without using things like templates.
This has me considering maybe running a kickstarter with a cheap tier that’s just ‘we make your OC into a card and you get a nice high-quality copy of the art.’ I dunno.
At this point the volume of cards has me wondering if it needs to be a tight small-box 120 card game (as I make on Drivethrucards) or if this wants to graduate to be the next big thing as a small-box game that comes with tokens and markers.
If you think this sounds cool, if you think you’d want to chip in for art of your character, or if you’d back it on kickstarter, encourage me, dangit. I don’t know what I should be doing.
Project: Hunter’s Dreams
The Pitch: It’s a 4th Edition D&D Setting/Modbook which is about playing Bloodborne and Castlevania style gothic horror hunters. Combat is not about crawling through dungeons and parselling out careful resources, but instead about short tactical fights of 2-3 sequences of fights in a row, known as Hunts, usually with solo-class enemies rather than larger groups.

Between each hunt, the players invest effort into the thing that forms the core of their group, their Nexus, determined by the type of group they are. You can build your own keep or workshop, or network of connected hunters, depending on the type of game you choose to play.
The aim would be to keep the tactical, movement-based miniatures-driven combat of 4th Edition D&D, and giving you a sort of ‘boss rush’ way of playing. DMs don’t need to design larger dungeons, but rather just small connected places for the hunt to find their prey, and thanks to the hunters being hunters, these encounters naturally can take the shape of kill-boxes, or containment points.
Details
This would be a gamebook, first and foremost; a single book that’s designed to work with Dungeons & Dragons 4th Edition. Hypothetically, if your players are into other systems, it might be designed to handle that kind of cross-compatibility, but the basic point is to be a game system for a game I like. The game would then be made up of a series of modules that you snap together to make your campaign.
One module would be the rules for creating your Nexus. A Nexus sets some ground rules for the style of campaign you play in and also works against the ‘murderhobo’ problem that more free-moving campaigns have. A Nexus is something that roots you back to a space – things and people you can’t leave, and it’d have systems for checking on or recognising the nature of the location the Nexus is in. You’d decide at the start of the game if you want to control one of three options:
- A Keep. Your hunters are known and important, and they have to manage and marshall the resources of the town. They may rule the town, literally, and they go out and hunt to push back the boundaries of dark around the town. This is for your more basic ‘heroic fantasy’ feeling, and have a system for managing competing needs in the keep. Think of it as being an anti-dracula, or princesses defending their castle. People like princesses right.
- A Workshop. Your hunters are part of an organisation within a city, and they relate to the people who live and move in that city. They can be trusted or distrusted, liked or disliked, and the central establishment of the workshop means they can benefit from the connected resources of the city. Workshop games are more like your Bloodborne, where people might recognise that you are a hunter, not necessarily that that means they should respect you.
- A Secret. Your hunters don’t have any physical location that they centrally can meet at. They’re all people aware of a secret of the world, and that means in their city or town, they’re the ones who can understand what the monsters are here for. This is for your Buffyverse kind of hunters, though set in a more gothic horror setting. In this situation, inspecting the monsters and hunting them may be seen as foolish or dangerous. There may be no idea of ‘a hunter’ and part of the challenge of The Hunt is making sure you can gather your friends together in time.
One module would be about dealing with monsters and classifying them based on their grouping. Back in Ravenloft there was the mechanics of Fear, Horror and Madness, which kind of did a similar thing – in this case, the idea is that monsters represent types, and exposure to/interaction with a type can change how you react/treat them. This would be a space for ideas like beasthood or maybe insight from Bloodborne. If players want to contain the powers of the nightmares, this is where I’d put that kind of idea.
Another module would be for handling gear. The 4th ed weapon system is really good for things like transforming/trick weapons, or weapons that evolve naturally over time. Your Nexus might be able to replace a conventional gear system – with gear and abilities levelling up based on a budget/availability. One of the funny things with 4ed is that most gear was just meant to get replaced by level – you were never meant to plow your entire budget into a thing that you could hypothetically pay for, after all. Just making it so ‘downtime can be spent to upgrade gear’ seems an obvious way to streamline gear and reduce the quantity of knick-knacks that are a bit of a design problem.
Another module would be for ‘Races.’ Particularly, it might be useful to make a system for turning a lot of Races into Ancestries or Heritages, the idea that in this culture, what a Dwarf represents mechanically is just another type of human, and to put the races that are blatantly visually monstrous in a basket that let players play twisted, monstrous hunters. Imagine being a minotaur trying to hide in Yarnham.
Needs
Playtesting, for a start. It’s also a big project. Art for RPG books is always a thing. Fortunately, this is something I’m going to want to exist so I can run it, so that’s going to mean that even if it never gets made/polished and sold as a big project, this guide will still be useful as a reference point if I share development on this blog!
Project: Casino Worker Placement
The Pitch: It’s a wallet worker placement game, where you’re commanding a gang of The Suits inspired thieves hitting a casino, avoiding guards, and trying to have the best score at the end of the night, in a high contrast black-white-red style.
Details
First up, I wanted this game to use a small number of cards, some tokens and to fit entirely into a gamecrafter style bag. That meant trying to use a small number of cards to create a space. What I got was when I looked at cards like this, it wasn’t just nine rooms, it was also a series of hallways between them.
hey look maw, I’m vaporwave.
These are nine rooms, and players can move any amount, but there are guards that block hallways – and you can move them, too, with the right game action. That means that in addition to trying to put your thieves in some rooms, the guards also limit where you can be, but they also let you block your opponents’ movement or make it less convenient.
Each room has a value like a poker card, but also a type and a special rule. So there might be a room that pays out to everyone in it, or a room that pays out to the player who pays the least, or whatever. So it is a worker placement – you put in a worker, you get a thing. At the end of the game, though, your workers’ positions represents a poker hand and that determines your share of the final payout from the heist.
Needs
The biggest barrier to this is … well, stuff on gamecrafter is harder to sell at conventions. People tend not to buy my stuff on Gamecrafter, and this would want to be Gamecrafter for its tokens-and-cards style, as well as the small bag.
Think there’s a demand enough to continue on this idea?
Anatomy of Nsburg
Hey, remember me posting about my Craft-a-long project for Desert Bus 2018? I made a little card game about rearranging the inner city of the town of Nsburg, from the QWERPline podcast.
Now, I posted a bunch of this to twitter, as I was doing it, but twitter rolls past, and I wanted it to be both searchable, and I wanted to remind you this is a thing you can have. This is going to be (hopefully, as far as I know) available as a charity prize for donating to Desert Bus 2018. Here! Check it out! Get hype!
Here are some of the town cards of Nsburg so you can have a look, and a bit of a laff, and see how this game project went from Nothing to Something in as short an amount of time.







Ironically, this game was really hard to research, because Nsburg is definitively confusing. And of course, none of what this represents is canon – there’s no sign in the QWERP continuity that Lack Fixlakeindianname is its name. I still had a lot of fun doing this and sharing it with people and I hope you tune in to Desert Bus and we see how it goes!
Project: The Pipesman Conspiracy
Hey, this is kinda a cool one.
I’m working on this little game. It is, as far as I understand, never going to be for sale anywhere. It’s going to be available only as a charity option in Desert Bus. As I write this, I’m finishing up the first round of beta card faces.
The game is a secret goal, area control game about the city of Nsburg, the setting of Loading Ready Run’s QWRPline, and I’m making it so you can bid on it, and win it, for charity!
This is a really weird feeling? Like I wish I’d gotten into that space of making fan games, when people would think it was reasonable that I was making not-for-profit free games which built in spaces people liked already, like Star Wars amateur card games or the like, before I vaulted into making proper games, games with concerns like copyright and stuff, because I was selling them for money.
I mean I don’t regret it, but still. It’s nice to work with someone else’s concepts, someone else’s art. I really liked the way that the game came into being as I tried to express this idea of a slightly crap, but very funny conspiracy.
Anyway, with that in mind, here are some examples of card faces in production!
This game is almost a wallet game – the town of Nsburg can be made with as few as 16 cards, and the goals can be a few more cards on top of that, to make sure they’ve got some variety to them. You don’t want the game to be about the same end-goals every time, right?
The two goals are meant to represent two different options – one that’s kind of easy to do, if nobody is messing with you, and one that’s a lot harder to do, but much more specific. The idea is that you’re meant to be able to arrange the city of Nsburg based on your particular interpretation of the incredibly vague plan of the Pipesman.
Now, the game that remains might get stripped down a little bit and rethemed maybe a little bit to be a different game, but there is going to be at least one feature that definitely only exists in the special Nsburg version of the game.
Now, when this goes up, odds are good the game is on its way to Canada. We’ll see how this goes!
Project: Voiceless
The Pitch: It’s a hidden identity game where all the players are merfolk princesses, who have surrendered their voices to the Sea Witch. Except one of you is the Sea Witch, and in the midst of the group is a powerful charm that binds all your hexes. If it’s laid upon the Sea Witch, all the curses will be broken and everyone is free, and you each know a little about the women around you.
Except none of you can talk.
Details
Voiceless is made up of cards:
- Identity cards, of which you get dealt one at the start of the game
- The Hex card
The identity cards have an identical back. One of them represents the Sea Witch, and the remaining cards represent roles.
The most basic kind of role is just a mermaid princess. These win if the curse is broken. There’s also a Sea Witch, who wins if any of the princesses gets cursed.
Setup: Choose the princesses you want to include in each game. There should be some proportion of princesses to Sea Witch, and some princesses that complicate the game. Shuffle these princesses, deal one to each player face-down. Players can look at their card at the start of the game. Put the Hex card where everyone can reach it.
Play Loop: Players cannot talk throughout the play.
Starting with a first player, a player looks at another card on the table. They can then take the Hex card and either hand it to the next player (showing they are done), or hand it to another player face up. Players can then vote on whether or not they trust that with a thumbs-up or thumbs-down vote.
If the players all vote thumbs-up on one player, that player is Hexed, and the game ends. Cards are revealed and then players determine who won based on their role cards.
Needs
I mostly need art for this. The game at its core just needs a handful of pictures of mermaids, including at least one that can be The Sea Witch, so with a clearly different palette and style of the others. The aim would be to have the mermaids, as princesses, represent extremely different styles of personality, such as ‘mean girl’ or ‘innocent’ and I would want to make sure these mermaids didn’t represent just one vision of cool mermaidness. They wouldn’t need action shots or physical prowess or detailed weapons or whatever, just pictures of cool, Disney-Princess style mermaids.
Do you think you have the skills for this? Are you interested in the idea? Feel free to contact me, either via the Twitter DMs or by emailing me!
Project: All Of the Clams
The Pitch: It’s a small deck auction game with currency cards and a failure state. It’s a bunch of pirates or merfolk haggling over who gets what cool junk they found while trying to offload a cursed coin they’re all stuck with.
Details
All of the Clams is made up of two sets of cards:
- Treasure cards, that you bid for
- Currency cards, that you bid with
The Treasure cards are all stuff that matters to the players, so the framing device requires them to be people who want something, or have some reason to want things. I don’t want these things to have a grim tone so it probably can’t be something like post-apocalyptic medicine, or evidence for important criminal cases, so I vastly prefer for this to be motivated by greed or self-importance.
The Treasure cards come in three basic forms:
- Value cards. These just give you points for the end game.
- Negative Value cards. These take points from you for the end game, and you have to bid in reverse to avoid them.
- Box Cards. These cards come with other cards from the Treasure deck, and have some inherent value. Players can choose to leave the box closed or not, but opening the box makes the contents public.
The currency cards come in the following forms:
- 3 Coin cards
- 2 Coin cards
- 1 Coin cards
- Cursed Coin Cards
Setup: Players get identical sets of currency and it always includes 1 cursed coin. They have fewer 3-coin cards than 1-value cards. Probably a sort of 3-2-1 distribution, but make it so that it’s possible to overwhelm 3-value cards with 1-value cards (so 3:1 ratio). Then, remove a treasure card (or more) from the top of the deck, hidden.
Play Loop: Each round, the top card of the treasure deck is revealed. If it’s a box card, put the proper number of cards in that box. Then, players bid in a round on the treasure, not a value but a number of coins. Players can withdraw their bids and drop out of the bidding at any time, reclaiming all their coins. When all players are done putting cards into the centre, all the cards are flipped over, and the bids are compared.
The player who bid the highest value gets the item and the other players get their cards back. Note: Any player who revealed a cursed coin in this phase has to leave it revealed for any future bids. These coins are then taken from the player and lost.
If there’s a Negative value card, the same thing happens in reverse: Players coins in hope of not getting the coin. If one player withdraws or passes, they can keep their money, but have to take the Negative value card.
If one player has run out of coins, the other player can then claim a number of face-down treasures from the top of the deck equal to their remaining coins. These face-down treasures are worth only 1 scoring unit.
The winner of the game is:
- The player with the most victory points who has no cursed coin, or
- If all players have their cursed coins, the player with the most victory points
Needs
I mostly need art for this. There are three major concepts for the game at the moment – mermaids vying for human junk, pirates distributing treasure from a raid, or cyberpunks swapping chunks of code and virus-infected bitcoins.
Do you think you have the skills for this? Are you interested in the idea? Feel free to contact me, either via the Twitter DMs or by emailing me!
What’s Nyarr?
Hey, what have I been up to these past few days? Well, I was writing up the Nyarr.
What’s a Nyarr?
The Nyarr are going to be this June’s tabletop release. They’re not going to be a card game – they’re a new ancestry for your tabletop RPGs, released as my Lost Libram line of content. Lost Libram is my division of my work that’s from my older D&D work, stuff I never released because hey, 4ed came out and my friends are playing that now.
As a designer, I still love this old content, and realising there’s a market for it, I decided I wanted to get it out there. Especially since a lot of writing of this type isn’t mechanical, it’s conceptual, it’s giving flavour and tone for the stuff I’m sharing. RPG writing is in a lot of ways bits that you playtest.
Here’s an excerpt:
Nyarr are humanoids comparable in size to humans, ranging between 150 cm (5 feet) and 195 cm (6-½ feet) tall. Despite their size though they are markedly heavier than humans, ranging from 72 kg (160 lbs) to 118 kg (260 lbs). Nyarr have skin hues that range from a dark brown to a pale green, and some Nyarr are coloured blue or purple. Nyarr have soft plates of chitin on their skin on their shoulders and knees, and their feet are split into two large forks, rather than five small toes. In silhouette, Nyarr are most like humans, though with larger feet and hands.
Nyarr are most easily distinguished from humans by a number of secondary traits; Nyarr have scaled hands with pronounced, thick fingernails that look like claws, scaly plates on their shoulders, horns – typically two, though rarely four, – long, thin tails, sometimes splitting with feet that stretch up into a ‘high’ stance for running. A Nyarr running tends to lean forward a great deal. These traits have been called ‘demonic’ and ‘monstrous’ commonly, though their actual threat is quite minor; the scales protect their hands for fine manipulation in extreme environments, and the horns and tail allow them to steer while running more readily in areas like cliffsides or desert plains.
Nyarr gender differentiation is complex to explain, as Nyarr have at least three major genders. Their words for each gender are translated as generally ‘male’, ‘female’ and ‘onyar’. Physical differences between the genders are hard to determine; roughly half of Nyarr have a shape regarded by some students as ‘feminine’, but commonly-recognised indicators like hips and breasts are not common to the genders. While female Nyarr tend to have shapes other cultures regard as ‘feminine’, and male Nyarr tend to have shapes regarded as ‘masculine,’ these are not hard rules at all. Onyar Nyarr vary the most, with some onyar having prominently powerful arms and legs, with a more petite body trunk. Some Nyarr tribes even send out explorers to learn from other Nyarr other genders, trying to find the best ideas for their people to choose.
The Nyarr then, are a deliberately enby inclusive race of cool monster people for Dungeons and Dragons 3.5, who are powerfully social, deliberately cooperative, and inclined towards trying to make friends, even as they are careful about trusting the rest of the world for being hazardous to their culture at large. Visually they’re kind of like big-footed and big-handed Tieflings, and they have culturally, an idea of ‘choosing’ genders from their three major genders, with the understanding that some Nyarr choose other genders if they’ve heard of them.
One detail here, and which I’m putting out there to put on the record even if I fumble how I say it: I am recruiting non-cis artists and writers to contribute small bits to the text of this. My thinking on this is pretty simple: The Nyarr represent a way for a game player, someone who isn’t necessarily heavily connected to the world of nonbinary genders, to be introduced to them, and, as a creature in a game, it gives people a chance to play with, and come to understand that idea. If I’m going to put that kind of thing out there for people to include in their game, I’d want to make sure that people with experiences like the Nyarr interacting with other cultures, are able to put their mark on the work.
Complicating almost all relationships Nyarr have with other cultures is the expansionist trends of almost every non-Nyarr culture. Nyarr have a phrase that translates roughly as Be Wary Of Those People. In the past, Dwarves have hollowed out mountains that Nyarr considered home, collapsing the landscape underneath them. Humans have cleared forests they considered home and turned them to furniture and machinery. Elves have magically tamed jungles and ousted Nyarr from the trees they considered home, in the name of making them more like their own forests. Nyarr tend to view all these cultures as invasive.
Humans and dwarves are very much cultures that judge and compete, and view survival as a personal thing. Nyarr culture rejects these ideas, and sees survival as being a shared responsibility. Also the humourlessness and lack of fun in Dwarf culture is abhorrent to Nyarr outlooks – to survive without an ability to feel joy is to be as good as dead. Dwarves can sometimes appreciate Nyarr because of their survival abilities, while others see Nyarr and their culture of change and cooperation as weak and strange.
The cultures less prone to building empires and starting wars tend to cooperate with Nyarr better – particularly orcs, who rarely want territory that Nyarr alone can hold. Nyarr feel a kinship with the half-humans like the Half-Elf and Half-Orc, seeing them as something a bit like themselves; outsiders in a group.
It’s a little ostentatious, I guess, but I want to be careful about the ethics of it. I don’t want to stomp into gaming with Here Is A Trans Metaphor For You, As Expressed By Me, A Cis.
If you’re at all interested in this, if you’d like to give the Nyarr a read before their release, let me know. I don’t pretend to be an expert, and I can’t really afford a proper high-grade sensitivity reader, but if you’re curious, let me know.
Cities And Towns
Let’s talk about a game idea, and what I want to be sure I’m saying with it.
This game idea is known tenatively as cities and towns. It actually started as a colour matching/multiplier game, a math game for my nephews but I liked the metaphor of it being about things rather than stuff, and so it slowly took its shape as a town builder.
The notional mechanic is that there’s a common pool of cards, the city, that determine the value of the cards in each player’s personal pool, their town. At the start of the game, you deal each player a starting card that’s not worth anything, but gives you a place to start from, and put three cards into the city, to give people a standard view of how things are valued. This means that putting cards into the city can represent an explosion of value for you, but it’s something other players can piggyback on – if you have two of type A, and there are two more A in the city, you get four points, but any player who builds an A gets two, too.
I like this mechanic for representing things like trade dependencies and culture growth. A university on its own isn’t worth as much as a university surrounded by other smaller towns with universities, and a market thrives when there are other, connected markets. Players are simultaneously building the scoring mechanism for the game as they are building their own little spaces in the game.
Then came the time to make the game pieces, and I hit an interesting conundrum. See, one thing I could do is go with a pastoral, adventure-game vibe, you know, the not-necessarily-fantasy, but-probably of kingdoms with farms and quarries and woodcutters, as you see in games like Settlers or whatever.
The next option, however, is to build assets using something like these Kenney assets, isometric city representation.
Now this choice opens up an interesting question. I think that a modern urban city and smaller town thing presents an interesting set of different mechanics – after all, you have faster communication, and maybe there are some buildings that can’t go anywhere but in the city, and some things that can’t go anywhere but the town, because of infrastructural needs. Is there a need for variety the same way in buildings when they look modern, when they could show similar buildings on different blocks with ‘zoning’ rules?
But then we hit an additional question: What about redlining? What about the history of deprivation? If these are buildings that look like cities, but outside of cities and minus the skyscrapers, am I just building suburbs? And if I am, do I really want to present a scenario to players where they want to build more schools in the city, because it makes their schools out in the suburbs more desireable?
Now, I’ve made my decision – the game’s underway. But these are decisions you gotta be prepared to consider and confront. When you make a game, you are responsible for the things you choose to put into it, and the assumptions you make about what the game should have in it.