Monday, February 08, 2010
Well the game is done now, so now it's time to start the submission process and obviously the pimping process.

I've knocked up a cheeky preview video clip of it in action, and it's right here.

Now I've got to do some icons, write some copy that will wow the money out of peoples pockets and take some screenies. Nearly there.

Squize.

Monday, February 08, 2010 6:07:41 PM (W. Europe Standard Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
 Wednesday, January 27, 2010
The huge never ending project I did for National Geographic, "DogTown", has ended.

Dogtown1.jpg

We produced 5 mini-games for it which had to fit in an already written wrapper which managed all 9 of the dogs as the went through the vets getting better with a view to being re-homed ( It's based on some tv show apparently ).

Dogtown3.jpg

In the need to be diplomatic now and again, I'll just say it was an unusual development process. I actually finished on it in November with the client employing 3 on-site coders to finish it off ( And that's not due to me being crap I hasten to add ).

That's about it really. I'm trying to tether my usual blunt and honest write ups on projects, as I don't want to even go down that route with this. I've not played the final version and seeing how you have to pay to download it I never will. I think a developer not caring enough to even see how there game(s) turned out speaks volumes.

I've done better.

Here's the link more for historical preservation rather than expecting anyone to go and buy it.

Squize.

 | 
Wednesday, January 27, 2010 10:14:16 PM (W. Europe Standard Time, UTC+01:00)  #    Disclaimer  |  Comments [2]  |  Trackback
 Tuesday, January 26, 2010
Development of our first bit of iPhone goodness is coming along nicely. The game is an actual working game now, and plays quite well. As you can see the look & feel has taken a major change in direction from the first screenshot the other week.

zap_ingame.png

The glow look & feel just looked toilet. Without being able to use Blendmode.ADD like you would on a normal Flash game and other feedback effects it just wasn't working. It looked like someone had just discovered the glow filter and was dropping it onto everything.
So after a bit of feedback I decided to go for the faux GameBoy look. It's what I was planning originally anyway for the game I shelved. As it progressed I realised the game was missing some character, so out came the JBJ Sisters. They were characters in only my 4th ever Flash game and the only real character based IP I think we've ever done ( You should know by now we're more big slabs of metal and big lazers than identifiable characters ).
Straight away the game got an injection of life, which I'm really pleased with. And the best thing ? I did a remix of the original JBJ Sisters, the "Milk it mix", and that was my first flirtation with making something look like a GB game. So I've got all these GB coloured assets that hardly anyone has ever seen which weren't doing anything and needing a home.

One other major plus is that all the images are 8 bit, there's no alpha blending going on there, which really improves performance. The change has been a major win all round.

The game itself is based on the skeet shooting event in HyperSports. Not the first time I've coded this game, we did a version at preloaded back in the day called Shootin' StarZ, so I knew it worked as a game, and fits the device nicely ( Those two gridded areas you can see are your thumb buttons, it just feels nice in terms of input, straight forward and direct ).

When it comes to changing my game structure for the iPhone, it's really not been too bad at all. I'm still developing it in Flex3 ( And thanks to Rich I've got auto-complete on the new API stuff too, which is really rather lovely ) and doing all the testing with a normal swf with keyboard input, and just publishing it for the device to test performance and new graphics ( They do look different on the ipod than onscreen ).
This means my workflow hasn't been hit by long publishing times, which would have stopped me working on this long ago.

The major change was to do with when to trigger my constructors. I normally don't create class instances until I need them ( Ususally in the startGame() method ) but this was causing a noticable pause when going from the title screen to the game, so I call them during the "preloader".
Basically when an app first runs a bitmap is displayed straight away, then once the app is loaded it cuts to the app itself. All I've done is made the first screen in the game match the initial bitmap ( A big GYW logo, naturally ) so when it cuts from the bitmap to the game there's no change. I can then call all the constructors there under cover, and they set up all their object pools etc. before fading that logo down to the title screen. Nice and simple and effective.

Next up is fleshing out the presentation and giving the game some love and we should be good to go.

Squize.

Tuesday, January 26, 2010 3:15:05 PM (W. Europe Standard Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
 Wednesday, January 20, 2010
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.

Wednesday, January 20, 2010 1:04:47 PM (W. Europe Standard Time, UTC+01:00)  #    Disclaimer  |  Comments [4]  |  Trackback
 Friday, January 15, 2010
After a week of playing I had to abort "Andrew", my first crack at an iPhone game.

It's no great loss in the grand scheme of things, I hadn't committed to it a 100% and was more a tech test hoping to evolve into a game, and as is the nature of these things, it failed.

Onwards and upwards, with a title screen grab of the current WIP, which has got what I think is the worst name I've ever come up with for a game.

zap_titleScreen.jpg

It's my usual "Put a lot of glows on things so people don't spot I can't actually do art" look and feel. The transparent balls are moving around in 3D with a depth of field effect ( An overly grand way of saying blur ).

You'll notice the 3 little breadcrumbs at the bottom center, this is because it uses the usual iPhone finger slide ( Is that the term ? ) to scroll through the 3 pages of the title screen. It's actually done using the old school favourite startDrag(), which is pretty nasty in Flash, but works lovely on the iPod.

That's it for now, I'm not sure what I can and can't say under the NDA, so I don't know if I'll be able to touch on performance ( Much better than I thought, it's very impressive and they're still working on it ) or other API related things ( Other sites may be running more in-depth details about CS5, but lets be honest, I must piss more than enough people off already without adding Adobe to the list ).

Squize.

Thursday, January 14, 2010 11:48:04 PM (W. Europe Standard Time, UTC+01:00)  #    Disclaimer  |  Comments [2]  |  Trackback
 Tuesday, January 12, 2010
It seems the NFL Rush site has opened up the game section, which is cool as I can actually show you some work now.

My favourite of the bunch was the first one I worked on, Gameball Maize Maze.

gmm_grab1.jpg

I think this was only my second iso game, it's not a display system I love, but I'm pleased with the depth sorting on this, it's pretty solid, and I love the art style so much.

As a game I think it works pretty well too, it's more for the younger readers out there, but it did all come together nicely ( There are some blog posts about it's development from way back, this one in particular should make a whole lot more sense now ).

Squize.

Tuesday, January 12, 2010 10:26:46 PM (W. Europe Standard Time, UTC+01:00)  #    Disclaimer  |  Comments [2]  |  Trackback
 Saturday, January 09, 2010
                       i.
.7.
.. :v
c: .x
i.::
:
..i..
#MMMMM
QM AM
9M zM
6M AM
2M 2MX#MM@1.
0M tMMMMMMMMMM;
.XMMMMM ;MMMMMMMMMMMMv
cEMMMMMMMMMU7@MMMMMMMMMMMMM@
.n@MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
MMMMMMMM@@#$BWWB#@@#$WWWQQQWWWWB#@MM.
MM ;M.
$M EM
WMO$@@@@@@@@@@@@@@@@@@@@@@@@@@@@#OMM
#M cM
QM tM
MM CMO
.MMMM oMMMt
1MO 6MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM iMM
.M1 BM vM ,Mt
1M @M .............................. WM M6
MM .A8OQWWWWWWWWWWWWWWWWWWWWWWWWWWWOAz2 #M
MM MM.
@MMY vMME
UMMMbi i8MMt
C@MMMMMbt;;i........i;XQMMMMMMt
;ZMMMMMMMMMMMMMMMM@A;.

So that's being 3 years of GYW ... me and Squize working together for 3 years as GYW - that's worth a little celebration, isn't it?

Oh, and if you discover the secret message you can keep the cake :)

nGFX

Saturday, January 09, 2010 11:43:52 AM (W. Europe Standard Time, UTC+01:00)  #    Disclaimer  |  Comments [7]  |  Trackback
 Tuesday, January 05, 2010
With Ionic in bidding hell ( Really, it couldn't be going any worse at the moment. I think a game about rape would be an easier sell ) it's time to start on the next game.

I've got a vague idea of what I want, and what platform it's going to run on, and the background colour is set ( #B5C7AD ) and that's about it. Acorns and Oaks and all that.

Oh, and it's going to be called "Andrew".

More as and when.

Squize.

Tuesday, January 05, 2010 7:39:42 PM (W. Europe Standard Time, UTC+01:00)  #    Disclaimer  |  Comments [2]  |  Trackback