The success bias & (lack of) prototype
We spent a good year with the paper prototype of Gremlins, Inc. before we went into production, but we completely forgot about it.
When we started the production of Spire of Sorcery, we felt we had “the touch” - we just needed to produce the game and ship it. Prototyping is for people who couldn’t make their first game work! That success bias alone cost us 2 years of development.
Our basic advice to avoid this would be to talk to other developers… but the thing is, we did that. It’s just that when you’re successful with one game, you tend to ignore all the comments that you don’t like, even if you get the good ones.
So a more solid advice would be to – regardless of whether you need it or not – pitch the second game to a publisher/investor. These people, being asked to give money, will ask all the same questions, but you won’t be able to wave them off!
Essentially, if you’d have asked me in 2018 about the gameplay of Spire of Sorcery, I would only give you either a description of the world, or a list of features, but not the actual core loop and flow. And anyone giving me money would have stopped right there and demanded a properly structured vertical slice or GDD.
A paid Beta on Steam?
By the end of 2019, we wanted to get the game into the hands of our players. The advice from Subset Games to engage your players as early as you can is truly great!
However, Steam didn’t have the current “keyless play test” feature back then. So we considered either a) sending out keys (like on Gremlins, Inc.) – but only 50% of recipients activated them, and only 10% provided meaningful feedback – or b) releasing as a paid Beta in Early Access as an unlisted page, which is what some studios did at that time. (You cannot find the game on Steam, but if you have the URL, it shows up and you can buy it.)
The latter is what we ended up doing. And looking back, our advice to others is not to do this. On the good side, we got 2.000 very engaged players who paid €20 to access the beta. It was a very valuable audience, filtered by preference and validated by purchase!
On the bad side, you may run into problems during beta, and may need to change the game significantly. And if you do this… some of the early adopters will get very angry with you.
No amount of disclosures (“this game may change”, “please refund if you’re trying to buy a finished product”, etc.) will help here. Just don’t risk, because if you will need to change core features, you’ll be ‘between two apps’.
So, about ‘between two apps’?
We still have to meet someone who succeeded in transitioning between two apps that are different versions of the same game.
There’s enough cases, actually, once you start looking, of games that didn’t work in EA, and got canned, with the developer opening a new version of the game as a new app. In all of these cases, there’s a bit of an angry mob coming at the team “BUT YOU PROMISED US ANOTHER GAAAAAAAAME!!!”
Generally, we think you should take money only when the game is set on its course. Early, sure. Super early, sure. But if your core loop is still evolving… or might need to change… God save you from running two apps.
Some memories are short…
Time is a subjective matter, and that’s evident when you talk to some players. We all, I’m sure, know games that were announced in 2019, where players say “they’ve been in development for 10 years!!”
After our unlisted beta on Steam at the end of 2019, we announced that we changed the concept in 2020, and then spent the whole of 2021 building the new version. To us, it was a super-intensive sprint for 12 months, with weekly builds and weekly dev updates.
This did not prevent some people in the community saying “this is unexpected” (despite detailed explanations), “this is surprising” (despite 30 dev diaries) and, the best, writing in 2021 that “I played a different game just a couple of months ago” – referring to the build from 2 years (!) earlier.
Our advice here is same as the advice from many other studios: only announce the sequels, because there early exposure provides feedback via detailed expectations. But for an experimental game, each year that you develop it in public is 3x years in the minds of some of the players. So when you ship after, say, 2 years, they would think “ah, this is a game that was baked for 6 years, must be HUGE!!”.
Releasing without an interactive tutorial!
We did this with Gremlins, Inc. and we took some harsh criticism, and built the interactive tutorial post-release, back in 2015.
We forgot about it by 2021 (same dev team! 1:1!) and shipped Spire of Sorcery also without an interactive tutorial, and again we took harsh criticism, and added it with the first big update.
Advice: do not, I repeat, DO NOT ship games in Early Access without an interactive tutorial.
Early Access launch with tech bugs?
We kept developing the launch build of Spire Of Sorcery until 12 hours before release. As it happens, we shipped the game with some tech bugs. Even though we fixed them in 48 hours, we caught a number of refunds and bad reviews just based on that (“cannot complete the game”).
Advice: if you can afford it… take a week to fix game-breaking bugs before you ship. Though in some cases, this advice is like “eat well” to a person who only has yesterday’s sad sandwich at their disposal.
Two games, one release…
We reached Early Access on Spire Of Sorcery with 80.000 wishlists, on the back of pretty huge demand for the unlisted beta back in 2019. You see, in 2018-2019, we ran weekly dev diaries, and commanded quite a lot of attention. In our minds, we were still there. And thus we also shipped at €20, without any discounts.
The reality, though, was that we ‘only’ had 24.000 wishlists from the year of 2021, when the game already had its current concept, and that previous result was for a different concept.
We also didn’t have the time for regular dev communication in the months up to EA release. So when shipping an under-promoted game with 24K wishlists, we actually thought that we were shipping an 80K wishlist highly desirable product. We thought we will sell “at least 10% of wishlists” in Week 1. Our actual sales during launch week: less than 1,500 copies.
Basically, we had “Spire of Sorcery” (2017-2019) and, let’s call it, “The Wild Mages” (2020-2021) games, which were publicly conflated as one game, Spire of Sorcery, which complicated matters on every goddamn level in communication. Should we actually have renamed the game? We don’t have an answer for that, so cannot advise anything to others.
Unbundling the situation
Examining things post-EA release, we ended up with badly mixed reviews (50-60% positive) that were made of 2 groups:
- positives from people who discovered the game in 2021 – and who tried the demo before purchasing
- negatives from *some* people who bought another concept in 2017-2019, and were Very Unhappy with the change of the core mechanics.
At one point we wanted to see if the owners of unlisted beta were the ones who wrote negative reviews, but it wasn’t the case. Some people wishlisted in 2018, bought the game without checking in 2021, and were very unhappy. And some bought the game in 2019, attached us change the concept, and actually really enjoyed the 2021 edition.
Our action plan: monthly updates addressing the most impactful items, as per community discussions, combined with discount sales that trigger wishlists. We released a big update in November, and another in December. The next one is coming at the end of January.
We added a feedback form to the demo, asking about what people like and what they dislike, to get actual, clear feedback from the source - and it helps a lot. We see that the people who like the concept love the original mechanics. And the people who hate the concept, hate pretty much everything – from UI to art direction and the core flow. And so we’re focusing on making happy players even happier.
With each update, our sales are picking up. And our Steam announcement news posts went from 50 to 100+ thumbs up, which is pretty great when compared to the (still not high) sales.
We think the Mixed review rating impairs the sales, of course, but also works as a sort of a filter: you only buy a 65% rated game when you’ve tried the demo, and liked it, so we’re selling to the audience that is much more likely to enjoy what we produce.
Conclusion: going forward, and our takeaway
We’re currently set to finish the game and ship full release in about 4 to 6 months. As we develop and ship monthly updates, we’re also talking to publishers to see if we can sign up with a partner and access a big bigger budget, plus get an experienced producer to take a look at the game and help us align the priorities.
We think we have a pretty awesome original mechanics on our hands, and a setting and theme (spellcasting) that makes people excited, so we’re on the right path. How soon we reach full release and how much content we can throw in there, right now depends on a bunch of external factors.
Our takeaway for others would be:
- try to avoid success bias, by keeping in mind that a lot of dev teams crash with their 2nd game after seeing the 1st succeed.
- get someone external, wearing an investor/publisher hat (real or imaginary), to review your new game and ask the hard questions
- do not announce your game before your core loop is complete and you enjoy it and are willing to “marry it”.
- do not run paid Betas as unlisted apps - use keyless playtest instead. This will save your reviews big-time.
- weekly dev diaries work really well, especially in multiple languages; use this tool to build your audience
Generally, if you have a good game in X genre, build what’s strong to become even stronger. AND if so you desire… invent Y in the background, treating it like a new startup, rather than as a guaranteed success.
We think this story will end well, with the game getting its release and all the recent wishlists converting (people play the demo, like demo, and our wishlists keep growing). But the price we paid, and are paying, is so steep that we do not wish this onto anyone else. Having said that, if you showed this article to me in 2018, I’d probably ignore most of the advice. So let me try to focus on just 1 thing:
Treat your new game as if you were invited to invest in it.
What if you handed over the whole concept to another dev team? Would your description, concept and business plan still satisfy your needs to secure your investment? If yes, then probably you’re on the right track!”
