Sixty Years In Space: Devlog 2

When I started writing Sixty Years in Space, there weren't as far as I was aware any TTRPG adaptations of board games. Dungeons and Dragons itself was an adaptation of a miniatures game, and that tradition had kept going, and a collectible card game had a an adaptation, but the overwhelming flow of adaptations was in the other direction. Board games, especially in the modern renaissance of board games, were prolifically adapting everything they could, either directly or inspired by. And video games in turn have begun borrowing ideas from board games and rapidly iterating on them, taking advantage of the fact that while a board game rarely gets more than 10 plays at the table, a board game-inspired video game might be able to get 10 plays an hour.

Board games have a number of cool ideas that could easily be adapted into TTRPGs. As someone pointed out on Twitter, board games have much, much cooler character sheets. Indie board game fans are are more comfortable with the idea of paying for things than indie TTRPG fans. I would argue that boardgames do a lot more work with a lot simpler maps and rules (although you are free to disagree). And board games sometimes do something else, which I'm going to term diegetic play.

Something strange occurred as I was writing Sixty Years In: I began to notice that reading the rules was part of playing the game.

For a start, that's a great excuse for allowing me to get away with making more rules. If reading the rules is part of playing the game, then more rules equals more game play. But I already had a great excuse: as long as nothing I wrote was as complicated as rocket movement in the High Frontier board game, I could get away with as writing as much as I wanted (and let's not start with the sins that the phrase living rules enables). So something else was up.

Monopoly is a much bullied game in the board game community in a way that ignores its popularity. Most of the Monopoly rules are terrible. But when you go to the bank in monopoly, you get handed money which is counted out by the banker, just like people of a certain age used to do in real life. And that's what I mean by diegetic play: the thing you do in the game mimics as closely as practical the thing you do in reality.

Reading the rules in Sixty Years In with a group of friends and figuring them out is as close to the experience of sitting in NASA mission control, with the spacecraft design and operating manuals out, trying to figure out a technical solution to an unexpected situation as I can make it. And that's not the only place I was able to introduce diegetic play. Creating a map can become diegetic play, if I make the process of creating the map follow the same order of operations as surveying a planet or star would follow in the real world. Running an exfiltration, while you watch from afar as red and blue teams move throughout a map, can become diegetic play. Calculating fuel allowances is diegetic play -- but building rockets in the board game is diegetic play but not in the TTRPG, so I've not been able to do this everywhere.

You might argue that even venerable Dungeons & Dragons has diegetic play every time you have a conversation with an NPC. But there's an inherent tension in every role-played conversation in every TTRPG: it is reliant on player-performance instead of character-performance. And moving figurines around the map is diegetic only in the miniatures forebears of D&D, mimicking the battle map a general might move their troops around during a combat operation. Except. Except if you recast yourself as a co-director of a fantasy movie, moving figurines around a map is just what you'd do with the stunt and special FX teams while you were planning out an action scene. And that's where D&D gets the closest to indie TTRPGs: the combat map is a collaboration between players and DM in much the same way that collaborative play is designed for and encouraged in many of these games.

Sixty Years In Space: Devlog 1

Sixty Years In Space is available now at https://half-apress.itch.io/60-years-in-space

 
Sixty Years In first came into being as a Google doc, then a collection of Google docs, early 2015. I had been working in my spare time (I didn't need much sleep) on the High Frontier 3rd editon - I am the uncredited developer of the edition of High Frontier Interstellar that was packed in as a stretch goal for that release and provided cheerleading, goading and playtesting on the 3rd edition proper.

Very quickly I recognized that this was a unique opportunity to develop a game unlike any other that I had played: by making it a table top roleplaying game I could give it unlimited scope (up to a billion years it turns out), by steering into the idea of the player characters being responsible for colonizing the solar system I could give them the ability to shape what the future looked like - the trade-off that the bump mechanic provides between personal gain and making sure the future is safe for everyone else was added very early on - and by making it act much like the board game I could get rid of the need for a GM which meant I could play it as well.

My background in roguelike game development meant I was comfortable with procedural generation mechanics, and thus the rough shape of the game formed. Player characters (crew) would be sent on randomly generated missions, encounter randomly generated spacecraft and visit randomly generated locations on fixed planets on the High Frontier map initially, but randomly generated elsewhere in the universe. And it would happen at High Frontier scales, which meant years would pass quickly - perhaps a decade in a play session. I had tried this previously in a much smaller game (Wisp) that was unfortunately lost due to a laptop hard drive failure, and much of A Lot of Zeroes is a spiritual successor to that game.

The next 8 years have been filled with figuring out what that exactly looks like and how much I had to create to fulfill those requirements. And how to make it fun.

Making the game GM-less immediately created a whole lot of challenges. The biggest one is the amount of bookkeeping required. Without a GM, I couldn't rely on any authorative game state being preserved implicitly in the game master's memory. So everything has to either appear on the map or be written down. I struggled for a long time trying to work through the implications of that and ended up abandoning almost all attempts at turning that process into systems. There was at one point a whole set of mechanics for creating characters who had secrets hidden from each other, that could be revealed during the game. Players didn't just have crew positions, but also have separate roles which determined what parts of the game they book kept. These ideas may return: there is absolutely a good game to be made where each player is a crew member on a space ship who is controls part of the game (navigation, comms, etc). This is not that game although it wants to be.

The second set of challenges arose from the fact space is an incredibly hostile and unforgiving and worst of all, unintuitive place. To reflect this, I needed to both create systems that reflected this, but also understand myself what that meant. I did mathematics in university, but not physics ever and was at times during development literally doing rocket science. There's an incredibly messy Google spreadsheet with maybe a hundred tabs of doodling and calculations where I hopefully haven't made too many gross mistakes. A few very helpful space people helped me out: I absolutely need to shout them out, but, much like maintaining a bibliography, I didn't have the discipline to note who they all were. You'll just have to trust me when I say all of this game is based on research.

My love of science fiction drove a lot of this: but I've tried to avoid direct homage too much. I removed an entire supplements worth of random faction mission tables from All Errors are my Own when it became obvious the amount of work and page space required to have one table per faction (I'd already done half) and the fact I was worried I might be sued for lifting plots from every science fiction work I'd ever read. What also drove my was my absolute annoyance at some beloved sci-fi game properties. The entire Weapons chapter is fueled by my annoyance at the generic-ass-we-gotta-have-a-heavy-pistol Eclipse Phase weapons table. No Mans Sky has a great sound track but is also extremely instructive on where planetary procedural generation works (pretty colours and crossing hazardous terrain on foot) and what doesn't (almost everything else they tried).

To create as much as I did requires some cheating, so apologies for this in advance. I absolutely created hundreds of faction doctrines by Googling "theories of X" and then creating a doctrine for each theory - and then never taking the time to hide the evidence. There are so many random tables because random tables have blank entries, and blank entries force you to come up with ideas, and then even if those ideas are bad, you can come back later and fill them in with a better idea. Hopefully I did that everywhere. Some of those random tables have levels of precision required to precisely match stellar frequency or demographics, and some of those tables I've basically pretended that 2D6 has the same probability distribution as 1d12. And speaking of demographics, two of the most egregious outcomes of the whole development is the lose of diacratic marks from the demographics table in the core rules, and deciding to use consciouness as the measure of how advanced a civilization is on the development path. Or maybe its using Alzheimer's and cancer as game mechanics (they're from the source material!). Or maybe its alphabeticizing some tables and not others. Or the use of capitalization.

But the biggest cheat was that I had to make the process of creating the game fun. That absolutely breaks Sid Meier's fifth rule of game design "5. Make sure the player is having fun, not the designer/computer." This game wouldn't exist if I hadn't had fun making it. And will you have fun playing it?

One morning at about 5 am after having spent a largely sleepless night planning a turn for a play by forum game of High Frontier 2nd edition, I made a move where my rocket got to the Saturn heliocentric zone. I can still feel it to this day: my stomach dropping away from me like I was on a roller coaster as I'd finally, after months of playing a cut throat and unforgiving game, I'd moved a plastic counter on a cardboard map farther than I had ever moved it before.

That's a strange kind of fun. But I want you to experience something like it. And that's why I've made this game

Hell Let Loose: Winning as Commander

I'm going to teach you how to win as commander in Hell Let Loose - at least at beginning and intermediate levels. This is for purely selfish reasons: I have a much better experience at Hell Let Loose if the commander doesn't loose the game, and too many of my recent game experiences have been because the commander loses the game.

Let's start by inverting the command chain. The fantasy of being in charge of 49 other people is just that, a fantasy. As a commander you are not here to command: you are here to be a servant for the other 49 players in order to ensure that they are having a good time. To do that you have to understand human behaviour, because your chain of command is fundamentally about getting the team to behave the way you want them to. A key part of this is understanding loss aversion: people are prefer to avoid losses then making equivalent gains, even when the final outcome is equivalent. To translate this: the team will have a much better time if they hold a point, rather than if they lose it then regain it over the same period, even though the net outcome is the same. And by holding a point, we avoid the risk of losing the game.

Your primary responsibility as a commander is to never lose a point.  Everything else much become subordinate to that. If you never lose a point, your team will have a stable platform from which they can launch attacks, feints, go off on adventures and find stories to tell. At worst, you will lose warfare maps 2-3 (but only against other players who've read this guide), win offensive maps when you're defending 4-1 (given the first point can often fall before the team gets there), and offensive maps when you're attacking... well, let's get there after covering off the basics.

Mechanically, how can you lose a point? Again, there is a very simple reason: your team is not on the point defending it. So all your actions must be considered in the light of "will this ensure my team will get to the point and defend it?", and anything that does not must be discarded.

At this point, some players reading this might start to object and point out how important the commander is for attacking. This is entirely nonsense. The commander does not need to do anything for the team to attack. The team will naturally attack. They have all the tools they need. A support class and either an officer or recon can put up offensive garrisons in blue territory. A well organised squad or pair of squads can do the same in red territories, given at most 40 seconds of swapping players between support to do so. An officer or spotter in a supply truck can do that anywhere that there's no armour on the field. If the squads don't choose to do so, that is not your problem as the commander; it is their problem as one of the other 49 other people in the game. If they can't kill the other team effectively when they're attacking, it's their problem, not yours.

Luckily for us the game is balanced so it is much easier to defend than attack, that smart players will realise that you're giving them every opportunity to maximise their kills and win that 50% experience bonus.

So as we're agreed that defense is the only thing we need to consider, let's look at the commander powers in light of this, starting with the manpower abilities.

Airheads

There is no faster way to lose your point then put up an airhead in exactly the right spot to attack the enemy team.

This may sound paradoxical, but hear me out. An airhead that gets up and stays up long enough to be useful attacking an enemy point will immediately divert the majority of your team from defense to attack. One of two things will happen: either you'll cap, because the other team is unprepared, or you'll be met with an equal or greater number of defenders. Your team attacking off the airhead will get their outposts up, and if you're lucky a garrison, and if you're incredibly lucky the garrison won't stay locked. But the stars have to align right for you to do this (and we'll talk about how to get the stars aligned right when talking about bombing runs) but in every instance, your airhead will stop before you've finished capturing the point.

At this point, you are in an incredibly precarious position. Your garrison and outposts are surrounded by enemy spawn points, a whole lot of your team is stranded in enemy territory and the other team is doing the right thing (staying on the point defending) and you're doing the wrong thing (not staying on the point defending). This is where I bring up the third principle of being a commander: you will win if your team is better then the other team, regardless of what you do. If your team is better, you can cap off an offensive airhead. But if your team is better, you're going to win anyway. Using the methods outlined here, you'll get your team joking "HLL speed run", a message I got while commanding a team last night using these techniques - even though I had lost voice comms for almost the entire match! That, by the way, is the secret to winning an offensive map when you're attacking, that I alluded to earlier: just have a better team than the opposition. It's simple really. Being the attacking side on offence is a test of the entire team, not just the commander, and I suspect where a lot more interesting high level commander tactics are actually useful. You'll see players haranguing you about these: "place the airhead here", "bombing run please", "drop supplies on me". Ignore them, unless you're the attacker on an offensive map. Then, and only then, start to consider the wisdom of the crowd and traditional techniques.

There's only one circumstance that you can reliably expect the other team to be unprepared, and that's after you've just captured a point. You may be tempted in these circumstances to drop an offensive airhead to get a double-cap. Ignore it. You're going to be setting up double-caps using an entirely different technique that will get you triple-caps, without any of the risk of manpower. And if the airhead stays up, you're in an even worse position than a traditional airhead, because now you've spread your team out across three points: the airhead, the point you've just captured, and the point you were defending.

Instead, use the air-head to reinforce a point you're just about to capture or that you've just captured. Drop it on or as close to the point, ideally behind some friendlies, with an unobstructed path to the point. The timing of the airhead is important: I required at least half of the capture bar to be filled, but usually as commander I'm busy doing something more important and end up saying something stupid sounding like "oh **** we're capping" and that's my cue to drop the air-head.

Get everyone to redeploy onto either the airhead you've dropped or the garrison someone is placing. People will ignore you, then come in on the second wave. That's ok.

Reinforce

Reinforce should be used whenever the capture bar starts to turn red on the point you are defending. Don't wait for it to get one third red, or in fact any appreciable distance into the red bar. Do it immediately. You're already in a position where the enemy has got too close to the point, because, as should be obvious, it means that all the enemy are close enough to the point, because, as stated before, all your team should be on the point defending. Reinforce is a force multiplier, so the best time to use it is when you have lots of defenders on the point.

Always keep enough manpower to use reinforce, but be prepared to sacrifice it immediately to use your airhead as described above.

Encouraged

Use encouraged whenever you get above around 700 manpower. You'll get to do this often, because you're not wasting airheads or reinforces. You'll end up with 2000 or more fuel as a result, but that's ok. Don't use it if you don't have nodes.

Supply Drop

Fourth rule of commander: Do not drop supplies anywhere in front of the point you are defending. This includes in the blue territory. In fact almost all of the supplies you should be dropping should be on the point you're currently defending. Supplies are a giant flashing sign in the sky of where your garrisons, infantry and recon squads are. They give away vital intelligence and are honey for enemy recon squads, recon tanks and bombing runs. Instead use them to encourage your engineers to build defences and to ensure your squaddies can immediately build another garrison if you ever lose the garrison on point.

We may as well discuss garrison placement now. This is your primary minute by minute job as commander: to ensure you have defensive garrisons. You'll do this by running up supplies using a supply truck, turning around, going back and getting more supplies. Make sure that you build the garrison as far away from where you dropped the supplies as you are able to, to make the supplies harder to find. But also be careful not to put the supplies within 50m of a zoomed out map grid line because a) it makes the locations more predictable because it is easier to measure in map grids and b) someone might build a garrison in the red territory (even if that territory is blue now).

A lot of commanders will argue that you should triangulate your garrisons around the point you're defending so that you don't have a garrison on point. The argument boils down to it's not fun spawning on a garrison which the enemy is bombing or spawn camping; and they're going to be spawn camping the point they're attacking. But the enemy is going to be focused on garrisons anyway, and triangulated garrisons gives them three opportunities to spawn camp instead of one.

I instead prefer to have a garrison on point, because I have the supplies on point and I have engineers building barricades to block incoming fire on point. I then have a defensive half-moon of garrisons around the rear of the point around 300 meters out (one and a half grid squares). I pick 300 meters, because I want the enemy to build their offensive garrisons within this ring, and I want to slow down enemy recon squads and tanks getting from garrison to garrison. I've seen a recon tank take out 3 triangulated garrisons and a half-track in less than two minutes around an undefended point at rear.

I want the enemy to build their offensive garrisons within my garrison ring so we can always flank and take them out, and because of rule number two: I want my team defending the point, not wandering off it. 300m is too far away to be convenient to spawn at another garrison and run back to point. I want them on the point.

There is one other exception to supply drops, for warfare maps only, and only when you're 2-3 or 4-1 down. If you have plenty of supplies on point, you should drop a supply drop or two deep into enemy territory: half-way between cap 4 and 5 if you are defending the second point, or between cap 3 and 4 if things have gone really bad and you're defending the last point. The function of these supply drops is to enable a triple-cap. This works as follows: you cap a point, reinforcing it using your airhead as you normally would. Your friendly recon squad immediately builds an offensive garrison in enemy territory using the supplies you dropped. From there you cap the next point (double-cap) by moving back from that garrison and the point after that (triple-cap) immediately afterwards.

It is really important that these deep supply drops aren't anywhere that can be used to build a garrison before you make the next cap. Doing so will enable your team to wander off the point you are currently defending, diluting your defense.

Recon

Since you never need to recon the next point, because you don't want to encourage attacking it, this frees up reconnaissance flights for their primary function: hunting tanks. Ensure that your officers mark up all the tanks locations to assist your tank and anti-tank gun crews.

Strafing Run

Use your strafing runs to kill the recon squads taking your defensive garrisons out. Zoom in and make sure you aim carefully, as soon as you notice the garrison is locked (completely red). Sometime it'll be an enemy vehicle passing by, but rarely. You want to teach the enemy recon the lesson that they'll die any time they try to take down a garrison. Then have someone deploy on the garrison to hunt down and kill them and destroy their outpost.

If you're dead or respawning, change your respawn location to an HQ to ensure you get the strafing run in time. Note that you can place strafing runs and other command tasks while you are mortally injured and waiting for a medic.

Bombing Run

Use your bombing runs to take down enemy garrisons that enemies are using to attack your point. Only use them against confirmed (precisely marked) garrison targets, and give the squad 30 seconds or so to take the garrison down itself. They likely won't be able to because that's where the enemy will be aggressively spawning, but note that if the garrison is in your blue zone, that it'll be locked from 100m out which should make it easier.

Note that these enemy garrisons will often include the garrison on their defensive point. Your team may choose to take advantage of this.

I will freely admit to not being very good at this but I've seen it used against my team and it is truly terrifying.

Half-tracks

The initial version of this article had a bunch of theory crafting about half-tracks, based on the most effective uses I had seen. I then went out and tried to put it into practise that evening, and remembered why the only times I've lost warfare matches is because I've used half-tracks. Half-tracks appear to support, but actually violate the principle "will this ensure my team will get to the point and defend it?". Will they can double your defensive spawn capability, any player of your team can decide to relocate the half-track, either driving it into a place which will get it destroyed (the least bad option), do something incredibly stupid like forget to switch the engine off (which will waste your team resources trying to fix it) or by putting it into an effective attacking position (really bad). This is bad for exactly the same reason that an effective attacking airhead is bad. The specific game I lost because I spawned half-tracks in, we lost because a player 'helpfully' got a disabled half-track from deep within enemy territory (wasting time they could have been using to defend our point), and drove it right up behind the enemy point in an highly effective attacking position. Everyone saw this, abandoned their defense of the final point, and we lost as a result. (We were defending final because I'd effectively lost the game in the first five minutes by getting a supply truck stuck in a great attacking garrison position, and the team built a succession of four garrisons all of which drained resources away from the defense of the point we needed to defend, after losing the neutral cap).

There are two situations where a half-track might be useful as a stealth airhead: either when you have capped the first point in an offensive map and need to get to the other edge of the map for point two; or when you have your fourth point almost captured and you want to ensure you can spawn on the HQ behind the final point. In both instances, limited yourself to a single half-track and hope that someone gets it blown up shortly thereafter.

Supply Trucks

Spawn a second one as soon as you are able to. You're going to be spending a lot of the game driving these: initially to get your garrisons up and then to get supplies up to points. If you are killed in one of these, just respawn and get another. Your team will use the one you left behind, or it'll get destroyed. If you drop the supplies, turn around, go back and get more supplies.

The worst thing you can do is get a supply truck stuck, so don't take any risks driving them. It's better to have the truck and you destroyed by a tank or mine than to get it stuck.

Other Tanks

I have never met as meek and polite a group of people as armoured officers asking for another tank. They're incredibly apologetic that they wasted your resources and embarrassed that they let a tank get killed, and if they don't hear from you they're likely to just go off and fire some artillery for a while. Keep reminding the command chat that you have 2000 fuel and Tigers for everyone.

"All your team should be on the point defending"

Don't ever tell the team off for not defending. Encourage them to defend, but if they do something else, that's fine, but it's their decision, just not something you can provide support for right now. The whole point of this "Doull's Doctrine" is to make everything else inconvenient enough that defense is the obvious thing to do. Call out when outposts and garrisons get lit (red indicator) or locked (all red), but you already have plans for that. Smart squads will use the garrisons you place to flank enemy positions.

The most persistent people are those calling for a supply drop, especially recon, because that seems perfectly reasonable thing to request from their perspective. The best thing I can do at this point is claim supplies are a minute out, and then in a minute, drop supplies on the defensive point again and blame the supply drop user interface: "Sorry I double-dropped at the last location". If it's a recon squad, drop them deep, and tell them "get the garrison up after we cap".

The location they're requesting will be overrun by the attackers soon enough.

So uh how do we cap?

If you never attack, there's no advantage to the defenders defending, is there? The defenders will get bored and stop defending and go all in. At that point, one of your disobedient squad leaders or a newbie will get in the attacking circle and start capping. This might happen several times. Just be patient and re-read the airhead section. You'll get the point faster than you think.

Games as Emotion (Part Two)

Looking back at my older blog series, I guess I've broken the post title convention I used to adopt, which was The Blog Post - Part One (The Partening) or something like that. I guess if you want a subtitle, then I guess part one might be Sadness, but this part two would be Making, which of course makes no sense.

A big part of the reason I've played a lot more games this year, is that they've got a lot easier to play. Roughly this time last year, I spent a bit too much money on a new rig with a 3080 and a curved QHD high refresh rate monitor and as a result games got a lot smoother than my slightly upgraded rig from 2012.

I bought it, of course, to play the PC release of Death Stranding (104 hours), which is an incredible visual feast of a game with DLSS running. I also played and finished Deathloop (time not tracked?) and Rage 2 (40 hours), started and finished a new play through of Prey (around 15-20 hours), and played Hell Let Loose (191 hours), The Witcher 3: Wild Hunt (72 hours), Mad Max (47 hours), The Witness (15 hours), Cyberpunk 2077 (6 hours?, I've done one quest after the opening), Disco Elysium (5 hours?, I've made it out the front door of the hotel and visited a book shop), Neocab (time not tracked), replayed half of Titanfall 2 (time delta not tracked because the game whips by), wasted my time getting frustrated by bad stealth mechanics in Alien Isolation (90 minutes) and am still unsure how the majority of games systems work or what I was doing in Destiny 2 (51 hours). Of those games, Death Stranding, Hell Let Loose and the Witcher 3 have become the 5th, 4th and 6th most played games of mine since Steam started recording that sort of thing. I also clocked some hours on Slay the Spire which is undoubtedly up there on time played.

This is mostly to say that the human brain loves lists (or perhaps a table or pie chart), and I am no exception. But my play experience has been made well by getting a new PC, and in turn, I've been able to play a number of well made games. And the games on this list are well made in the sense they exhibit a technical mastery of art and video game development. But that's not what I mean when I used the phrase "well-made" in the previous post.

Instead I think specifically of the interactions between the game, it's systems and aesthetics, and the player, the act of playing itself, to create a story which is experienced in a completely separate mode from being told or shown it: making a story. I've intuitively discarded alternate phrasings like "well-played", "well-designed" or "well-done" (doing a story), because of unwanted meanings associated with those phrases and because I want to emphasise the (conscious and unconscious) choices of the people making the game (in all its aspects, not just game design). I'm trying to gesture towards an active process: the construction of a "well-made" story requires the presence of a player who willingly enters the magic circle and plays the game aided by the game design suspending their disbelief and engaging them. However there are enough random factors in any game and player that I don't want to put any blame on a player if they don't experience the emotion affect intended: this is the distinction between "well-made" and a hypothetical "well-played".

In this sense, a game is a tool that allows a player to generate emotional experiences.

(And now I am torn, because maybe the term should be "well-generated" stories, but I've already used and abused 'generate' too much).

What I'm trying to capture here is best expressed by Hell Let Loose, a first person multiplayer collaborative shooter, where players effectively enter a deliberately limited consensual reality that largely mimics specific World War 2 scenarios. Hell Let Loose defies some conventions of these games while embracing others, but at its heart, much like Death Stranding, it tries to force people to communicate and collaborate in specific modes and channels to achieve objectives. Hell Let Loose does this using a number of now standard mechanisms (pings, voice and chat, group voice and chat) but creates vertical and horizontal choke points in these mechanisms which require players depend on each other to overcome. Players read compass directions and map grids and symbols to each other because targets are hard to see and quickly become dangerous; audio channels become expressive if used sparingly but jammed if overused, with officers having to observe, listen to and use channels and expressions that their squad is not privy to; building and attacking dynamically placed critical infrastructure is more important than individual achievements.

And, unlike a co-op shooter like Left 4 Dead, Hell Let Loose has a wide breadth of experiences for players to choose from, all of which are weighted with enough significance so that they meaningfully impact play: you can choose from driving a supply truck, firing artillery, desperately trying to flank a tank to hit it with one of only two rockets, and so on, so that the potentially each of these actions is a unique experience generator even nearing 200 hours of play. For instance, last night I lead a squad for 10 minutes to push a supply truck 200 meters up a road to try to get a second attacking garrison into Foy, only to have to abandon it to defend a previously well-defended position that was now falling on the other side of the map. For those 10 minutes, moving that truck while under fire was the most important thing we could do, and none of us ever before had had driving a truck such a short distance become so meaningful in the game.

These stories are not "well-told" or "well-shown": they are unique to games. And I am wise enough to see the hand of the game makers in making specific choices in Hell Let Loose that I see a continuum between single player, highly authored experiences like Death Stranding and multi player chaotic experiences like Hell Let Loose.

I'm going to pause a while, play some more Hell Let Loose and then think about writing a part three.

Games as emotion (Part One)

 2021 was a year where I reconnected with playing games in a big way. I played a lot more games. I finished games. And I felt a lot more strongly in games.

To be clear, I didn't feel a lot more strongly about games. As has probably been obvious from this blog feed and the lack of any Roguelike Radio episodes for more than a year, I have cared less and thought less about games than probably any time in the last decade. The exception maybe the TTRPG I've been working on since 2015, but even then releasing it has felt less urgent than probably at any point during its development.

This is because I am tired of the whole rotten industry edifice: the abuse of game maker and critics by players and funders continues to harm, burn out and drive away those people in the industry while enabling abusers. I quit BGG a few years back because of the way that community ignored, created and facilitated that actively hostile environment, and I genuinely see no end in sight anywhere in the industry. The world wide failure to deal with COVID should be clear to everyone by now that capitalism ensures there is no end.

While I'm highlighting the power imbalance between workers and consumers, I should be clear that there is no safe part of the industry: game players are just as trapped in this systemic abuse as anyone else, nor elsewhere in the world. My non-game industry day job is about 8 out of 10 on the actively evil scale and I spend as much effort as I can afford trying to get it to a 7.

But games in 2021 made me shout out emotions: fiero, joy, boredom, regret, surprise and surprisingly sadness, in a complex palette, in brief shared exchanges with strangers and in ways that no other medium can possibly encompass.

I'm writing this because I want to talk out a distinction I felt between emotions engaged by games and emotions engaged by narrative in games. I'm sure that there's plenty of writing and analysis out there about this (post in the comments if you know of any), but I'm going to try to tease these out myself so excuse any old ground that I'm walking over in a way that doesn't patent infringe by causing a narrow path to slightly broaden (thanks Sony!).

And that brings me to the first feeling I want to talk about, and probably the most complex: sadness in Death Stranding. Parasocial twitter mutual GB 'doc' Burford has written extensively about this elsewhere but I want to call out a different time Death Stranding hit me in the feels: the literal end of the Elder quest chain. Quest chain is the wrong word: Death Stranding does part of what I asked for many years ago and turns quests into a trading-like game, although like everything the game does, it makes the them most gentle and forgiving version of that idea.

On this scale, the Elder is the more annoying version. He's out of the way, requires that you climb up to the top of a hill without being technically difficult, and offers little in the way of rewards. The Elder also delays his connections to the chiral network just to rub it in your face: he doesn't want you there and the game does little to pay back your investment. Unlike another mission giver, there is no hidden back story, no secrets or twist. The Elder starts being unpleasant to your face, eventually begins to like and praise you and, just as I got towards the end of the game, he leaves you a message saying he's dying and then dies.

And his death left me in tears.

I have a good relationship with my father. He nearly died last November, which is to say that I have possibly felt a tiny fraction of the grief and frustration that someone who has lost a loved one during this pandemic and been unable to travel to see them before they died or to grieve them with others afterwards. This happened well after this incident in the game, which is my circular way of saying that I don't think there are specific extenuating circumstances that might have rendered me vulnerable to this story arc in a way someone else might not be.

Instead I think it was a story well-made. It wasn't well-told, or well-shown: the holo image I saw of the man fit the thematic conceit of Death Stranding, and the plainly written emails aren't especially memorable in themselves. This underdevelopment is typical Kojima canniness towards the broader themes he's exploring, but that set dressing needed me to act and feel my along the path he had laid out. My thesis here is games are unique in the way they can make emotions in a way no other medium can.

And in part two, I attempt to explain what I mean by the phrase a "well-made" story.

His Eyes - Part One

“Words have lost their power. I could tell you your life was a lie but it’d barely graze the hardened callouses you’ve built to protect yourselves. Whereas for me those words rang true like the call of the bugle my grandfather fell into the trenches fighting for. Thundered like the New Zealand guns that shattered his friends.”

“At least we can agree on one thing. Fuck Australia!” They toasted together burning their throats with the space brew.

“It’s an unusual position I find myself in. Plotting trajectories with the grandchildren of those whose earlier arcs broke him.”

Why not stay in China? The words stayed unsaid but he curled his mouth downwards, sliding his top lip over the stubble under his bottom lip. He had refused to depilate, roaring ‘I spent so much getting this.’

“I had reached the periapsis of what the Party would find acceptable. China was too small for my ambition and my childhood dream was not going to resolve itself. To Rocket Labs!” He toasted again and all four raised their drinking tubes.

There was not enough gravity to drink from glasses in Deimos station. Deimos station! The words themselves made him giddy with how far they’d come and how much they’d achieved. But not just them. The Americans. With their Callisto-bound nuclear rocket parked just over the horizon. They kept to themselves, not just for safety, but the political situation back home had worsened and while the spirit of international cooperation flowed so far, it apparently stopped short of coming the final kilometre of the 157 million they had travelled. To celebrate his birthday.

“Deimos station, this is mission control. We don’t mean to interrupt your fun, but NASA has an urgent request.”
“Mission control, how can we help?” The commander spoke up, flashing glances around the galley.
“It appears Triumphant’s uplink is out. They’re running diagnostics Earth side but we might need to EVA and get a relay up.”
“Decompression protocol will take two hours. What are our remote options?”
“So far we don’t think we can get an antenna up high enough using one of the drones.”
“Can we print one? Straight up from the refinery.” Engineering suggested.
“That’s a… novel option. We’ll run the numbers. But prep for the EVA.”
“We’ll get the relay in place but to get that far up the ridge we may as well roll down the other side and tap on their hull.” He said.

He was out on the surface with Payload. She was smiling, excited to be out on the surface again so soon. The rover seats were filled with the antenna mast, tools and emergency gear in case the situation on the American spaceship was worse than a communications error.
They reached the top of the ridge.
“Hailing Triumphant. This is Deimos station. Hailing Triumphant.” He repeated the hail using another set of standard codecs, then switched to analog radio in case the digital systems had failed. When they didn’t respond, Payload hefted a scope from the front of the rover.
“No exterior damage visible. No outgassing. No one on the surface. Hatches are all closed. Uh… the crew module is warm. Really warm. Radiators are pumping out a lot of heat to compensate so its not a thermal circulation issue. It’s survivable but not comfortable in there.”
“Ok. Forget the mast. We can run the relay from the rover. It’s about a 200 metre walk down the hill. Let’s get going.” He checked the brakes on the rover and followed Payload down the slope.

“They’ve dug up one of the RTGs.” Payload said as they reached the shadow of the ship. The RTGs were radioisotope thermal generators: basically big radioactive batteries that relied on the the decay of isotopes inside them to create heat to generate electricity. Deimos station had supplied a couple to Triumphant to keep it powered to avoid running their reactor at night: there was no way of turning the RTGs off whereas the reactor could be shutdown using control rods to allow it to be serviced. But the RTGs also sank into the moon’s surface and had to be periodically moved to avoid overheating, a job that wasn’t due for another few weeks. The boxy shape of the RTG was visible about 50 meters beyond the ship.
TICK
The closest airlock hatch of the two was up a ladder next to the foreleg of the spaceship. He climbed up and banged on the body of the airlock. Then he waited for a response, holding his glove to the hatch to try to detect any vibrations. Nothing. He banged again, twice more, and checked. The hull rang like a bell from his impacts but no one replied.

The next step was complicated. With the crew inside the airlock would normally be pressurized. He would have to evacuate all air from the outermost part of the airlock, called the crew airlock before entering it. But there were no manual controls external to the hull to do so. He’d have to hope that the crew airlock was unoccupied and the pressure door to the inner “equipment airlock” was closed. If not, he’d depressurise the whole ship.
He carried hull patches to patch the holes he was about to make. But not enough to patch the holes twice. The equipment airlock door needed to be closed for him to be able to enter the ship at all. Best assume the best scenario and operate on that basis.
TICK

He began drilling.
TICK

The soft pop of air turned into a jet as he pulled the drill bit from the hole. How long would the crew airlock need to empty? A minute? Two minutes? He’d work on exposing the door lock mechanism in the mean time.
TICK

The jets in the door died down suddenly. The door was closed between the outer and inner airlocks. He signalled down to Payload, forced the hatch open and stepped inside.
TICK

Payload and him worked quickly to plug and seal the holes he’d drilled. TICK. The seals would take a couple of minutes to set in vacuum and they’d hold for years. TICK. Then once the seals were set, they pressurised both the outer and inner airlocks to a low pressure, high oxygen mix. TICK.  Best keep this mix in case they had to leave in a hurry. TICK. Open the pressure door to the equipment room. TICK TICK TICK They could take the space suits off here and enter the ship without TICK TICK harming anyone inside. TICK TICK TICK TICK He put his hand to Payload’s helmet, just as she was about to release the seal.

TICK TICK TICK TICK TICK TICK TICK TICK TICK TICK TICK TICK TICK TICK TICK

Both their suit geiger counters were furiously warning them about the radiation levels in the inner airlock.

“The reactor is fine.” They repeated the mantra to each other. “The reactor is fine.” If it wasn’t, they’d have seen red hot molten rock where the rear of the ship would have been and their hair would be already falling out in clumps and the hard radiation would be dancing in white flashes through their retinas.

So where had the radiation come from?

The air in the outer airlock came from bottled air reserves carried on the ship. It had been clean and radiation free until they’d open the inner airlock. The air in the inner airlock mixed with the ship, although they could control the pressure and oxygen content. The air in the inner airlock was filled with radioactive particles which as they decayed triggered the geiger counters. The ship was filled with isotopes. Spread around the corners of the ship intentionally. From the RTG. The crew had taken one of the cells out of the RTG and opened it up inside the ship and spread its contents everywhere.

The radiation levels in the ship wouldn’t kill them. At least not for decades and only if they stayed around long enough. But swallowing some of the radioactive material would. It would stay inside them, and although the heavy metal poisoning would be bad, the radiation it would continue to emit would give them cancer and a horrible untreatable death.

The ship was a trap.

PLAN.B

Michael Brough has just released an expansion to 868-HACK called PLAN.B and it's available on Steam as DLC and iOS as an in app purchase. Much like his recent Ossuary expansion to Imbroglio, I consider it pretty essential but for different reasons. Ossuary made the early game more interesting by allowing for a much greater variety of deck builds which were not necessarily game winning but were a lot more fun to play. This was great for a player like myself who wasn't likely to get to the end game but was looking for a fulfilling experience.

PLAN.B is instead for players with deep understanding of 868-HACK and who are looking for increased difficulty at the start, but more competitive long term play. Luckily, I also fall into this category so both releases have hit the sweet spot for my game skill. PLAN.B makes the game more difficult by having the deceptively named power ups occur from game one instead of appearing only after a few streak games. But at the same time it adds 8 new programs to give you more control. The cumulative effect is that while I feel like each run is harder (even just to survive) I've ended up playing longer streaks.

The new abilities are good but not essential (with the exception of .QUIT which is situational but vital given the power up changes) but they do a good job of filling the middle ground between a bad build and a good build in part by decreasing the overall likelihood of finding the 'perfect combination' and partly by adding cheap and useful ways of killing things (and I have no idea what .SAVE does but I'm okay with that). All but one, .CULL which is situational and expensive and while it has synergies, they're also expensive. I haven't tested .ICE/.CULL but that would make this useful if it works (and be the kind of enemy clamping, screen clearing ability that the name suggests it should be).

Of course, this wouldn't be a 'I love MichaelBrough's game' blog post without me trying to backseat design :)

(My urge to back seat design is worse than this post appears. I had written a longer post exploring two additional abilities, but ultimately that felt incredibly self indulgent).

I'm less sure PLAN.B is worth getting if you bounced on the original game, but if you managed at least a single streak score then this expansion is going to be a must have. The power ups fix many of the issues that single game score chasing scored by ramping up the difficulty enough to make high score chasing unpleasant and much more unpredictable and reducing the surprise of suddenly finding power ups affecting how you played (much in the same way that the jungle in Spelunky throws a difficulty curve ball).

Unangband 0.6.5c released

I would like to announce that Unangband 0.6.5c has been released by the new Unangband maintainer DGoldDragon28. DGoldDragon28 had been developing a variant based on Unangband, and now has my blessing to continue with the main Unangband releases as well.

You can find the full details at https://dgolddragon28.github.io/Unangband/ which is also the new Unangband homepage. Please redirect your links.

4:40 am

I started recording the latest Roguelike Radio podcast (on Imbroglio) at 4:40 am in order to accomodate both UK and US based guests which is why I have such a slow start to the show.

One point I touched on is how Imbroglio has the ingredients of a roguelike with a very different set of outcomes, which justifies Michael Brough's labelling of it as 'roguelike?'. This missing piece is close to the tactics versus strategy debate but it doesn't fall on the same axis. It's also close to a puzzle form but it isn't just procedural puzzle solving. I'd like to label it "improvisation" because it feels very much like improvisation (in theatre) or how I imagine musical improvisation plays out. Imbroglio has improvisation, but the core design discourages it in some of the ways we talked about (at the level I'm playing at).

I don't think I've seen anyone write clearly about improvisation in depth in the context of game play (Feel free to point me to articles I may have missed) except perhaps relating to Far Cry 2. More significantly, I'm not sure if there are games which have improvisation as their primary mechanic (Spelunky?) and I'd be interested in hearing about whether there are any games which do so.

Texclipse & LuaTex 2016

Just some quick notes for fixing up Texclipse to use LuaTex 2016.

1. Remove the --src-specials option from the Build options.
2. Add the following 2 lines as early as you can in your document:
"\usepackage{luatex85}
\def\pgfsysdriver{pgfsys-pdftex.def}"
3. Font paths don't appear to be supported in Windows. Instead copy the fonts into the fonts directory.

How High Frontier builds futures

I've been a little hesitant about talking about the design work going into the High Frontier RPG since the arguments of the politest naysayers to my first post about it  can be approximated by "I haven't been to Russia so it can't exist." There are far less polite responses on the High Frontier board game mailing list, so I appreciate the general tone of the arguments being made in the comments - I'm just not swayed by them because among other things, they miss the fundamental fact that the person whose post I linked to is not just a hysterical tumblr user, but someone who has actually won a landmark precedent setting court case on the exact thing I was talking about.

Nonetheless, I'm also feeling guilty about a throwaway line I made in the last design post, which I think needs clarification and expansion on:

"Unlike virtually every other RPG on the market (sans Microscope), High Frontier RPG does not have a fixed game world"

This is, of course, nonsense as every single game master can attest to - the game world evolves as soon as players being to interact with it. The caveat I should have added at the time was "unlike virtually every other published setting on the market" and even then that is insufficient, as much like comics, RPG settings have to be torn asunder and rewritten to account for inevitable power creep and conflicts in the stories set in them.

What I meant, is that the published setting for the High Frontier RPG consists of very few immutable rules: nuclear power in space, wet extra planetary locations, a new space race, and even then there's potential caveats and loop holes that may mean not even these are true - for instance, the data used to predict icy comets and Ceres, a frozen Mars and water in the clouds of Venus has turned out to be inaccurate but High Frontier relies so much on these places having useful amounts of water to keep the game balanced and interesting that it'd be a different game if these changes were made.

The rest of the High Frontier RPG universe is not fixed: its random and chaotic and procedurally generated from the players actions directly (you can go out and set up factories and colonies yourself to increase the tech level you have available) and indirectly (the chosen Space Politics will directly impact how the social, political and technological milieu of the game evolves). Even then, I'm only attempting to stuff 60 years into the rules (the average time simulated by a High Frontier board game) and borrowing heavily from all sorts of science fiction tropes to try to guide what this looks like.

At the heart of this system is trends: a trend determines what the next few impacts on the crew are - be it a technology they can begin using, or a change to the way they operate or the missions they get, or a new type of human they are forced to evolve into or are replaced by. I split the trends up into ones driven by Mission Control, ones driven by the political environment that Mission control works in, and wider social trends representing what long term trends are happening Earthside (as distinct from short term events).

I'm going to quote from one person's experience of messing around with the trend system rather than an actual game session, to give you a feel for what this might play like:

I generated the equivalent of Luftwaffe-in-Space: Red MCSU - Crew Nationality German. Not sure how to determine starting politics (always Purple?), but I simply rolled for it at the beginning and started on Red as well.

In a fairly small number of turns:

-Zipped out to Ceres with a VASIMR-Orion combo and planted a factory.

-Performed an Orbital Bombardment Weapons Test at Deimos.

-Got assigned another refinery mission out to Dione, but rolled snake eyes when crossing Saturn's rings, ending things rather prematurely.

Other cool things that came up that would have been great for an RPG session:

-En route to Dione the Germans received an additional mission to rescue a stranded Indian crew...on Dione. Didn't know if it is possible to take multiple missions if the destinations for both of them are the same, but I never got there to find out. The RPG possibilities for that encounter would have been fantastic. "We're here to rescue you. Also this is our factory now. You seem upset, why?"

-Not sure if I was doing the Earthside trends correctly, but it was generally of an increasingly gruesome flavor thanks to the Red space politics. A whole lot of Ludditism, some Surveillance State, and by the time my Germans met their unlucky fate, someone down the well had built a tomb to Fearless Leader that was visible from space. Could see having to react to a parade of such things being really interesting (especially with a crew differing strongly from Earthside trends).

-Rolling for Stresses, the Military Payload Specialist ended up with Pacifist. Lots of interesting RPG potential there, though I never encountered a combat situation.

The intuitive approach for building trends would be to go with a technology tree style structure. But I know from previous experience that tech trees are very expensive time wise to create and balance, and often feel restricting rather than enabling. So I've ended up going with a tech era system, with a random table in each era determining the trend for the era. And about midway through the era there should be a trend change which rolls 1D6 + big positive or small negative bias, instead of 2D6 + small positive or negative bias, effectively moving from a wide band of overlapping options, to a much narrower band of less overlapping and more individually likely options.

And each subsequent era has the extremes going more, well extreme. The most authoritarian regimes start out merely performing Great Projects. They then move to being Big Brothers or Failed States, and then Homeward Hive or Forever Wars. And where they can end up? Well let's just say aggressive Grey Goo Berserker starships consuming everything in their path is only the second worst option.

Some long overdue administration

This is only 3 years overdue.

Every vote for the 2013 Ascii Dreams Roguelike of the Year poll is below. As for why I stopped? I kind of forgot about doing it the next year. Which is probably an indication that it stopped being fun to do. I wish someone a little more active in the community had picked up the idea and run with it, but apparently it wasn't important enough for someone else to feel the need to do so.

_____rogue the space	0 (0%)
@Star Wars	0 (0%)
10 Second Roguelike	0 (0%)
3	0 (0%)
3079	0 (0%)
3089	0 (0%)
8.68-HACK	0 (0%)
868-HACK	2 (0%)
86856527	1 (0%)
88 Pages	0 (0%)
A DAY @ THE ZOO	0 (0%)
A False Saint, An Honest Rogue	0 (0%)
Ad Astra Per Aspera	0 (0%)
ADOM	85 (25%)
ADOM II	22 (6%)
Adventure Dungeon	1 (0%)
Adventure Mall	0 (0%)
Akamar	0 (0%)
Alchemy	0 (0%)
AlexandriaRL	0 (0%)
Allure of the Stars	0 (0%)
Alternate Dimension Rogue Like	0 (0%)
Anarchial	0 (0%)
Angry Troll versus Magic Bridge	0 (0%)
Appeasing the God	0 (0%)
Archmaster	0 (0%)
Arcology Escape	0 (0%)
AscentRL	1 (0%)
Asterogue	1 (0%)
Asylum Escape	0 (0%)
Attack The Geth	1 (0%)
Aurora	2 (0%)
Back up	0 (0%)
Bardess	0 (0%)
Beltham's Lair	0 (0%)
Bionic Dues	1 (0%)
Black Mage Goes Rogue	0 (0%)
Bonfire	0 (0%)
Borstal	0 (0%)
Brogue	23 (6%)
Bronze and Faith	0 (0%)
BRS-081	0 (0%)
Bughack	0 (0%)
Bump!	0 (0%)
Cataclysm: Dark Days Ahead	55 (16%)
Caverns of Shrug	0 (0%)
Chase Brannick: Space Mechanic	0 (0%)
Chest Quest	0 (0%)
Chicken and Thyme	0 (0%)
Cogs of Cronus	0 (0%)
ColdRL	0 (0%)
Comrade Pixel	0 (0%)
Consuming Shadow	0 (0%)
CoreRL	0 (0%)
Cosmic Commando	1 (0%)
Cosplay Mystery Dungeon	0 (0%)
Cutpurse Castle	0 (0%)
De Sade's Dungeon	0 (0%)
Dead Man Walking	0 (0%)
Delusions of Grandeur	0 (0%)
Delver	2 (0%)
Depths of Tuzua	0 (0%)
Desktop Dungeons	7 (2%)
Diablo, the Roguelike	4 (1%)
	Disc RL
Disc RL	0 (0%)
Distant Echoes of Ancient Lies	0 (0%)
DiveDive	0 (0%)
Don't Starve	4 (1%)
Doom, the Roguelike	24 (7%)
Double Rogue	0 (0%)
Down The Brain	0 (0%)
Dragon's Lair	0 (0%)
Dragons Hoard	0 (0%)
Dragonslayer	0 (0%)
Drakefire Chasm	1 (0%)
Dungeon Crawl Stone Soup	37 (11%)
Dungeon Dashers	1 (0%)
Dungeon Fray	0 (0%)
Dungeon Ho!	0 (0%)
Dungeon of the Endless	0 (0%)
Dungeon Penetrator	0 (0%)
Dungeon X: Flesh Wounds	0 (0%)
Dungeon-Themed Starvation Simulator	0 (0%)
Dungeonmans	7 (2%)
Dungeons of Dredmor	13 (3%)
Dungeons of Kong	0 (0%)
Dying Embers	0 (0%)
DynaHack	1 (0%)
Eldritch	2 (0%)
Elite RL	0 (0%)
Elona+	11 (3%)
Ending	0 (0%)
Enter the Roguelike Dimension (EtRD)	0 (0%)
Epilogue	1 (0%)
Equin: The Lantern	0 (0%)
Eternal Cave	0 (0%)
EXCELent Rogue	0 (0%)
fabu	0 (0%)
Faith in RL	0 (0%)
Famaze	0 (0%)
Fame	1 (0%)
Fancy Skulls	1 (0%)
Farm rl	0 (0%)
FHRL	0 (0%)
Firestorm City	0 (0%)
Fishtryoshka	0 (0%)
Fisticuffmanship	0 (0%)
FlatlineRL	0 (0%)
Fleeing the Fray	0 (0%)
Forays into Norrendrin	3 (0%)
Friendly Meddling	0 (0%)
FunhouseRL	0 (0%)
Gatecrashers	0 (0%)
Gelatinous	0 (0%)
Goblin Men	0 (0%)
GUTS	0 (0%)
Hack, Slash, Loot	2 (0%)
Han Yolo and the Mysterious Planet	0 (0%)
Hark!	0 (0%)
Herculeum	0 (0%)
Heroes of Loot	0 (0%)
Hoplite	3 (0%)
hproguelike	0 (0%)
HumFullRL	0 (0%)
Hunted	0 (0%)
Hush Little One	0 (0%)
Hydra Slayer	1 (0%)
HyperRogue	2 (0%)
Illuminascii	0 (0%)
Incavead: infinite cave adventure	3 (0%)
Infection	0 (0%)
Infra Arcana	6 (1%)
Inside Out	0 (0%)
Interloper	0 (0%)
Into the Labyrinth	0 (0%)
It Did Not End Well	0 (0%)
Kali's Ladder	1 (0%)
KeeperRL	1 (0%)
Kerkerkruip	1 (0%)
Khu-Phu-Ka	0 (0%)
KlingonRL	0 (0%)
Kollum: The Pressure Valve	0 (0%)
Krater	0 (0%)
Kukulima	0 (0%)
Legend of Dungeon	4 (1%)
Liberation of Yama	0 (0%)
Like a Rogue	0 (0%)
Live as Long as Possible	0 (0%)
Lost Crypts	0 (0%)
Lost Labyrinth	1 (0%)
Lurk Under Wires	0 (0%)
MacRL	0 (0%)
Magic Fountain	0 (0%)
Malachite Dreams	0 (0%)
Man in a Maze	0 (0%)
Mazmorra	0 (0%)
MGRL	0 (0%)
MidBoss	0 (0%)
MidsomerRL	0 (0%)
MLP RL	0 (0%)
mmoRL	0 (0%)
Mosaic	0 (0%)
Moving@	0 (0%)
MovingETA v0.07	0 (0%)
Mysterious Castle	1 (0%)
MythosRL	0 (0%)
Nebulaic Toaster	0 (0%)
NEOScavenger	2 (0%)
Nightmare Tyrant	0 (0%)
NinjaRL	0 (0%)
Not the Robots	0 (0%)
Now Hiring: Zookeepers	0 (0%)
Noxico	2 (0%)
NPPAngband	4 (1%)
NPPMoria	2 (0%)
Nuclear Throne	0 (0%)
Nya Quest	0 (0%)
Nyanko	0 (0%)
Occult Chronicles	0 (0%)
One Way Heroics	3 (0%)
Paranautical Activity	1 (0%)
Peli	0 (0%)
Pitman	0 (0%)
Pixel Dungeon	6 (1%)
Pixel Piracy	2 (0%)
PonyRL	2 (0%)
Possession: Escape from the Nether Regions	1 (0%)
Post Future Vagabond	0 (0%)
Prehistorical Bean Climber	0 (0%)
PRIME	2 (0%)
Prospector	3 (0%)
Pugnacious Wizards	0 (0%)
Pugnacious Wizards 2	0 (0%)
PurpRL	0 (0%)
Quadropus Rampage	0 (0%)
QuickHack	1 (0%)
Rasatala	1 (0%)
Red Rogue	3 (0%)
Return to the Dungeons of Doom	0 (0%)
Rillaung	0 (0%)
Risk of Rain	7 (2%)
Rodney	0 (0%)
rogue (7DRL)	0 (0%)
Rogue Break	0 (0%)
Rogue City Scavenger	1 (0%)
Rogue Coder	0 (0%)
Rogue Dream	0 (0%)
Rogue Effect	0 (0%)
Rogue Fleet	0 (0%)
Rogue in the Void	0 (0%)
Rogue Legacy	15 (4%)
Rogue Shooter	0 (0%)
Rogue Valley	0 (0%)
Rogue's Eye	0 (0%)
Rogue's Labyrinth	0 (0%)
Rogue's Souls	0 (0%)
Rogue's Tale	2 (0%)
Rogue3D	0 (0%)
Roguelike Runner	0 (0%)
RogueMek	0 (0%)
Room Rogue	0 (0%)
RRRSAncientBlade	0 (0%)
RuneMaster	0 (0%)
Ruoeg, a minimalist roguelike	0 (0%)
SanitasRL	0 (0%)
Scrounger	0 (0%)
Seduction Quest	0 (0%)
segfault	0 (0%)
Seven Days in Space	0 (0%)
ShadowsofHumanity	0 (0%)
Sil	7 (2%)
Skool Eskape	0 (0%)
SkullDorado	0 (0%)
Slaughter	0 (0%)
Smashing Bad	0 (0%)
So Many Jagged Shards	0 (0%)
Sorcery Saga: The Curse of the Great Curry God	0 (0%)
Spelunky HD	11 (3%)
Splitter	0 (0%)
Starship Rex	0 (0%)
Steam Marines	5 (1%)
Stink Warrior	0 (0%)
Sunk Coast	0 (0%)
SurviveRL	0 (0%)
SurvivorRL	0 (0%)
Swift Swurd	0 (0%)
Sword of the Stars: The Pit	5 (1%)
T.H.A.D. - 7DRL edition	0 (0%)
T.o.M.E. 4	139 (41%)
T@XI	0 (0%)
Teleglitch	5 (1%)
Tetrogue	0 (0%)
The Artifact	0 (0%)
The Aurora Wager	0 (0%)
The Case of the Girl and the Red Dress	0 (0%)
The Conception	0 (0%)
The Fourth Wall	0 (0%)
The Guided Fate Paradox	0 (0%)
The Hunger Games	0 (0%)
The Land	2 (0%)
The Monastery Garden	0 (0%)
The Power of Dreams	0 (0%)
The Reset Button	0 (0%)
The Royal Wedding	0 (0%)
The Veins of the Earth	1 (0%)
The Wizard's Lair	0 (0%)
TomeNET	2 (0%)
Tower of Guns	2 (0%)
Triangle Wizard	5 (1%)
Ultima Ratio Regnum	6 (1%)
UnBrogue	1 (0%)
Underhall	0 (0%)
Unhappy Devil	0 (0%)
Unnamed RL	0 (0%)
UnReal World	22 (6%)
Uushubud	0 (0%)
Versus Time	0 (0%)
Voyage to Farland	2 (0%)
Warp Core Breach	0 (0%)
Wayward	8 (2%)
WazHack	6 (1%)
Web Raid Mobile	0 (0%)
Weeping Angels	0 (0%)
Witchaven the Roguelike	1 (0%)
X@COM	3 (0%)
Zero-Player Game	0 (0%)
ZomgRL	0 (0%)
Zoo Base	0 (0%)