Bad games != Bad developers ( Sometimes ) 20. January 2010 Squize game development (4) I see a lot of blogs where people tell us all how to make good games. It seems lots of people have something to say on this subject, even if they've only got one or two games under their belt, and then of dubious quality.Some posts are truly inspiring, they show common gameplay / design issues in a new light that just clicks in your head, that "Shit yeah" moment when you connect with someone else's words in such a way that your own thoughts are solidified.Other posts are like a tick list of game design. Responsive controls. Fair collisions. Give the player lots of power-ups. Shops, shops are always good. Sigh.Rather than me force my view of game design down peoples throats ( I still only consider myself a so-so game designer, I've got better, but I'm far from good. If I was good I'd be confident to lay out my golden rules, but without me being able to say "You know that game I did, that you loved and played for hours ?" and all of you agree, I don't think I'm too well placed to hand out the testament according to GYW ), I thought I'd take the other tact of explaining why some games have faults.Sometimes shit bits in games aren't due to the developer being shit. There, I've said it.How many of us have posted a game to a forum and died a little inside when having to read "It's good, but if you did <whatever> it would be better" ? Or the classic "It'll be good when it's finished" after the person playing it has just played it on the client / sponsors website. What part of that obviously been finished haven't you noticed ? Don't get me wrong, no one's above feedback, and you can't post a game and expect everyone just to gather around you in a circle in awe. For the most part the feedback is spot on. When it's not though, it jars like nails down a chalk board.We don't live in a utopia where every game is released when it's finished just how you want it. There are developers who release their magnum opus, and when asked how long it took you hear "Over 6 months", "Around 9 months" and so on. That's great, that's games as art in their purest form. That's not game development as a viable living though. That's game development as a hobby, a break from the day job. If you spent 6 months on a game, well fuck, it should be exactly how you wanted it, there's very little reason for it not to be aside from technical ability or the ability of collaborators.In the temple of making a living wage with games, things are different. You have a budget to work to. If it's a client game then you have a deadline as well as a budget, not to mention the client themselves.If you're doing a project for a client you usually have a set amount for the project. That includes designing how the game will play, prototyping if need be, some times creating custom engines or getting your head around 3rd party libraries. It means getting an artist on board if you don't work with one full time, giving them direction, sorting out a sound guy too. It means showing builds to the client and waiting for sign off, and dealing with amends. Some where during this time you have to actually ensure the game is fun, it's not a God given right that it will be just 'cause you've done a game design doc. Also you've got bug fixes and testing.The vast majority of your time is spent on getting the features in, getting the game to be what it should be and just working, that things like multiple iterations and tweaking the difficulty curve are just a luxury. You can go over the budget and swallow a loss to devote more time to the more neglected areas, but by over delivering you're doing more work for less money. Good developers do that, but there does become a point of ever decreasing returns, where the extra hours being thrown at a game aren't giving you enough back in terms of cost vs quality.This isn't just a client based issue, even if you're doing a game for sponsorship you've got to have one eye on budget. You know roughly what your game will bring ( Whilst secretly hoping for more ), and you have to avoid slipping into making that magnum opus which will only ever at best earn a fraction of the development cost back. If it's a business then it's got to be about the money as well as the art.This is sometimes why a game isn't as feature complete as you would like, this is why you're aware that "If you did <whatever> it would be better", but unless that avatar on the forum with all the wise words is going to pay you for that extra time, it's not going to happen. It's not a lack of love for the project, or ability, or vision, it's called paying the rent.Deadlines. There's never enough time to do what you want, so corners have to be cut as you need to hit that deadline ( Whether it's for an ad campaign or that Halloween themed game that has to be sold to a sponsor in a very tight time window ). That's not always skimping on levels, only doing 20 where 30 would be better, sometimes it's nasty kludge fixes to your code where you hope that the bug you get every now and again is so rare now that it's just magically gone away as you've put some heavy handed code around it to force it to work rather than re-coding the whole routine.Again things like tweaking the difficulty and testing are hit. Yes, if you press the mute button over and over the title screen hangs, thanks for finding that and pointing it out, I just wish I had the time to test that myself rather than just doing everything else.Clients come in all shapes and sizes. Some of them are great, some of them are not quite as great but still nice ( Yeah I can be faux professional ). No matter what though, they'll want some input. This varies from changing the colour of some text to sweeping changes that push you right up to the deadline, to gameplay changes which just break the game. The adver-game you see is never the developers pure image of what the game should be.So if you're not a game developer, next time you're looking at a game, and you're thinking "How the hell could they release it with that bug / missing feature ?" hopefully some of the above will explain why. Yes, some games are just plain crap, but sometimes every once in a while a good game under achieves. It doesn't mean the developer doesn't give a shit, or isn't insightful enough to realise that it would be better if it did x,y and z, it means they've got rent to pay and that some times that gets in the way of making a truly great game.Squize.