Over the last decade we have seen an interesting change in action and multiplayer-based designs with the adoption of RPG systems and progression. From the likes of Borderlands, Dark Souls, Call of Duty and many more, the RPG influence has had a profound impact on game design and progression. With that said however, it’s not the magic solution to good design and can do harm to a game’s long term viability if not kept in check.
Everybody likes to talk about win states and rewarding the player for playing their game, but there are very few talks on the punishment for failing or fail states. As game design has evolved over the years, so has the different ways to fail a game. For today’s post, we’re going to look at the hierarchy of fail states, and how there is more than one way for the player to feel the sting of failure.
From a previous industry insight over on the Game-Wisdom YouTube channel, I discussed the challenge of raising the price of your video game after its been released. These days with Games as a Service being a popular model, we are seeing more games given the post release support. Knowing how to add value to your game is a big deal when trying to earn more revenue from it. For today, we’re going to break down the three most common ways developers will work on a game following its release.
Today’s Industry Insight is on the subject of game delays and why they are ultimately a good thing for video games. This in response to a backlash from an indie game being delayed this weekend, and designers need to remember you only have one shot to launch to a game.