Persistent systems have become an effective way of smoothing out the difficulty curves of rogue-likes, and provide replayability and progression to many video games. Despite their popularity, there are ways to cause the player to lose interest in replaying a game.
During a recent live cast, we got on the discussion of the company culture in the Game Industry. Just because studio names like Naughty Dog, Blizzard, Bungie, and more are still around, doesn’t mean that they’re the same studio when they were creating their hits. People go on to new jobs or are fired, but no matter the case, the studio changes.
And this creates an interesting and challenging topic to talk about: Just who is responsible for the success of a video game?
In the past we’ve talked about all manner of tutorial design and philosophy on Game-Wisdom. Such as: The elements of a good video game tutorial, how to structure it and so on. For today, we’re going to set all that aside and talk about one simple fact that many indie developers still haven’t grasped: Every game needs a tutorial.
Over the years I’ve had the luck to speak to developers across the spectrum in terms of success. From those who just released their very first commercial game, to experts with decades of experience working in the industry. Their success in the industry is just as varied, and I had to talk to people about how the last two to three years of their life produced a game that no one wanted to play.
Everyone wants to talk about the big successes, underdog wins, and game changers, but rarely do we hear about the failures. For today’s post, it’s time for another sobering talk about the quickest way new developers fail in the Game Industry.