Gaming Your Way

May contain nuts.

Go left. NO! Not that left, the other left!

Let's start with a screenshot of the recent game prototype:

The testbed for the goon's AI.

Even though it's only 2D, there's a lot going on to let the goons walk around the map on their own. Handling their normal way is easy enough, it is just looking ahead 2m and then decide what to do next (mostly broken up into multiple random chances).

If the goon sees a door, it is set as next target and he start walking into that direction (although there's a check every now and then to see if the player can be shot). After he reaches the door there aresome things to decide:

  • Have we reached the max number of steps (90% chance of using the door to exit the stage)
  • if not, there's 10% chance of an early exit
  • ... and a 5% chance of turnung around
  • otherwise pick the next target
Doors are easy.

Elevators on the other hand trigger a lot more possible actions (heavily simplified):

  • Is the elevator on the same floor? (and is it empty?)
    • Enter, pass or turn around
  • otherwise:
    • is the elevator coming towards our floor (90% waiting for it)
When the goon is finally in the elevator there are still a lot of things to check:

  • are we heading towards the player's floor? (keep going until we reach him)
  • no? (chance of riding another floor or exiting the elevator)
  • are we at the top or the bottom (90% chance of getting off, but which way?)
  • ...

Here's an image of an early draft for the goon AI:

And the first playmaker based version (I since moved that over to code)

The code version is in a way easier to maintain than the playmaker version, but also less easy to track when you want to know what's going on.

And with this, I need to get back to the goons ...
--Olli

I want it painted black

Firstly, thanks to everyone who played the demo over the weekend, the feedback has been excellent.

To celebrate the game finally going out into the wild I had a couple of lazy couple of days, just adding love here and there.

I think the title of this post gives away where I spent that time.


The fire effect was in the demo, but I wasn't quite happy with it, so I've exported all the frames with -60% brightness and now as the fire burns on we slowly reveal the darker frame ( Just by increasing it's alpha ).
It's a little change but it makes a big difference, it's good to show direct feedback to a players actions.

Now because re-exporting a ton of frames is just boring donkey work I treated myself to adding some ember particles rising up off the burning zombie.
Zombies are only going to catch fire when caught up in an explosion, which already triggers a ton of particles ( Maybe too many at the moment, I think I may be showing off a little with those and could perhaps cut them back ) so there's actually a delay before we trigger them embers to try and keep the performance high.
Also I think the embers will be dropped entirely if the game is running on mobile, on my iPhone 5 I'm getting a fairly good 30fps, my iPad3 is less and more variable, so eye candy like this can be optional depending on the platform.

Squize.

That's rotten

So it's been like a 100 years hasn't it ( Well, nearly a year ).

Time to pimp our new game then,


I've been working on this for just over 3 months now, my first big HTML5 game, and we're finally able to show off the demo:

http://www.gywgames.com/rotdemotwitter/

We're about half way through content wise, there's a more weapons and outfits to go in there, mainly this build is to see if people find it fun or not.

Hopefully over the next few weeks I'll actually flesh out what goes into making a monster of a game like this.

Squize.

PS. It's good to be back.

Welcome back.

Well, time flies. 

A few days ago (actually weeks now) we sat together and talked about the neglected blog and what a shame it is that the (dated) visuals prevented us from adding new posts (lame but this is how things work).

Anyway, the blog also needed to be moved to new server and the software needed an update as well, so we decided that this would be the time to do it. Or maybe tomorrow. Or next Monday. Or next weekend ... oh that was last year? Fuck!

Soooo....
here we are, on a new server, the newest version of the blog software and a new design (which is, I must admit, the default design slightly modified).

A lot has happened since the last post (a new year for instance, which is already 1/3 over), Squize is working on a really impressive html5 game (I'll nudge him to do some posts about it) and I've been busy writing non game software and just prototyping and doing a good deal of 3d character work in my spare time.


We'll try to get up to speed again with the blog, so hopefully there will be a shitload of new articles ...

-- Olli

It's Friday, again ? So soon ?

As a quick follow up to the last post where I was trying to fix the tiny slow down in the game I had a bit of a break through. Reducing the size of my pooled objects made a really large difference ( I was just pre-pooling too many items, mainly as a safety net ).

With those pools reduced it's a lot smoother now, which I'm pleased about.

Set up a twitter account for the game ( @DN8Pulse ) , as I think it's going to be an easy way to get quick feedback from players.

And to hopefully finish off the twitter / social stuff I've added a "Tweet your score" option to the game over screen. I thought rather than just a bland text tweet a custom image may be cool, and that's what you can see above there.
( It's all done using Movieclips and Sprites in Flash, so didn't take a fraction of the time to have done it in Starling, and it's just so nice being able to layer and position things in an IDE ).

I've just finished the Orbs power-ups, these are two droids that spin around your ship blocking baddie bullets. If a bullet hits one rather than just being destroyed, it's rebounded back at the baddies, which should hopefully be slightly more than a nice touch.

A bit of a slow week really, more focused on the fluff rather than getting levels and baddies in there. There's still more to do than I'd hoped for, it should be coming to a close now.

Squize. 

(no subject)

On the weekend if I'm working I like to count it as "Treat days", where I get to dick around with things I don't really have time for.

This weekend I updated the skybox to a much nicer collection of 1024x1024 textures and to celebrate I added some parallax stars.

The stars had to be away3D sprites as they needed to go behind the planets ( That took ages, 3D positioning isn't my strong suit ).

It looks lovely with a 100 stars, really nice and subtle, but as ever the iPad isn't going to cope with that. When I was testing though I did notice a one frame hold up when a baddie was killed ( The new stars actually really helped with the testing of this, I could see them jitter, which is something which I was missing with just the planets / skybox in there ).
Today has been spent trying to optimise things to avoid that judder. It was a case of removing every element of the explosion until I found the bottle neck, which it turned out are the particles.

So I've removed one of the explosions ( Down to 3 from 4 ), capped their max size as they grow in size depending on the beat of the music, reduced the number of particles which are belched out and done some loop unrolling in Starling itself.

A couple of things I noticed, with the particles I could pre-calc pretty much everything, their speed / rotation / speed and store all those values in Vectors in the constructor so their actual movement / scaling is just a case of getting values from a Vector, which helped. The code per particle is really cut down now.

Also with my alteration in Starling to keep the visible / invisible display objects in their own Vectors ( More here ) I found that there could be really large loops due to the number of children in the game, so I've unrolled some loops there. I think I need to do some more work though, as triggering 34 particles at once means a lot of looping to move the sprite from the hidden to visible Vector. There's got to be a smarter way to do that.

All these amends still haven't got rid of the tiny judder, I don't think it's going to be possible and I'm not that gutted about it, I'm developing on the slowest on the market iPad ( 3 ), and I added an additional check that if there are more than 20 particles running at once then I hide these new sexy parallax stars. It may sound nasty, but they're really tiny and it gives the impression that they're blinking ( Also if there are explosions kicking off on screen you're not going to notice anyway ).

Have I go time to mention retro mode ? No, ok, let's save that for now then.

Squize.

Sociable, for a change.

At present with the game I'm trying to do as many of the boring things as possible, they're going to need doing so let's kill them off in one painful hit.

So yesterday was the pause mode. Now user acquisition is a thing I need to think about as this is a mobile game, rather than a Flash one that will get traffic almost in spite of itself, and the cheapest way to do that is to leverage social networks ( Shit, I'm starting to sound like all the blogs I've been reading recently. Just don't get me started on Customer Lifetime Value calculations ).

Rather than shoehorn a "More games" link or banner ad to the pause mode, I've added the ability to tweet a screenshot.

My never used personal account, a victim of my own spam.

I'm quite pleased with it, it has a nice taking a photo effect along with a picture frame, it looks pretty good. Ideally I'd like to be able to let the player mess around with the image like the screen grab feature in AAA games, but I don't know if only one person in the whole world will use this, so it's best to focus on what will be used rather than what could be.

And that's the Game Over and pause mode done. Hopefully next week will see more levels ( I've got to drop the bosses in yet, which I'm looking forward to ) and the final player power-ups.

Squize.

It's game over man!

That's such a lazy title isn't it ( I bet I've used it before )

Ok adding the Game Over stuff may not seem such a big deal, but it's an essential part of the flow. It's almost a complete ( Rather than finished ) game now, we only need the game complete sequence, which I've not really thought about yet, and that'll be it, the flow from start to finish, which is a great milestone to get out of the way.

The other part of doing the Game Over sequence is that it's a way to test that all your house keeping routines are working, that sprites and particles are being properly killed and put back into their pools etc. I know that happens between levels, but it's still important that the game can transition from title screen > game > title screen again with nothing breaking and everything nice and clean.

You'll notice the blurred baddies. I did try Starlings blur filter in a vain hope that may just be powerful enough, but it gave me 20fps on desktop, and as I keep the level playing in the background it just wasn't going to work. I did find a good looking alternative on the Starling forums ( http://forum.starling-framework.org/topic/code-much-faster-gaussian-blur-implementation ) but by that stage I realised it just wasn't going to be practical to perform a real time blur on a ton of objects.
So I cheated, and just exported all the baddie sprites and bullets with a blur, and adding them to the sprite sheet. We're doing fine in terms of GPU memory, so although it's a little extravagant we're no where near to hitting any hardware boundaries.

That's it, game over man.

Squize. 

That one day of the year...

...where the whole internet seems to competing with itself to be as unfunny as possible.

Fucking April Fools Day, a vacuum of humour.

Anyway we've not posted anything for a while, sorry, I've been a little under the weather, so not been as communicative as normal.

Lot's to update you about, I'm sure I'll repeat myself and / or forget some things, so let's just plough headlong into it.

I had a weird bug where the game broke and baddies just kept exploding, and it looked awesome, so I've actually altered the explosions to emulate that bug and they look much better.
Yesterday I altered the particle effects slightly so they slow down and that looks better too ( Had a play of Geometry Wars for inspiration ).

I've started adding in the player weapons, I think I'm roughly half way through that, the "Pods" are pretty cool.

Adding these meant updating the baddie bullets / baddies themselves so they have collision checks against them which doesn't seem to have hurt performance.

So we've got more weapons in there, the first 5 levels are done ( I discovered Flash' BezierSegment which has improved the paths a lot, both in terms of how they look ( As I was only using one control point ) and the speed it's all calculated ), but the big thing was...

I redesigned the level select system. What a massive fucking pain in the arse that was to do in Starling, I think 3 whole days was spent on that.

Yesterday I had a bit of a break and played with getting the game running on Android. It's almost there, but there are some issues with the FLV playback. Because I'm using the normal display list to show it I just can't get it to position correctly on the different sized screens ( The game is 1024 x 768 for iPad, whereas the Nexus7 is 1280x736 and there are a couple of other oddities you have to take into account ), I even tried using percentages like in html, but no joy. So I'm going to have to re-do that. Joy.

So for now it's just a case of throwing data at the game, I need to finish the player power-ups and adding the levels, then it's sound, remaining UI and Game Center / ads integration.
I want this gold in two weeks time, so I'm in two minds about adding the challenges, they may be a post launch update just so I can hit the deadline ( It may be a case of skipping the challenges for iOS, putting them into the Ouya version to give some added value as we'll be charging for that, and then retro-fit them back into the iPad game. I'm not sure yet, we'll have to see how we're doing for time ).

Squize.