One of the most important (if least mentioned) aspects of game design is how smoothly the game operates.  Your game can have snazzy features and a great concept, but for it to be really fun to play, it can't handle like a constipated tank.  Unfortunately, avoiding this issue isn't exactly easy.  Smoothness of a user interface is something that's difficult to quantify, but I'm going to give it my best shot.

First off, let's take a quick look at a game that gets it right.  A couple weeks ago I raved briefly about the delightfully smooth experience that is Frogatto.  What is it, exactly, that makes Frogatto so smooth?  There are a couple of things.  First, the engine runs well on typical modern hardware, so it has an excellent framerate.  Nothing feels smooth when you're chugging along at five frames per second, and Frogatto avoids this issue entirely.  More than that, though, it's Frogatto's design that makes it smooth.   For instance, if you've downloaded the game already, try walking around, and watch what happens when Frogatto changes directions.   Seriously, go try it right now.  I promise this blog entry will be here when you get back.

Now, did you notice the amount of time it takes for Frogatto to turn around?  It's not abslutely instantaneous, but at the same time, it's very responsive.  If it took him too long to turn around, the game would be annoying to play -- that much is obvious.  But here's the kicker.  If he turned around instantaneously, the game would feel klunky.  That small amount of time it takes for him to decelerate and begin moving the other direction adds a level of immersion to the game that wouldn't otherwise be there, because Frogatto acts physically the way you might expect him to in the real world -- a way your brain is already hard-wired to understand.  As a consequence, Frogatto's controls feel very "real" and natural.

Some of you may be thinking, well, my game is a turn-based strategy game, so none of this applies to me.  If that is, in fact, what you are thinking, then you are incorrect.  That touch of physical realism that makes Frogatto fun to play can also be applied to your user interface.  Consider the lowly drop-down menu, for instance.  The easiest way to implement a drop-down menu is just to have it appear instantly when the user clicks on a certain item.  Unfortunately, this is also the least pleasing to the eye.  If you want the menu to feel natural, you need some sort of transition, perhaps sliding it out.  But that's not quite enough!  Not only does the menu have to slide out, it has to slide out in a believable way.  This means that it can't just slide out at a constant velocity, but rather, it should start slowly, get faster, then slow down again, and finally stop, and it should do all of this quickly enough that the user doesn't feel like they're waiting for it.

Now, perhaps this is all just glitz and flash -- and you can certainly make a pretty amazing game while ignoring these things altogether -- just look at Dwarf Fortress, for instance.  People don't spend countless hours playing it for the smooth and intuitive gameplay.  Nevertheless, if you want your game to have that finished feel, take some time to work on making the controls and UI as smooth as you possibly can.  Keep your transitions fast but not instantaneous, and you'll do well.

Bart

P.S.  We're still looking for 4 more new subscribers this month.  If you can spare 3 bucks a month and want to help us buy new art for the community, hit the "Donate or Subscrube" button on the right. :)

I know there are a lot of FOSS game projects out there that keep an eye on OGA, which makes us very happy.  If you're reading this and you're a maintainer of a FOSS game project, there's a very easy way you can get more out of OGA.  Namely, make a list of the art assets you need.  It doesn't need to be a complete list, even -- just a few things you can think of off the top of your head.  When you have your list, put it up on your forum or wiki and put a link to it on our forum, or just type up a forum post here on OGA with the list and keep an eye on it.  Be sure to specify which license(s) you prefer.

You'd be surprised how often our contributors are sitting around idling in IRC, looking for ideas for things they could work on.  Make that work to your advantage and get some game assets out of it. :)

Peace,

Bart