We’re Amused Sloth and we recently released our newest needle to the haystack called mobile games, in the form of Disco Dave (iOS/Android).

The game was well received by both Apple and Google. We got to 500.000 downloads in the first month which was enough to make us proud and boost our egos a bit. This was the smallest project we ever tackled. Yet, it taught us a plethora of lessons and debunked many of our theories about the world of mobile game development. In this article we want to share one of the most peculiar problems we faced and how we decided to approach it, in the hopes that it will help other game designers.

Game Bug: Diagnosis and Remediation

Oops, we made a Boo-Boo!

Soon after launched we started seeing glimpses of what we later ended up calling “The Tile Hack”. Kids would post videos on YouTube about their discovery of a cheat, store reviews started mentioning things like “I found an easy way to stay alive. Now it’s too boring.”, our QA managed to easily reproduce it and ultimately what triggered the last drop was an email we got from fellow game developer Austin Shaf from Gnarcade. Austin took time out of his day to write us an email letting us know about the issue of which we’re very thankful.

This led to us bumping the priority of “The Tile Hack” to a critical issue. Even though to us it wasn’t even a bug, it was part of the game 🙂

Yes. You read that right. The issue everybody was complaining about was something we always knew about and considered a part of the experience. What the players found was an easy way to stay alive, but to us, the game was never a survival game, it was a high score game. We intentionally made it easy to survive, but hard to reach a high score. This was all intentional, yet some of the players felt that the game became predictable.

Thinking vs Feeling

At this point there was no ignoring the issue. It was actually causing us to lose retention and get lower ratings from people who misinterpreted the game as a survival game. We had to take quick action. This is the part where we decided to go off-script and impose a different way to fix bugs like this, even if we did not consider it a bug.

The first instinct you get as a game developer is to quickly jump into action and fix any issue your baby has, just like a parent runs to a child that stumbled and fell. This would mean quickly changing the algorithm of the game or worse – hack a fix, pushing it quickly to the store and pretend nothing ever happened. Basically, sweeping it under the rug.

We decided to go against this knee-jerk reaction and sleep on it for a night. What we came up with felt better and more honest. Everybody on the team loved the idea. Implementing it actually brought the team closer, reminding us why we got into this business in the first place.

Rewarding vs Punishing

So, the player discovered a pattern in your game. That means he was active and paying attention to your creation. Having the knee-jerk reaction of quickly fixing it and pretending it never happened would be like punishing them for being clever little scoundrels.

That goes against every instinct we have as game developers. Games are about discovery. They are about having those a-ha moments. The human brain is wired to find patterns. Yet punishing them for it is the initial reaction all the developers have and is considered the right way to do it. Well, here is where we decided to disagree with the status-quo and show that we want to make our own path in this industry and not blindly follow the best practices.

We decided to leave the pattern like it was, but make sure the player knows the game is about making combos, instead of surviving and actually rewards the player for finding “The Hack”. When a player follows the pattern for 9 times in a row, we pause the game, we congratulate him for finding “The Hack” and unlock a secret hacker character.

Our secret character is a Guy Fawkes figure wearing mask, dressed in “V for Vendetta” dance clothes. We felt this properly expresses the player’s pattern seeking personality (and makes the player look more badass).

Game Bug: Diagnosis and Remediation

Yay, we learned a lesson!

The lesson we learned with this experience goes beyond issues and reactions and player feedback. The most important thing we extracted is that we will always be prone to misjudge situations if we act upon our initial impulses or “what did the others do?” mentality.

Brains conserve as much energy as possible when performing a mental task. This will lead to designers having rigid mindsets. Developers implementing the easiest solutions. Artists accepting to have their creativity suppressed for the sake of current trends. And overall, a product that does not stand out amongst the competition.

Since the update, our ratings improved, and our analytics show an increase in retention. Yay! 😀

Don’t lose your creativity and uniqueness in a world of preconceptions and settled processes. Don’t always jump onto the first instinct. Keep your eyes on the ultimate goal of your creation. Remember that games are about learning, improving and having fun, not about spreadsheets and checklists.


Article written by Flaviu Vescan

This article was originally published here.