
I want you to imagine you’re at a party. I like to think that my readership is cool and sociable enough to have been to at least one, so conjure that memory up.
While you’re at that amazing party, you meet some new people. You’re probably introduced to them through a mutual acquaintance. You’re not so cool or sociable that you can just start going up to strangers at imaginary parties and chatting away to them.
As the “getting to know you” small talk continues, eventually the inevitable question is asked: “So, what do you do?”
Now, this is the bit where I start to get a little flustered (oh yeah, I can totally handle talking to strangers up until now).
I will usually pause to think about what intonation is best to use on the next sentence. I need to read the crowd a little and try to work out if they are the sort of people likely to think my job is incredibly crap and entirely childish. Or are they nerds and thus likely to be impressed by, or interested in, what I do.
“I make video games. You know, for PlayStation and Xbox. That sort of thing.” Depending on my conclusion I will either mutter that and quickly move the conversation on, or proclaim it as if I am God, and prepare to bask in glory.
Some day that glory will come. What usually happens is either a) They weren’t really nerds at all; b) They ask if I can get them some free games; or c) Very rarely I’ll get asked how I got in to it.
So since there’s a slight chance that someone reading this will want to know the answer to that last question (because if you’re reading a blog called Mainly About Games I think there is a strong chance that you are interested in games, if only a little bit) I thought I would write a post about how I managed it.
And then spend half of that post on the set-up. Oh well, you live and learn.
Anyway, on to getting in to the games industry…
To say “I fell into it” is pretty much the truth, though slightly simplified as I did do a bit of steering myself. It was sort of like getting a decent score in Monkey Target.
Though I am a very youthful thing, I have a brother who’s nine years older than me. In his teens he was very interested in computers (though has since given that whole lark up for something much better paying. Sensible guy, my brother). This meant that at a very formative age there was a Commodore Vic20 in our house.
This also meant computer magazines, and with them came type in listings for games. I was probably around five or six years old at this point, and was watching my brother type these things in, then work through the listing to find things to change. I think the earliest bit of programming I did was change the “programmed by” credit on some type-in game to say it was entirely my own work. Six years old and already performing IP theft. Shocking.
After the Vic20 came an Acorn Electron. This was the computer that salesmen flogged on the understanding that it was the same basic machine as UK schools used at the time (the BBC Micro, if you’re interested). It never seemed to be wildly successful to me, and many popular games were never released on it and not many of my friends had one.
This general lack of commercial games could possibly be what pushed me more towards programming my own. I was never the strongest programmer (and still aren’t to this day), so unfortunately I was limited to Basic, but still managed to knock out a few simple shoot ‘em ups, platformers, and a couple of text adventures. I also remember my first encounters with simple modding, as a few Gauntlet clones shipped with map and graphic editors.
Eventually I / my parents saved up enough money and, realising that the trusty Electron was on its last legs, bought an Amiga 500. This is pretty much where I got the majority of my games knowledge, and also where I continued to create my own games, this time in AMOS (yeah, hardcore coding there!)
Anyway, all of this exposure to computers and games somewhat predictably led to Computer Science being my strongest subject through my GCSEs and A Levels (I’ve included Wikipedia links so that those not in the UK can still follow what sort of age range I’m talking about here). From that I went to The University of York to do a Computer Science BSc.
At this point I hadn’t really thought about games in a professional capacity at all. Computer Science seemed like a good general subject that would suit me well no matter what area of computing I eventually wanted to get in to, and that has latterly proved to be the case. Still today if I’m asked how best to get in to games I suggest doing a generalised computing qualification that includes programming.
Between my first and second years at university I spent some of my student loan on buying a PC, as by this time the Amiga was pretty much dead in the water, release-wise. The PC was just coming in to its own. Command and Conquer and Quake had been released within the last couple of years, and everything was looking very exciting.
I soon splashed out on a 3d card for running Quake, Quake 2, Tomb Raider and Carmageddon. At the same time my housemate had bought a PlayStation, and so I was seeing a steady stream of the best that had to offer.
The next year I did an industrial placement. This was for Digital Equipment Corporation in Reading, UK. Working meant that I had a lot more spare time in the evenings (no coursework or reading to do – brilliant!) and I somehow fell upon the idea that making maps for Quake would be a good idea. This was down to it being the game played by my house and work mates over lunchtimes, as the software rendering kept it going on work computers.
Later that year Half-Life was released, and since it used the same basic engine and tools as Quake it was a simple step to move on to making maps for that, and then later Counter-Strike.
Back in university for my final year, and it was time to start looking around for jobs. I was applying to all of the big computing firms, same as all of the other computer science students. But as I was browsing some Counter-Strike mapping forum one day (admittedly my memory for which site isn’t so good, especially since I lost all of my bookmarks in a change of computers a number of years back) I saw a recruitment thread. A company in Sheffield was looking for level designers to work on a console FPS title. Hey, Sheffield is near York, I should apply for that, what’s the worst that could happen?
And, as they say, the rest is history. That job was my first step in to the games industry.
Obviously I’ve had the chance to talk to a lot of games designers since then, and it seems that my route isn’t entirely uncommon. Most people get into games because they love games, and that usually ends up with them working on something in their spare time.
Some more cynical commentators might suggest that this prepares them for exactly the same experience in the industry. I couldn’t possibly comment.
Anyway, I hope this has been an interesting (if overly long) read to at least one person wondering about getting in to games. I have a few more updates planned along these lines – some further suggestions for how to best get yourself into a games job, and also a bit of a retrospective on my old maps (which should be fairly embarrassing).
And now that you’ve read about how I became a game designer, maybe you’d like to read my tips on how you can become one too.