It has been a while since I posted (other than about bitmap fonts in flixel). A brand new baby daughter and a wildly increased work load in the office has cut my coding time down dramatically. But tonight I updated and released our new game Quartet. Quartet is a graphically retro-inspired puzzle game. You attempt to assemble faces as quickly as possible, with more “complete” faces scoring much bigger points. As the timer decreases things get frantic and it’s as much as you can do to survive, let alone put that final piece of robot chin into the slot you need to secure a “full face” bonus

The game is now in active bidding on FlashGameLicense, and we’ve had favourable feedback and play testing from a lot of people. Those who “get it” seem to really love it, and ferocious high score challenges have occurred on the beta test. We took a lot of player feedback on-board and produced the final build this weekend, which is up on FGL.

Right now I cannot tell how the bidding will go. It’s started ok, with a healthy first bid, but the weekend has meant its failed to progress from there. I think the quirky retro style may put some sponsors off (as opposed to the game itself) but personally I love what Ilija’s done with the graphics and music. It has a charm all of its own. And while part of my brain wonders what would have happened had we shoe-horned it into a contrived Aztec / Egyptian setting, or one with cute Safari animals, I’m glad we didn’t.

I’m also glad that Quartet is finished, and that we completed it in such a short time scale. There is nothing quite like the feeling of finally releasing a game! It’s quite a buzz. A good kick-start, because we have much bigger, more impressive titles looming sharply on the horizon, and some big changes for this blog. So stay tuned folks oh and if you can view the game on FGL, be sure to check out the Credits!

Today I released my FlxBitmapFont package to Google Code. This allows you to use bitmap fonts directly in your Flixel 2 games:

The bitmap fonts are just an extension of a Flixel Sprite, meaning you can throw them around, collide with them, scale them, rotate them and generally cause havoc. Or of course they could just be UI elements, proving a score/lives count. But at least the choice is yours

11 fonts are included, 2 sample programs and comprehensive documentation in the form of a PDF file. I’ve also published that here on my blog: http://www.photonstorm.com/flxbitmapfont and I will update both my blog and the Google Code archive as needed.

Anyway I hope you have fonty fun with this! Look out for a number of new Flixel classes from me in the coming months, or catch me on the flixel forums where I help moderate the place.

FlxU.overlap in Flixel 2 uses the new FlxQuadTree to handle collisions. It allows you to pass in either a single object (say an FlxSprite), a group of objects (FlxGroup), or even a group of groups! To be honest the more you give it, the more useful it proves to be.

However it’s got one annoying side-effect: if you don’t specify a custom function to deal with the collision, it will kill() your objects. This is often a far from ideal end result. For example if you had a bullet and an enemy being compared – you may want the bullet to be killed instantly, but the enemy to be only “hurt” by this, reducing it’s health.

The only way I’ve found to do this so far is to override the “kill” method of FlxSprite (in my Enemy class) and then perform the logic in there. Reduce health, update animation, health < 0, then kill it for real.

This isn’t ideal, but it certainly works – so if you’re stuck in a similar bind with FlxU.overlap, this may help.

Also it’s worth mentioning (as this caught me out too) – if you do specify a custom function for overlap, make sure it returns a Boolean. False will ignore the overlap, true will say you’ve dealt with it. If you don’t return this value it appears to default to killing your objects again.

I’ve been playing with Flixel a lot recently, and over on the forums someone was having trouble getting a “snake” game to work. I always applaud people who “start simple”, rather than diving in the deep end and sinking without trace.

So I spent lunch time today knocking together a simple snake game in Flixel 2.23.

There are no graphics (just blocks), but it shows how to use an FlxGroup to handle single to many collision checks, simple sprite controls and of course a basic snake game mechanic. The whole thing is just one single class file with no external requirements.

It’s up on my GitHub account here: http://github.com/photonstorm/FlxSnake

And if you want to join in, the forum thread is here: http://flixel.org/forums/index.php?topic=1261.0 (I’m a moderator on the Flixel forums, so drop by and say hi!)

This game was created to celebrate the launch of Series 2 of the awesome little Droplet vinyl toys. iLKke and I took the Droplet characters back into an 8-bit NES style era, complete with platforming action, colourful scenery and a truly micro bipbop vibe.

Read more about the game, and of course play it on the Droplet page