Design of Runehack: The Asterist

Ahoy! I have something I've wanted to tell you for a long time but kept it to myself for now. While making so many short games is nice and all, I do want to make a bigger game that could be fun to play for a longer time. I want it to be stimulating as a game, fulfilling narratively, but also different from what the market offers. Plenty of designers take the three pillars of D&D for granted like they are meant to be the foundation of every big TTRPG. Combat, exploration, and social interaction are fine, but I have some issues with them. Combat tends to be overrepresented and I'm tired of it. Exploration is okay in theory, but either undefined or unused in most cases I've partaken in. Social interaction is fine as is. So, I've been planning this project for quite a while, as some of you may know, and my first step was actually to figure out my own pillars of experience. In Runehack: The Asterist, I have explored one of these pillars... hacking.

I hope you'll enjoy reading this article, and I wish you all a wonderful day!

This artpiece was created by my wonderful girlfriend Arell with great care. Since one of my sources of inspiration for this project was the video game Transistor, I asked for something a little more surreal. I really like the glitch effects on the character, the lines that connect to the illustrated endpoints in the exact same way as the dice would in the game, and the big clock at the top with 23 spokes that represent the 23 hours during which the city is simulated every day.

In the Beginning, There Was a Line

The origin of my hacking minigame goes back to June 24, 2022. In the afternoon hours after a Friday lunch break, I've been talking to a pal of mine about one of my game design goals: if you want the story to focus on an activity, make it into a minigame. Combat in D&D is very much a minigame, and I'm pretty sure there have to be some minigames out there in games I haven't played as much too. I briefly mentioned how Watch Dogs has this hacking game I like a lot, pretty much a waterpipe-connecting puzzle, and how it does a couple of twists just to spruce things up now and then. Of course, not all hacks are done that way, it's just the really important ones when the game wants to emphasize the process.

But that got me thinking... wouldn't it be fun if this was doable on a board? After a few minutes of pondering this while the conversation continued, I had an idea. Placing the dice down, connecting them into lines using their pips. The dice pips are very underutilized, so much so that plenty of six-sided dice have replaced them with numbers. Eventually, this idea grew from just lines into branching trees. One cool thing I realized is that if the trails these dice make up were traced on paper, they would have no sharp angles, only 90° and 135° angle connections. Kind of like circuit boards. ... okay, those don't have a 90° angle, but it's close enough to remind me of those.

After working out the rules, I had to make up some basic patterns for the GMs to use, and abilities for the players to rely on. Fortunately, this minigame is rich with unexplored metaphors: firewalls, crossroads, pivots, endpoints, and so on and so forth. The turn structure for a player is simple - roll the die, use an ability if you want and can, and place a die on the board.

I'm extra proud of the fact that I came up with a way of explaining the basic rolls players would make to resolve simple things into hacks too. "Solo hacks", as I call them, are required when you would've succeeded on a task, were it 5 points higher than it currently is. What happens here is that you make a minor hack using only a single die, and on a success, the attribute increases temporarily by the necessary number. There are solo grids included in the rules, which are interconnected only by the corresponding die roll, or higher. For example, a solo hack grid for a difficulty of 3 succeeds only on the rolls of [3], [4], [5], and [6]. Yes, I've gone one step beyond and explained how the most basic rolls work, in case the players would like to hack those too. There's an optional rule for it.

Watch_Dogs 2 was rather influential for me, and it is still one of my favorite games. Even if these hacking puzzles are quite easy to grasp, they were enough to inspire me.

Immortals in the Ocean

The setting of Everling is one I had in my mind long before the game was written. Even before technologies anywhere close to ChatGPT have been invented in our world, we've been worried about the rise of Artificial Intelligence. I figured that a fictional world would too, which is why they'd want to test out its behavior in a secluded place, safely tucked away from the civilization. Then, I realized something important: these people are holograms. The entire city can be a hologram. And an image can be hovering anywhere if it's done just using the runes. Even... at the bottom of the ocean.

All this being said, though, the toughest part to figure out was the question of worldbuilding. Being a member of an immortal, theoretically post-scarcity society is fine, ... but how does one turn that into a game? What drives these people, what do they do on a daily basis? How do they identify each other and communicate? And is there anything that could have a price in their eyes? These questions took me literally months to answer, long before I even conceived of the hacking minigame in June. I got answers to these questions eventually, most of which you could find in Everling's article, which is why I'll move on from this point and come back to describing how it affected the game.

Originally, I wanted the players to keep track of their simulation time in the form of "hyres", a modernized version of the term for an hour they'd use as slang. However, while writing the game, I came to realize that that sounds rather intimidating. So, instead of doing that, I decided to group them into six time blocks. I still don't know if it's a good design decision, but it's a bit of an experiment on my side.

Of course, being a simulated mind with a hologram body comes with a lot of other aspects, which I felt the need to outline in the rules in the Ghost's Baseline Traits section. I wonder if this won't be too much for a player to get into, keeping in mind all the things I listed there.

The attributes were a tough cookie to work out because there are so many things a ghost could build themselves for. Ultimately, I decided to go with 11 attributes sorted into three groups: Corporeal (relating to how much influence they have in the world, such as telekinesis-powered strength), Phenomenal (relating to how they are perceived by others), and Intelligence (describing how fast they can retrieve information from the Mistweb). One extra attribute technically exists, but it's just for the unspent points. A player could change their loadout of attributes during any maintenance, giving them a lot of flexibility in expressing themselves. Furthermore, I've provided in the document a table that describes what each of the attribute values stands for numerically.

Finally, there's Corruption and memories, some of my favorite aspects of the game. During the maintenance, a corrupted ghost gets fixed to an extent or backed up if they were completely uncorrupted. You can't hurt a digital ghost, but you could try to corrupt their code. And the more corrupted they are, the higher the chance their simulation gets terminated. If you remember how annoying it is to lose that one document you've worked on for hours without saving it, you can imagine what happens when a ghost gets terminated. They are restored from their last backed-up state, forgetting everything that happened since then. Of course, there's also a way of "killing" a ghost, which is in actuality just hard-locking it by getting the city's servers to back it up while it is terminated. As for how that's done, let me just hint that that has to do with the following paragraph.

Hack the World

I don't say this lightly, but this might be the greatest game design idea I've had in my life. Hack the World is a mechanic available to all player characters in Runehack: The Asterist. To put it briefly, they can temporarily rewrite the rules of the game itself for you, increasing or decreasing some number in the game... by 1. It's usable once per Cycle (term for a day in Everling), after which the effects cease. I honestly can't think of a better setting for this mechanic, a city that's completely simulated and hacked from the inside is perfect. Of course, the rules had to be written around the fact that this can be done, but it wasn't as difficult as I thought. (Though this might be proven otherwise once players actually get their hands on it.)

Honestly, I feel like I could keep going on and on forever, but I've said everything about the game that's important, and then some. I'm just happy it's finally out, and I look forward to testing the rules out, and connecting them to the bigger project I've had on my mind for literal years.

Thank you for reading, and have a nice day!