Official development blog


Whew! I’ve finally finished putting together all the achievements-related features for Cogmind! As a large single system I’d like to provide a rundown of the whole process and reasoning here on the blog. It’ll be divided into two articles, this first one exploring achievements in general, how they were selected and organized, icon creation, and underlying implementation. Next time I’ll cover meta aspects like the UI and Steam integration.

I certainly spent a long time on this feature, so I guess the first question that comes to mind is why add achievements at all? In my case the answer isn’t simply “it’s just something games on Steam do to sell better” (although Valve recommends them for this reason :P), because after all Cogmind achievements are available to non-Steam players as well, and throughout development my focus has always been first and foremost on making the non-Steam version the best it can be as the “primary version”--Steam is simply a distribution platform.

When first starting out with achievement work, to help guide the development process I came up with my own list of reasons for adding them:

  • Record progress and skill milestones. Prior to achievements Cogmind already included a couple such systems in the form of lore and item gallery completion rates, and aside from their reference value they’ve shown to be useful among players when it comes to keeping track of their own long-term progress, and also measuring their progress versus other players in the community. Achievements provide yet another metric for both personal advancement and to compare against other players.
  • Recognize special accomplishments. Some interesting aspects of a run that a player might accomplish in the course of normal play under certain circumstances may go unnoticed or forgotten in the long term. Achievements can offer formal recognition of these accomplishments, like Shocking Conclusion, earned after corrupting 50 hostiles (something that combat players with a heavy EM focus might manage in a single run).
  • Create unique meta challenges. Unlike achievements that recognize existing milestones or likely (if situational) accomplishments, another type of achievement can actually suggest new goals outside the normal scope of gameplay. For example the Giant Slayer achievement challenges the player to take down five Behemoths. It’s fairly rare for players to even encounter this many in a single run, much less attack them (since they can be troublesome and are often best avoided when possible). So this isn’t the kind of achievement one might incidentally earn, but instead means actively hunting them down, requiring a different style and possibly a specialized build. Although having achievements at all increases replayability (as a kind of “collectible” like the lore and gallery), meta challenges are one of the best categories in that regard because they essentially expand the scope of the game.
  • Teach players about the world or mechanics. At the most basic level, achievements can be an alternative indirect method of helping players learn. Lots of games have these, perhaps because many players are blind to tutorials or help messages but pay a lot more attention when it comes to achievements! Still, although I added quite a few of these there isn’t a lot of overlap with Cogmind’s dedicated tutorial messages. For example there aren’t any “achievements” for basic UI functionality (which the tutorial messages cover), but instead we have achievements for some mechanics worth highlighting which don’t otherwise have a tutorial, e.g. Hehehe (“Reprogram a trap.”), or useful tips like Short-term Sacrifices (“Escape a Stasis Trap with help from an explosion.”). Loot Pinata (“Destroy a Hauler.”) was added because I’ve heard of players going for a while before realizing Haulers are a pretty good source of decent parts, or at least a source of spares, so achievements like these are aimed mainly at the players interested in actively seeking out achievements, where these are low-hanging fruit and also teach something in the process.
  • Hint at some things possible in the game. Achievements can be used as a way to tease content or features that players may not have early or easy access to, kind of as an incentive to keep exploring further. “Subspace Traveler” is simply described as “Find a way to teleport”--most players still don’t even know this is a thing in Cogmind :). Then there’s “WMD” (“Destroy 100 robots in a single turn.”), suggesting that it’s possible to wield some pretty devastating firepower. Similarly, only one plot-related achievement was intentionally left unhidden, “Origins,” which is described as “Discover what you really are.” Not too revealing, other than to suggest that there’s more to what’s going on than one might assume until starting to discover the story elements (intentionally somewhat left out of main areas of play).
  • Suggest alternative play styles. Although many people will have their preferred play style(s), providing achievements that emphasize a specific style is a good way to get players branching out, possibly discovering additional ways to enjoy the game, or simply approaching a new style as a different challenge. “Explosive Specialist” (“Destroy 100 hostiles with at least 90% of damage dealt by explosives.”) is one of the more straightforward examples, likely requiring a dedicated build focused more around blowing things up for an extended period. And not just a build but the associated tactics and long-term strategy as well--specializing in explosive-based combat means paying extra attention to matter acquisition and consumption, managing the risks of likely opening up a lot of terrain and increasing exposure across the combat zone, and dealing with the likely higher alert that results.

Although achievements are available both on and off Steam, having never played a game with achievements (or used Steam in any serious gaming capacity) I did have to spend some time researching how Steam handles them as well as how other devs have chosen to use them in their games. You’ll see this information come into play a little more later, but starting such a big system without a decent plan laid out in advance is just asking for trouble.

A more specific area for early consideration was how to treat difficulty levels. Cogmind has multiple difficulty settings, so how do achievements work in relation to those? Here I thought through three different approaches:

  • Require a minimum difficulty level for certain achievements. This one’s pretty unfair to some people who enjoy unlocking achievements, those who just want to play at their own level, undermining the purpose of adding difficulty levels in the first place.
  • Have separate achievements for every achievement at every difficulty level. Even though it’s possible to automatically award same-type achievements of a lower difficulty each time a new one is earned on high difficulty (important to avoid forcing better players to also play at a lower difficulty just to earn achievements), I’d prefer to avoid massively bloating the achievements list like this. An informal poll of current players showed that most people were against achievements for different difficulty levels. Instead I’d like to just make it possible to clear achievements in case a player wants to permanently move up to a higher difficulty and start over. I did, however, make it so that the game internally records the highest difficulty on which each achievement was earned, so this data could be exposed in the future considering that Cogmind has its own achievement browsing interface.
  • Allow any achievement to be earned at any difficulty level. This is what I went with. Simple. Accommodating.


Cogmind has a lot of achievements, and any time you have a lot of something it can benefit from some organization. I divided achievements into six categories, which comes in useful when there’s a need or desire to filter or sort them, or even simply to assist with quicker recognition of an achievement’s icon.

Some categories also further subdivide their achievements into “tiers” where appropriate (higher tiers being more difficult), similarly aiding in recognition and differentiation as we’ll see later with the icon design.


Initial category distribution for first batch of 256 achievements.

  • Mechanics: A group of mostly basic achievements covering common useful tactics and learning about systems. Even the obvious ones can serve as a way to reinforce features that players may accidentally trigger without realizing it. These make up over a quarter of the total, as there are quite a few different suitable mechanics.
  • Style: Specifically play style-related achievements, like combat, stealth, hacking, etc. These are generally earned through normal play using a given style/strategy, and while some might be more challenging or require focus in a certain area, they’re not difficult enough to be considered “special challenges ” (a separate category).
  • Progress: Personal meta progress like high scores, lore/gallery collection, and world exploration.
  • Challenges: This group doesn’t have anything to do with Cogmind’s “Challenge Modes,” but are instead achievement-specific individual challenges ranging from Tier 1 (not too hard) to Tier 2 (hard) to Tier 3 (pretty hard!). This is currently the smallest category, but is also the most likely to grow if and when more achievements are added in the future. (It’s also the smallest because a fair number of challenges are siphoned off by the later Wins category.)
  • Events: Story-related elements. Basically once you’ve visited every location and exhausted all the branching possibilities of the plot, you’ll have all of these. This category is entirely hidden, though, so these aren’t achievements to be explicitly sought out as if going down a list. You’ve just gotta explore and maybe in some cases use the in-game lore as clues to find more out-of-the-way areas.
  • Wins: There are many different ways to win the game, whether achieving one of the seven unique endings or simply winning by overcoming other challenging scenarios, so these get a whole category of their own. A lot of win-related achievements are technically considered Challenges, but since they require a win at the end they’re all collected under this category rather than the other one above.

Notice that these categories somewhat roughly align with the six reasons for adding achievements listed earlier, which probably isn’t a coincidence :)


I didn’t have any specific goal for the total number of achievements, just wanted to come up with what seemed like a pretty good variety covering as many aspects of the experience as possible. And while I could’ve eventually put together a large selection on my own, the process certainly benefited from player suggestions! Long before I started working on achievements, there was already a forum thread where players could submit ideas, and one of my very first actions when starting achievements work was to read through the entire thread and harvest any ideas compatible with both Cogmind’s architecture and my aims for achievements, in some cases modifying them where necessary.

Aside from of course thinking up a fair number of achievement concepts from scratch based on my own play experiences, I had a couple other outside sources for inspiration as well:

  • Score sheets: Years before achievements were even a consideration, Cogmind’s extensive and ever-expanding score sheets already recorded quite a few stats and accomplishments, so this was an obvious place to look for meaningful achievements. As of Beta 5 score sheets held more than 600 values, plenty to choose from!
  • Game Manual: I also parsed the manual to see if my Mechanics list wasn’t potentially missing out on anything worth emphasizing with its own achievement, although in the end not many came from here.

Coming up with a good set of achievements was a very gradual process of adding new ones to the list and making repeated passes over that list to group them by likely category, although this was before the final categories were determined so it involved a bit of back and forth. At first there were a lot of uncertain achievements organized into tentative categories, and later on the appropriate categories (and specifically their names) became clear, further helping flesh out and finalize the achievements.

Even within categories there are subcategories. I mentioned tiers earlier as a form of subcategory, but for determining which achievements to add, more important than difficulty-based subcategories are type-based subcategories. For example the rather large Mechanics category is broken down into general mechanics, combat mechanics, alert, interactive machines, machine hacking, robot hacking, information warfare, flight, allies, and more. (My earlier summary of Style-related achievements also happens to essentially reflect a partial list of its hidden subcategories.) This level of subcategory was created purely for my own organizational and development purposes, though, there’s no need to make them public.


Well, not public in the game anyway--may as well demonstrate here how they appear in the game data for my own reference :)

Prior to building the achievements list I also set out some important guiding principles:

  • Most importantly, an achievement should be obtainable in the space of a single run (rather than accumulated across many runs). First of all this does a better job of adhering to the roguelike spirit, which places a lot of emphasis on individual runs given the nature of procedural generation and permadeath. Second, since there would be so many achievement descriptions which ideally need to be as short as possible, it’d really simplify the system to not require every single one to specify whether it’s per run or across all runs combined. There are a few exceptional “meta achievements,” but it’s a small number and they’re obvious enough to not even require explicitly pointing out that it doesn’t refer to a single run, e.g. “Curator: Reach 100% gallery collection.”
  • While all achievements are definitely guaranteed earnable with the right tactics, strategy, and skill level, not all achievements will be within reach of all players. Certainly more of them become accessible to a wider audience by lowering the difficulty level, but it’s still going to take a decent amount of practice and skill to reach 100%. Some of them are downright hard even on easier difficulties, but serve as interesting goals in and of themselves, supplementing the many goals already suggested by the plot and world layout.
  • Although some games do this, I decided against having achievements emphasizing negative effects and experiences that might not ever happen to certain players, since it feels counter-intuitive to require that players intentionally subject themselves or their run to nasty things simply to earn achievements. A small number of exceptions were made for situations that will certainly happen at one point or another, but these are specifically designated as hidden achievements so that they’re not something to aim for--they’ll be earned naturally through regular play.

Again there was no target number of achievements, but by pure coincidence the final tally came to 256. It was originally 255, but after late-stage polishing I ended up removing a couple and adding a few :P. “Too bad” this is only the first batch--more achievements will almost certainly be added and end up ruining this rather appropriate number!


For now we can admire this number on the Steam store page.


The naming of achievements is important, but pretty straightforward so I don’t have much to say about that other than pointing out the obvious: players like names that are fun/interesting/provocative/cool/punny/etc. There were plenty of opportunities to come up with a variety of names when there are so many achievements :D

Of course there are a lot more details to creating a good set of achievements beyond simply choosing and naming them!


While a lot of achievements are essentially binary (“player did X”), many others involve reaching certain thresholds, which usually means numbers. It was really nice to have so much score sheet data (including archives) and past analyses to draw on in order to set realistic values for these numbers.


Excerpt of run stats from Beta 4 (the full table includes 446,028 data points). Filtering and sorting this data is able to answer a lot of questions about balance and difficulty, suggesting potential achievement requirements.

I could adjust the difficulty of an achievement based on the precise reported performance of players in earlier Betas, and further informed decisions by recalling anecdotal evidence from player discussions over the years--I’m always listening to stories and this continues to help shape the game in numerous ways, the most recent example of which being achievement design. Being pretty familiar with the game myself (I’m decent at it and enjoy playing, too :P) also provides some important context for creating reasonable achievements for all skill levels. So in the end details emerge through a combination of hard data and subjective experience.

One of the things I wanted to avoid in the number department are a lot of repetitive achievements, as these aren’t very meaningful. For example there are many different types of robots, but we don’t need dozens of varieties of “destroyed 10 of this robot.” In fact there are almost none of that type of achievement except where doing so is especially interesting, as with the Giant Slayer achievement discussed earlier.


Names can be fun and in a lot of cases not perfectly descriptive of the achievement, but descriptions themselves had better be clear. These I wrote (and sometimes rewrote, on later passes) with a mind towards “what are players going to ask about this achievement?” “What’s not clear?” Once descriptions have satisfied that condition, they’re also checked for consistency of tense, grammar, style, etc. (basically what should be done with any game writing :P), and at the end I ran a spell check on the final set to ensure no typos were overlooked.


Steam achievements don’t have a wide range of functionality, but do at least support marking an unearned achievement type as “hidden,” which shows only its name and whatever icon is associated with that state. (Or on the global achievements list for a game it’ll show the achievement’s icon and name, but still no description.) This offers some interesting possibilities, so I enabled the same feature in Cogmind and in order to take proper advantage of it spent some time thinking about reasons for whether or not to hide an achievement:

  • Plot spoilers is an obvious one. There are numerous plot lines and points to explore across different runs, reaching almost any of which can be considered an achievement in itself since every single one is off the beaten path. But I’ve always been spoiler-averse, not wanting to ruin the discovery aspect of the experience, so plot-related achievements (or any others dealing with “special content,” even if not necessarily connected to the plot) are all hidden.There is one plot-related achievement, “Origins,” which is not hidden but instead given a vague description (“Discover what you really are.”) and meant to be a teaser of sorts for any new or potential players just browsing the global achievements list on Steam. It hints that there’s more to even the basic premise for the story than one might guess.
  • A handful of special achievements I wanted to hide for spoiler reasons, but doing so would make it very difficult for players to discover them so I had to keep those unhidden. In this case it’s useful to rely on a “middle ground” approach: Make the description vague enough that the average player won’t know what it refers to, but experienced players will be able to accurately guess the requirements.
  • Actions that require specific behavior which is boring to set up with the intent to earn an achievement, but otherwise fun to recognize when it happens organically, should be hidden. This goes along with the general game design principle of “don’t reward tedium.” There are only a few of these, but they’re fun :) (as I write this article Cogmind’s achievements have been in prerelease testing for a short while, and already I’ve got reports from players laughing at these)
  • While it’s fun to recognize achievements that can be earned organically, and certainly many can, sometimes where the intent is to get players to explicitly try different styles it’s best to leave them unhidden. For example the Explosive Specialist achievement from earlier would be fun if and when earned suddenly by players focusing on that style, I believe it’s more valuable to use as a suggestion for any players browsing the achievements for something they might want to aim for. (In the same vein, Gun/Cannon/Melee Specialist also remain unhidden.)
  • “The Most Popular Achievement” (an actual achievement name :P) is a special case worth discussing, as it’s quite vague and also hidden. This one, awarded on a player’s first death, has several uses. First of all it takes the sting out of a loss, pointing out that this is a normal thing that is likely going to be a frequent occurrence. It’ll also be the one achievement that anyone who plays will have, meaning it will top the Steam global achievements list--as a hidden achievement (remember that means there’s no description) this makes it kinda intriguing to potential players who open the list. As the “guaranteed achievement” it also serves as an indicator of the percentage of people who’ve actually played through a run. Unfortunately this percentage will remain low at first since a lot of owners are waiting until Cogmind is out of Beta, and too bad achievements weren’t around when a huge percentage of players tried it for a bit during the EA launch, but I’m sure we’ll be seeing more players jump back in with the Beta 6 achievements release, and of course 1.0 later, and can use that number to follow the trend.

When creating an achievements list, my approach was to “assume unhidden is the default state, what should I hide?” But another game might take the opposite route and come out with different results, i.e. hide everything and only reveal what’s absolutely necessary (or nothing at all?).

Some players might even prefer this, because then they feel less obliged to play in a specific way and either all the achievements are surprises, or any descriptions that do exist might instead just be indirect clues to figuring out what that achievement requires. This would allow for an extra sense of accomplishment on earning one, but I decided not to have any like that for now. Maybe in the future as a fun expansion, depending on how players fare with the initial batch. (Note their icons could also contain clues, or not since icons for displayed achievements before they’re earned can be non-specific.)

Of the final set of Cogmind achievements (as of Beta 6), 31.2% are hidden, exactly half of which are for plot-related reasons. Therefore 15.6%, or about one-sixth of all achievements, are hidden for one of the other reasons.


Initial hidden setting distribution for first batch of 256 achievements.


Oh my… When you’ve got 256 achievements, not only do you need good names and descriptions, but also a whole ton of icons to represent them!

At least ASCII art is fairly quick to produce, and I didn’t have a choice with the style anyway, because 1) I am not capable of producing anything else decent, and more importantly 2) all of Cogmind’s art must be CP437 in order to fit in the game (remember that Steam is the sideshow in this system--the game itself has even more achievement-related features).

I did, however, have to ensure from the start that icons would also be compatible with Steam. Their system requires 64×64 JPGs, in which I can fit up to a 5×5 grid of 12×12 pixel ASCII (12px happens to be the default size at which I draw ASCII art), so 5×5 it is.

But icons also need a border, and inserting a border into a 5×5 grid means all that’s left for content is a 3×3-cell interior! This seemed ridiculously limiting, especially for “abstract” achievements, so after coming up with the initial list of achievement ideas I went through each category and sketched about 20% of them (since each category represents a different set of concepts). It started out well enough, and wasn’t nearly as time-consuming as I’d feature it would be, either, so amazingly it actually seemed like this would work out in the long run. Limitations leading to interesting results is basically a cornerstone of Cogmind development, and this ended up no different :P

Thanks to REXPaint the drawing part was quick and easy, but it took longer to both establish the symbolism and ensure it was consistently applied throughout all of the icons. It was definitely fun working with the symbolism, and later when I started sharing batches of icons some regular players were pretty good at guessing the meanings of each, even without a description! (of course it helps greatly to have an understanding of Cogmind’s ASCII mode…) So I think the system has worked out pretty well.

In terms of productivity, as usual it helped to draw all the icons over a very short period, making it less likely I’d forget some of the symbolism and either make mistakes that would need to be discovered later, or slow down the process by having to repeatedly review such a large collection of icons before continuing.

I also drew them all in a single file to make cross-referencing as quick as possible.


Cogmind’s complete achievement icon spritesheet as it appears in REXPaint. The code knows how to extract the icons and which is which.

Looking closer at the structure of individual icons, there are two main ways to differentiate categories: border style and color scheme.

Border Style

Since nearly two-thirds (64%!) of the cells in an icon will be occupied by borders, they’d better be put to good use. Their first priority is to reflect an achievement’s category--each should have its own unique style. The most basic category has the simplest style, but decisions for other categories had to take into account another factor: how many difficulty tiers would be required within that category. Some potential border styles naturally lent themselves to a greater range of modifications, making them more suitable for multi-tiered categories.

Before starting on the icons, I first designed a large collection of different borders, seeing which looked bad, decent, or good, and which could be expanded into a natural progression of multiple tiers. It’s from that page of concepts that I’d pick the final set which best matched up with the requirements.


Achievement icon border style concepts. I generally started with an idea on the left and changed only one aspect of it for each new iteration moving to the right, or sometimes up or down if I wanted to try taking the concept in a different direction.

Higher tiers would need to look “cooler,” essentially more intricate or elaborate. I eventually settled on this arrangement:


Final Cogmind achievement icon templates by category and tier, colored.

The Wins category doesn’t use its full range as a “progression,” as it has four border styles but only two tiers. The other two borders are for special subcategories of wins, specifically the core seven different win types according to plot, and challenge mode wins, so these have a different look from the tiered “special condition wins.”

Color Scheme

Border style is not the only way to differentiate categories--each has its own base color as well (demonstrated in the above template matrix).

Colors were picked with purpose. As an “extremely Cogmind” color, green is used for one of the highest level of achievements, Wins. As a “powerful, deadly” color, red is used for the special Challenges. As a category of “basic” achievements that don’t really need to stand out, the Mechanics category uses dark amber (somewhat close to brown) as its main color. Colors for other categories were chosen for somewhat less specific reasons :)

Border colors for the templates are all dark, at 25% brightness (and backgrounds are even darker at 12%), but each category also has a base foreground color (100% brightness in the same shade) used for generic content like numbers. This way the numbers, as secondary bits of information, are somewhat connected to the category and background/border itself, at least more so than most other elements that make up the interior.


A sample of Style category icons with generic number components highlighted.

Most foreground characters are all quite bright as well (usually 70-100%), so while the border and background colors serve a supporting and informational role, they don’t take over the entire icon.

As for icon interiors, colors used there are drawn from Cogmind’s ASCII mode where possible, although in some cases alternatives were needed where a concept is not already associated with some specific color (sometimes required for abstract icons). Again though, in all cases colors were chosen with purpose, and where a concept is repeated across multiple icons those colors are applied consistently.

Locked (Unachieved) Icons

Locked achievements need a display icon as well, and there are about three ways to handle them:

  • Use a grayscale or muted/darkened version of the unlocked icon. Most games seem to handle it this way, and it’s the recommendation from Valve.
  • Use the same icon to represent any locked achievement. This is a lot less common, but some games do it. I guess it has the advantage of making the actual icon part of the surprise/reward on achieving it. Hiding the icon contents also removes yet another clue as to what a hidden achievement might be referring to, becoming a truly hidden achievement aside from whatever information is suggested by the name alone.
  • With enough achievements to divide them into categories, a separate icon can be used for each category, but used across all achievements in that category. I went with this approach to further emphasize the categorical nature, and because it helps break up what would otherwise be a huge mass of identical icons if I went with the second method above. (For the same reason I don’t like the idea of grayscale versions--too much information value is lost when this many achievements are at play.)

Locked achievement icons.

Note that locked icons also reflect the relevant tier--essentially these icons are equivalent to the templates, with the interior replaced by dark question marks.

As for those PNGs, they are exported from the game via debug command in order to convert them from the internal format and assign proper file names. This isn’t necessary for the default DRM-free version, but again Steam requires that achievement icons be 1) JPGs, and 2) 64×64. So I created a tool to output all icons, then use Photoshop to batch convert from PNG to JPG while also adding a 2-pixel black border around each (since in Cogmind their dimension is 60×60).


256 Cogmind achievement icons, exported as individual PNGs.


We’ve got names! Details! Descriptions! Even icons! But… achievements also need to actually make their way into the game :P

Once all the data and resources were defined and ready, next came the code and systems.

On an individual level each achievement is pretty straightforward to implement, being a quick check for the condition and corresponding call to a method to assign it if applicable. This process was made even easier by the fact (mentioned earlier) that a fair number of achievements are based on the existing score sheet data, which itself already tracks many hundreds of conditions and stats throughout a run. Implementing a related achievement could take as little as a minute or less since I don’t have to search around for or confirm the right location in the source--just ctrl-f for the appropriate stat name!

Of course some achievements required new stats that I hadn’t been tracking, so throughout this process I also ended up expanding score sheets by several dozen entries where it would help. In yet other cases some achievements required whole new internal variables to track special conditions in more complicated situations, basically those which had to be confirmed at more than one point in time to award.

Note that most games will actually use Steamworks’ stats system for this kind of thing, but Cogmind has its own internal stats system so I could more readily use that, plus I wanted non-Steam Cogmind to fully support achievements as well, so relying on Steam for any help wasn’t an option anyway.


Checking the internal stat value for whether to attempt to award the Assassin achievement (“Sneak attack 15 hostiles.”).

The above code doesn’t do any heavy lifting because control should naturally be as centralized as possible to make any potential changes easier to implement down the line. So additional generic checks and the actual achievement award itself are handled by that single earnAchievement() method:


Generic code for handling achievement application.

For now I’ve decided to not hand out achievements to brand new players, to help them focus on the tutorial messages and avoid overwhelming them with even more information in an already daunting interface.

I was originally thinking of ways to save on development time throughout all this, and seeing as a lot of the achievements were so straightforward, one of the possibilities was to… skip testing. Nope--too difficult to go against my standard practice of manually testing every little feature, so I tested all 256, too xD

Only a tiny percentage didn’t work as implemented, but it’s better to make sure they do rather than have so many players scratching their heads, or reporting bugs I could’ve easily found on my own. Setting up testing conditions was extremely fast with debugging commands anyway.

The final step was to integrate achievement data into score sheets as well, which I did in three areas.

Like gallery collection and lore percentage, at the bottom of the sheet in the section for general game data there’s a new “Achievement%” which keeps a running tally of the total number of achievements earned so far, out of 256.


Cumulative achievement progress in a Beta 6 score sheet (recorded from one of the prerelease testers’ runs).

Like the other two, this percentage is a fun and useful indicator of overall progress.

There’s also the full list of achievements earned for the first time specifically on that run.


An achievement list as it appears in a score sheet.

And although it’s possible to count the number of achievements in that list to get a total, the tally for the run also appears as its own entry in number form with the regular stats. This is more convenient for players looking for a quick count, and also for me when I run the data analysis since no extra work is needed to extract the number of achievements while analyzing global stats.

The final feature tacked on at the end is a way for players to reset all their achievement progress for whatever reason (without losing their other meta data in the process). It’s a text-only advanced config option, but unlike other options this one is only discussed in the manual, not even listed in the config file itself, because players had really better be sure they want to do this and not accidentally trigger it. Manually adding “resetAchievements=1” to the file will tell Cogmind when it next starts up to erase all achievements.

I’m glad all this achievement work was handled late in development, i.e. after the core game content and features were completed, because it would’ve been much more likely for achievements to become a disorganized mess over time if it was added too early.

And I’m happy with the results--there’s something for every skill level, and players appreciate them. Achievements are a great high-value meta feature (so yeah, no surprise that lots of games offer them, and Valve highly recommends adding them, too).

And that’s it! Next up is another piece on how to provide ways for players to monitor and learn about their achievements, and hook everything up to Steam…

This entry was posted in Design and tagged , , . Bookmark the permalink. Trackbacks are closed, but you can post a comment.

Post a Comment

Your email is never published nor shared. Only the anti-spam entry is required. See here for the privacy policy.

You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>