First, the mockup!

(Click image to view larger)

Anyway.. the simple concept is you are controlling a fleet of the last ships of your race.  You are fleeing your planet as an alien armada of doom approaches.  You will be able to move your fleet up/down/left/right and there will also be a key that lets you toggle the density/pattern of your fleet.  Think of it as able to expand or contract.

You will move through the armada avoiding colliding with capital ships and what will surely be horrendous energy weapons fire as they attempt to anihilate your race.

You must get a least ONE of your ships through the armada to win.  The more ships you get through the larger your bonus at the end for saving a larger gene pool of your race…

Simple idea, hopefully the scope will be one of which I can get a fun, playable game out of before the deadline is up…

I thought it would be nifty if instead of directly building units, you had to attract units with various buildings. So you start with a base and 1 swarm. There are resource buildings (Apple, Flower, and Metal) that you can hover over that will give you various resources. You also have a base. You can build either Apple or Nectar huts in your base. These increase your attraction rates for food or nectar. (It was originally going to be food and sex, if you read the code. I guess bees have sex with flowers or something.) Once bugs are attracted to your base, you can add them to existing swarms, or break them off into new swarms. You can also build Radar to increase your attraction range, or buildings to increase the power or speed of your bugs.

Initially this was going to be swarm vs. swarm warfare, but I ran out of time pretty quickly. (I’ll go into my mistakes below.) So instead the computer just sent a specified number of waves with a specified strength at you at regular periods, and you needed to have swarms built up and ready to fight when they came.

Obviously one of my largest problems was art. As you can tell from my screenshot, It’s ugly. Really really ugly. All the art in the game was ‘placeholder’ art that I was going to go back and fix. That never happened. Secondly, I panicked at about 30 hours. I barely had an engine, and the deadline was closing in. I actually ‘gave up.’ I came back to it, and finished up later. Thirdly I didn’t have a good plan. I know I wanted an RTS, but I didn’t have a good execution plan. I also bit off WAY more then I could chew back then.

My tips for beginners are:

1. Make a plan – Seriously, take that first hour, and may out some code to get rid of the urge. THen take the next hour or two, and make a task list. What code does your idea need? Divide it up into tasks. As you go along, check things off that you’ve put in.
2. Take breaks – This is always a newbie mistake too, but, make sure you take regular breaks. 48 hours, even with a couple of sleep periods, is plenty of time to get something done.
3. Start Small – It’s much easier to add to a simple game then it is to try and cram in everything a more complex game needs.

Theme Swarm. I did a shoot em up, sidescrolling thing. Play the game online

Ingame screenshot

This is an in-development screenshot, showing some octree debugging going on.

That’s how the game looks like. Shoot down all the pink, eyed balls to encounter the uber-cool-final-boss-with-superior-AI. (I got feedback suggesting that at least one person actually played long enough to encounter the boss – so I consider the gameplay aspect successful.)

Here’s a mirror of the original submission: Swarm