Official development blog

Pricing a Roguelike

2 Flares Filament.io Made with Flare More Info'> 2 Flares ×

Price, funding, revenue, development costs… these are not terms traditionally associated with roguelikes. The situation has changed significantly over the past several years, though. Not only are there many more roguelikes these days, but some of them (*gasp*) even cost real money!

Having made the leap from years of hobbydev to years of commercial roguelikedev, I have some thoughts and experiences to share on the somewhat contentious idea of raising money for a roguelike, and pricing strategies in general. Although I write in terms of roguelikes, most of the same principles can be applied to other genres as well.

In short, Cogmind’s approach to pricing has worked out perfectly, initially meeting my expectations, and then before long exceeded them. Repeatedly.

Why Pay for a Roguelike?

Before I get into examples, the short answer is that money makes more things possible. Who doesn’t want even more higher quality games from their favorite genre?

As for specifically what money can do for roguelikes, not too long ago on the Cataclysm: Dark Days Ahead forum a relevant thread popped up.

cdda_forums_ui_improvements_discussion

Excerpts from a discussion on C:DDA UI development.

You see this a lot in roguelike development, where accessibility and UI features are an afterthought. That’s not to say they aren’t important, nor would many developers make such a claim, but it is widely considered a less enjoyable part of creating a roguelike. Roguelikes are all about adding new mechanics and content--heck, rapid feature development is one of ASCII’s strong suits to begin with! UI work requires yet more time (on top of all the other things RL dev entails) in a very different area of expertise.

Kevin (C:DDA developer) at the end there makes the point well: Hobby projects are more about what the dev wants to do. I can say from experience that after having switched from hobby to commercial development, the focus shifts towards a lot of what the dev should/must do. Sure there’s still the fun stuff--the new mechanics, new map generators, finding new and exciting ways to killchallenge players… but I also spend plenty of time doing things I don’t necessarily feel like doing.

You know, like most any other job that pays :P

A developer charging money for a game has an obligation to serve the player wherever possible, and that means devoting proper attention and resources to usability. Note that this in no way implies sacrificing creative control, it just means treating the project as a proper business--taking feedback, interacting with players (who double as customers), and providing customer service. As such, accessibility features have a much higher priority for me, which a lot of players appreciate.

Players get so much more than that, though. Increased production value and quality make up the bulk of obvious benefits from paid roguelikes. Being able to invest extra time or money means:

  • Extensive professional tilesets of a consistent quality and style. ADOM currently has over 6,000 tiles; ToME4 has a mind-boggling total north of 20,000; Caves of Qud has upwards of 5,000; Cogmind has 1,165 (plus over a hundred custom font bitmaps, a thousand pieces of ASCII art, and many hundreds of procedural animations). And because they’re all in development, these totals are still increasing as time goes by! (It’s early yet for DoomRL successor Jupiter Hell, but with all those 3D assets it’s in a league of its own and certainly not happening without funding! (already acquired through KS))
  • Sound effects aren’t something that a lot of roguelikes do--that’s mostly roguelite territory, but Cogmind has made it a big part of the experience with over a thousand samples and counting (far more than any other roguelike and most other indie games).
  • Music. Some roguelikes do this, too! (Still to write: my own article on that topic. Posted!)

Certainly plenty of perfectly good roguelikes have none of these things, but many of the more widely popular ones do, not to mention the potentially long stretches with no fixes for bugs reported in non-commercial roguelikes.

Optional elements aside, considering the time-intensive nature of roguelike development, simply having more time to dedicate to new features is a big thing. A revenue stream enables continuous development, much more desirable than the sporadic updates endemic to hobbyist gamedev (for which the ARRP was a somewhat successful attempt to remedy, but still can’t compare to directly funding the process!).

Development on Ultima Ratio Regum, an amazing free roguelike project started in 2011 but only about half done by now, was unexpectedly halted for some months shortly before a planned release last year. Mark is now back at it again, but a number of other roguelikes have died or faded out over the years before reaching completion. Pure hobby projects tend to progress more slowly, and therefore stand a greater and greater chance of dying as time goes on. It’s just a fact of life, in which any number of causes can spell the end of (or at least interrupt) development, be it family, studies, work, a change of interests, or “a bigger better idea!!1″ :). From that perspective, means to accelerate progress are a good thing (and of course for their part players won’t complain about access to more timely updates!).

Honestly it’s a huge amount of pressure to keep up that near-nonstop progress, but the ability to (relatively speaking) quickly and efficiently put together a world that others can enjoy is worth it.

cogmind_development_hours_cumulative

Cogmind cumulative development hours, 2013.6-2017.1.

As an experiment, let’s look at the hours I’ve put into Cogmind as of this writing (6,623) in a different light: What if this were a hobby project done in my spare time? Excluding basic needs and all other responsibilities, based on years of data I generally have about 50 hours to spare each week for work (all of which currently goes towards Cogmind). Assuming I use up 40 of that for a different job and develop purely as a hobby instead, and also making the big assumption that doing this other job wouldn’t leave me even more exhausted and desiring extra time to relax and get away from brain-draining activities (it would), that leaves 10 hours per week… 6,623 h / 10 h/wk = 662.3 weeks, or 12.7 years!

So rather than Cogmind being what it is today in January 2017, having started as a hobby back at the original date of June 2013 it would not reach its current state until July 2025. Sure we could chop off a year or two because, yes, I might spend vacation time working as well (though we’d also have to cut out the occasional weeks where I’d be too busy with other life stuff)--anyway, it’s a generalization, but no matter how you look at it that’s still terribly slow.

Then of course there’s the fact that it’s not done yet :P. I can say for sure that including post-1.0 work it’ll easily top 8,000 hours (beyond that I don’t really know).

In the end, most roguelikes and features are technically possible without any funding whatsoever, but it’s going to take a lot longer (which, again, increases the chance of failure), or a lot of manpower (DCSS is a good, if rare, example there).

Why $30? Balancing Price with Other Factors

Although as I write this alpha access is available for $25, in 2015 Cogmind was introduced at $30, the price at which it remained for the entire first year of public alpha. As you would expect, reactions to this number ran the entire spectrum from “for an alpha?!?!?” to “totally happy to pay that!”

I based the specific number on a couple data points, first and foremost what I’d noticed from video game Kickstarter campaigns, that early access as a “perk” often came with tiers upwards of $30. Even outside KS, I found games like RimWorld, similarly a highly-replayable game under long-term alpha development at a good pace by a very active dev, which priced its alpha access at $30.

Overall it felt like a plausible range was somewhere around $20-$30. I would definitely not claim this approach is good for maximizing revenue potential, or even maximizing players while still bringing in “sufficient” revenue, but that wasn’t the goal!

graph-elastic-demand

Graph demonstrating the concept of elastic demand (source). Video game demand is pretty darned elastic!

It’s fairly obvious that a lower price point might very well outsell the current sales model in terms of total revenue, but to me there are more important factors than money to consider in the short term. The point of alpha funding is to keep development humming along until 1.0, before which too many players actually becomes a problem!

While not necessarily true of all devs, I believe in the importance of being active in the community, responding to everyone with a concern, question, or some other need of support, while also putting effort into making resources, extensive progress updates, and other information available outside the game. This requires a significant time investment, the effects of which are even more pronounced as a lone developer where talking to players means I’m not making real progress on the game itself.

Lower prices naturally attract more players, which given this community-oriented model will inevitably slow development as more and more time is spent on community management. But I love having the opportunity to maintain closer relations with a smaller player base, even adding custom options at the request of a single player, while still having plenty of time to work on the next release. So in this regard a higher price is beneficial for both development and the ongoing alpha player experience.

Game development is also incredibly risky, so it’s nice to use any knowns to mitigate elements of risk wherever possible. This, too, played a role in the original pricing decisions, which you can see below from my general thought process:

  • I do know that I have an established fan base who would be willing to pay more for a quality roguelike with quality continuous development and support.
  • I don’t know whether lowering the price to something more common across the entire indie market (like <=$10) would be able to attract enough players to even make up the difference. But I do know that even if it could, having 2-3 times as many players would be a larger burden on the process and unnecessarily slow development. The resulting “high noise-to-signal ratio” also makes it harder to focus on the best design decisions.
  • Niche games, especially those with something truly unique to offer, can afford to charge more, and in many cases must charge more in order to be at all sustainable. Long-term sustainability is quite important to me, since this isn’t a one-off thing and I hope to not only develop it further beyond 1.0, but also work on other games as well. It’s (hopefully) a permanent job.

In that light, a $30 price point seemed the much safer route.

From a purely economic standpoint, where time is not a limiting factor (i.e. development and support can and will continue for quite a while), setting a higher price is also just smart business. Eldiran over on /r/gamedev (where especially when starting out I read a lot of first-hand industry info that was very helpful) put it very well in response to a question about how discounts damage indie sales:

Different players value your game differently. Hardcore fans want to buy it as soon as possible at full price. Some genre fans might be willing to grab it once it hits 10-20% off. People who are only mildly interested might wait for a 50% sale. And so on.

If you set up a 50% sale early on, all of those groups will buy it for 50%. That means you lost all the extra money you could have gotten from the 10% group, the 30% group, etc.

There are lots of other considerations. Consider what it looks like as a buyer to see a game go 50% or 75% off shortly after release. That would look like the developer isn’t confident in the quality of their game. Maybe they’re just trying make a quick buck with manipulative sales, and the game sucks?

That said, there are situations where getting a big playerbase as fast as possible is more important, such as for multiplayer-only games. Then it might be worth it to do sales early and often.

The comment is in reference to sales, but the same principles apply to pre-release pricing as well.

It’s not purely a numbers game, though--the price is still very much associated with potential value. Subjectively speaking, I consider Cogmind worth that price if I were a player looking at such a game, and clearly many others agree. Everyone else can make that call for themselves based on the large amounts of information available, while a higher price serves a useful secondary purpose here: prevent impulse buys. Impulse buys, which are where a lot of developers can expect to bring in more players via low prices and steep discounts, are also where a lot of the noise-to-signal problems mentioned earlier come from. It leads to too many distracting, non-constructive comments from players who probably haven’t spent very long with the game in the first place. (Not to say first impressions aren’t important, too, but they shouldn’t make up the bulk of the discussion.)

Side note: A great tool for games with a higher alpha price is a one-time mailing list for those who wish to be notified when the game comes down to its regular price. Over 1,000 people have signed up for that already. This is essentially akin to the Steam wishlist, albeit without the Steam part :P

A pricing discussion wouldn’t be complete without a look at the common argument for a lower price before full release: Players may very well be playing an unfinished, buggy version that’s not necessarily all that much fun, where a higher price equates to paying a premium to help find and report bugs! (That sounds like work…) I completely agree with that argument, though I would also argue that developers need to try to release early versions that are not so buggy, and fun from the start. Then it suddenly becomes more of a privilege to join the alpha process, where those players are not only having fun, but can also influence the future direction of the game via their feedback.

This is how I handled Cogmind--sure there have been bugs, but a relatively tiny number, nor is it usually anything serious (most serious bugs are discovered via automated testing prior to updates, and those which aren’t are patched immediately, generally within an hour of reporting). Fixing bugs is always a top priority, and even the original 7DRL is fun so that aspect is covered, hence the overall player consensus that “it doesn’t feel like an alpha,” which is exactly the kind of sentiment that is important to lay the foundation for by building a quality pre-alpha in the first place.

Yet another advantage of a higher alpha price is a factor many non-developers may not realize: while in early access and not on Steam I can devote a lot more of the revenue to actual development, whereas on Steam a majority of the funds would go to Valve (30% fee) and the US government (taxes…), and they’re certainly not going to help make Cogmind better! :P So each individual person supporting my work at this stage has been far more valuable to the project than even a handful of supporters on Steam could be, and the results are amplified with a higher price, all while keeping the player base to a manageable size. (Clarification: Steam is definitely a valuable channel in the long term, as it provides access to a much larger pool of players--so many only buy through Steam!--but given the context it’s not the right choice for me at this time. That said, in the interest of sustainability the amount of post-1.0 work will be mostly contingent on how successful Cogmind is on Steam.)

Getting Results

Cogmind Alpha Access has been quite successful, my definition being that it’s been able to fund itself. And that’s with just the right amount of feedback from players to help improve the design without causing too much of a drag on the process.

Revenue has been both relatively steady and just enough to keep development going. In fact, the process has been going so smoothly that the original plan to “finish” by the end of 2015 was quickly scrapped in favor of another year of developing extra features, which became yet another year of decent revenue that pushed the intended deadline into 2017. Sure, development could’ve been rushed to the planned 1.0 over a year ago, but there were/are so many tempting optional features, and many new players have come to support this project, so why not add more fun stuff? :D (For the curious, a sampling of the features so far that could only be added as a result of strong alpha support: traps, Trojans, Waste, garrisons, Zionite plot line, about 15% of the items, numerous additional robot designs, countless extra UI features, large-scale refinement of mechanics like hacking, machines, and flight…)

Since Cogmind was available at more than one price when alpha access began (an idea inherited from Kickstarter but without the temporary campaign nature), let’s look at the reasoning and performance of each of the tiers.

  • $90. While as a sum this highest tier seems expensive, it included multiple keys at essentially $22 each, or $15 if you subtract the value of the t-shirt thrown in. This whole tier was just something I wanted to do because having a custom t-shirt is neat, and 18 other people liked the idea, too :) (only available during the first month, though since then there have been numerous requests to bring back the t-shirt, so I’ve been taking names and will do that at some point).
  • $60. I can’t take credit for this idea, which turned out to be a really nice one indirectly suggested by sambojin over on the Bay 12 forums, who shortly before launch said he hoped for a way to buy more than one key, preferably at a discount, to give the others away. That sounded like a perfectly reasonable request, thus the Improved Tier was born and to this day 9.7% of all revenue falls into this tier. And it’s not only for gifting, either, as multiple supporters can pool their money and buy this 3-pack which breaks down to $20 each. Especially soon after the launch period it was possible to see such groups forming on various forums among friends. There are multiple advantages here, including a bit of free marketing while also giving those who couldn’t afford $30 a way to acquire it at a 33% discount. I also made sure to clearly indicate that $20 is the intended launch price for 1.0 (it always has been). Managing expectations is an important part of pricing!
  • $30. This one was already covered pretty well. It accounts for 85.6% of revenue in the first year, before the next tier was introduced.
  • $25. When the first anniversary of Alpha Access rolled around (May 2016), sales seemed to be in an ever-so-gradual decline, thus it was a perfect opportunity to introduce the first price drop. It was nice to have that middle-ground leeway in between what it was and the future launch price, enough to make a difference to buyers but still be a respectable amount of revenue without opening the flood gates to new players. As expected, sales picked up again, and have continued at a good pace ever since.
  • $20? More recently I’ve taken to offering the occasional 20% discount coupon in coordination with other events. These are neat since I can see precisely how much a lower price stimulates real buying interest coming from various sources by using different coupon codes for each.
cogmind_buy_tiers_alpha_summary

Summary of Cogmind Alpha Access Tiers, 2016.

Note that even in introducing the $25 tier, I did not remove the $30 tier. It’s still available as it offers a few perks that don’t come with the new lowest tier, just a thank you in the credits and a forum badge. And despite the availability of $25 access, some people still go for $30! From May 19, 2016, to date, the $30 tier still accounted for 14.1% of individual sales (15.9% of revenue). Had the same group of people instead only had the $25 option, gross revenue would have simply been $795 less. Not providing ways for individuals to offer extra support when they have both the means and desire is so-called “leaving money on the table.” And when I see that during alpha dev it means “leaving features on the table, too” :P

cogmind_monthly_revenue_gross_1509-1612

Cogmind Monthly Revenue (Gross), 2015.9 -- 2016.12 (graph excludes initial 4-month period after first release due to distortion by outside factors)

While there are too many factors involved to draw sweeping conclusions, it’s probably safe to say that lowering the price in May didn’t hurt the bottom line. Compared to the period before, when the lowest price was $30, average monthly revenue rose 13.9% from $2,478 to to $2,823. The latter average excludes October, which was a weird month because it was Cogmind’s largest-ever update combined with a little surprise article from RPS. In fact, October, November, and January were three consecutive “largest ever” releases (January’s not quite done so I couldn’t include that data, but it looks like it could break $4k alone).

Actually, we can do better than this with a comparison of averages from just the few months before and after May. February through April (plus the first half of May) sales were showing clear signs of flagging (monthly average: $1,927), while in the four and a half months after adding the new tier (through September, before things started getting crazier) the average increased 45.3% to $2,799. Looking at it that way, the change had a larger impact than I’d realized! A more detailed look at the difference between the 15 days before and after May 19th is equally telling:

cogmind_daily_revenue_160505-160605

Cogmind Daily Revenue, May 5 -- June 5 (2016)

During the months leading into early May I was getting kinda worried because I’d definitely have to wrap up development more quickly if that trend kept up (see those two zero days?! Scary!). But the new price put alpha back on a healthier long-term feature-filled schedule. The one-year anniversary turned out to be an excellent opportunity used well.

Update 170614: For additional stats and analysis on how pricing and other factors affected sales, see my more recent Year 2 financial overview for Cogmind.

Changing Times

Indie devs in general tend to undervalue their games, though it’s nice to see that a growing number of devs aren’t afraid to charge a (minimally) decent price for paid roguelikes. Caves of Qud is only $9.99 for early access, but will reportedly rise to $14.99 at full release; both Ancient Domains of Mystery and Dungeonmans are $14.99; Jupiter Hell is aiming for $30-ish… It’s necessary if we want this quality and pace to be sustainable.

Those graphs and numbers look pretty, but they’re not much compared to the amount of hours and money that I put into development, or what I can make in another line of work (it’s also gross revenue, not net!). Other devs are in similar situations. The genre is relatively niche, after all, and based on publicly available Steam data the above released games only have somewhere around 20-25k players each, so it’s been heartening to see the core community repeatedly coming out in support of paid roguelikes over the past couple years.

Roguelikes especially, with near infinite replayability and near endless development cycles (those games have been putting out updates for years), are just the kind of high value-to-cost ratio games that both warrant and can benefit from higher prices in the long-term.

As for my own future plans for Cogmind pricing, 1.0 will be released at $19.99, with no plans to do any significant sales for a long while as I continue updating with extra features (I hear this echoed by several other devs as well). Of course once on Steam, players in certain regions will have access to lower regional prices. Steam changes a lot of things by introducing its own many variables, so it was interesting to be able to take this somewhat more “pure” look at revenue and pricing data before it gets that much more exposure.

 

Good Luck

To the devs reading this, do remember that every genregame is different, and there are other very different yet equally successful models out there, too. Dwarf Fortress, UnReal World, and Tales of Maj-Eyal, for example, are all widely-popular free roguelikes that exist on purely donation-based systems (with full-time devs!), or offer some extra perks to supporters. My pricing decisions came out of what I felt could work for Cogmind based on lots of research and also consideration of my personal circumstances and experiences.

Oh, and I’m sure there’s gotta be some luck in there, too ;)

2 Flares Twitter 0 Facebook 0 Google+ 2 Reddit 0 StumbleUpon 0 Filament.io Made with Flare More Info'> 2 Flares ×
This entry was posted in Gamedev, Marketing and tagged , , , , , . Bookmark the permalink. Trackbacks are closed, but you can post a comment.

12 Comments

  1. lsend
    Posted January 27, 2017 at 7:04 pm | Permalink

    Hey, that’s very interesting. Do you have any thoughts on the usefulness of free demo/trial versions? Did you consider releasing such version?
    Personally, it would have been easier for me to decide to pay for alpha access if I could check it for free. I know there is a 7DRL version, but it is hardly comparable.
    Anyway, it took me about a month to make up my mind. I finally joined the alpha in November 2016 and do not regret it. But maybe there are lots of potential players who are still not sure?

    • Kyzrati
      Posted January 27, 2017 at 7:43 pm | Permalink

      Quite true, demos are one of the many potential subtopics I didn’t touch upon in this article. It’s certainly something I’ve put a lot of thought into over the years, though.

      I don’t currently plan to release a demo, most of the business and marketing reasons for which are summed up pretty well in this Extra Credits video. From so many different angles it simply doesn’t make a lot of sense to do so.

      While I grew up in an age where demos were the norm, and thus my first instinct was to offer one (not to mention the traditional roguelike standard of having free access to the entire genre), games in general have really shifted away from that model. There is so much information available out there these days, with everyone streaming, publishing on YouTube, writing review after review… (And then of course there is now Steam where refunds are pretty easy and people might use that approach as a makeshift demo.) I find that it’s pretty easy to get a feel for whether something will be enjoyable or not before buying, and whether a game is worth it or not in the long run is often something that can’t be determined from simply playing a demo anyway, for which it’s best to research the opinions of those who have played longer, probably with more experiences regarding content not reflected by a demo.

      My ideal approach for a demo would be content which is completely separate from the regular game itself, instead telling a different part of the story. A few other games have done this, and I would love to be able to as well, but it’s a lot of extra work that could be put towards the core game itself, and there is so much extra overhead to creating something like that.

      If I had infinite time I’d love to do this, but as a solo indie I can only put so much time and effort into each aspect of development :/

      • Posted January 30, 2017 at 3:10 pm | Permalink

        I found the 7DRL version worked for me as a demo. I played several runs on that for about a month before making my purchase, and while the 7DRL is certainly far less polished than the full game, it does provide a way to mess around with the unique mechanics of Cogmind for free, especially the inventory and equipment system.

        • Kyzrati
          Posted January 30, 2017 at 3:22 pm | Permalink

          Yeah I’ve found it’s definitely sufficient for some people (the idea being that “if you even just like this, you’re going to love the full game” :P), though as a 7DRL, and one meant really just for the core roguelike community, the first few runs might be really tough for some players to get through, not the kind of experience you want with a real demo!

          Back when I was designing it, it was intended as kind of a joke that at the beginning of the game you are immediately dropped into a little square room full of letters and nothing seems to make sense. Sure there’s a command list screen and extensive manual etc., but no kind of tutorial to ease the player into it. It hits you with everything at once :D

          That would be its primary drawback with respect to serving as a demo, otherwise it does a pretty good job since the core mechanic and gameplay are all there. But a hypothetical demo wouldn’t really be targeted at regular roguelike players, since they can pretty clearly see the value. More important would be the ability to use it as a tool to convince those who aren’t really sure what they’re looking at. Audience is important, and that particular audience needs a little more hand-holding.

  2. martin
    Posted February 2, 2017 at 10:34 pm | Permalink

    You know you lure me in finally. I love the game. Keep up the great work.
    This game is worth every penny.

    • Kyzrati
      Posted February 3, 2017 at 9:00 am | Permalink

      Heh, thank you, and sorry that it has gone on so long but my original plans to rush 1.0 out about a year ago just made less and less sense with all this support, which is still continuing. I’m tempted to put another year of work in to make it even better, but I guess it also makes sense to at least first declare a 1.0 at the big “story complete” milestone, then continue from there. (So much more I want to do with it!) In the meantime, plenty of followers have said “waiting for 1.0… waiting… waiting…” and then finally give in :P

  3. Posted February 16, 2017 at 5:04 pm | Permalink

    Hey Kyzrati,

    I’m a silent fan and reader of your blog (plus alpha player of course) and just want to say thank you for all your blogging. It’s incredible valuable information for devs like me and players as well. Plus I totally enjoy your style of writing. :)

    Keep it going, I wish you maximum success!

    • Kyzrati
      Posted February 16, 2017 at 6:35 pm | Permalink

      Hello silent fan and reader Xaron :)

      Very happy to be sharing my experiences! Regarding style, it’s funny because one of the WordPress plugins has a little indicator rating the language quality of each post, and every single one has always shown a yellow light with a reason stating something along the lines of too many complex sentence structures. I’m like… whatever that’s how I prefer to write, heh.

      Thank you for reading, and with success will come… more blog posts! (okay, I’d almost certainly blog about failure, too :P)

      • Posted February 16, 2017 at 9:42 pm | Permalink

        Haha cool! :)

        So you use WordPress? What a beautiful theme you’ve here! Have you done it by yourself?

        • Kyzrati
          Posted February 16, 2017 at 9:47 pm | Permalink

          Yeah I did all the design work myself, but the core code/functionality was based on the Thematic template. Highly recommended!

          • Xaron
            Posted February 17, 2017 at 3:12 am | Permalink

            Thank you! Actually you are one of the rare guys out there who can not only code but also doing artwork AND can write as well. Personally I can only code but hey… at least. ;)

          • Kyzrati
            Posted February 17, 2017 at 11:03 am | Permalink

            Meh, just a jack of all trades, really, but no master! I still wish I could compose music :P (I’ve tried several times, but lack the required time to invest…)

Post a Comment

Your email is never published nor shared.

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=""> <strike> <strong>