Hooray, I've finished the basic platformer elements of my game. There's jumping, and gravity, and collisions, and all that good stuff. Here's a screenshot of an early test level:

The somewhat flimsy plot device that is meant to excuse my horrible coder art is that the protagonist, after suffering a near fatal injury, has had certain parts of himself replaced by adaptive cybernetics, including his eyes, which causes him to see the world, um, squareish.

While Alex is off being a code monkey and writing stuff up, I'm being an Artist and doing arty stuff (and not my home work) Last night I drew character design for our little robo character. Today I was playing around and made this little gif. Yay it rolls! It also has a lamp on it's head =D -Biccy

I have completed writing the class which controls the rhythm inputs for my game. The premise of the game is simple, you are a scientist who wants' to take over the world. You build robots and send them to take out any resistance you face. Your control over the robots is based on how well you time the key strokes. Time them well enough and your robots will go on rampage and finish the job faster, Miss the rhythm badly and your robots are bound to fail.

Started working on the class for various units. Have to see if this work out or not.. it is kinda inspired from patapon. I can only hope to reach that perfection :)

Just a few more tweaks and it will be 100%, but I'm calling it done for now! Essentially I worked a little backwards from last time I tried this, I took Saluk's suggestion and created the level editor first before I make the game engine. The level currently consists of 3 layers, base (collision tiles), enemy layer, and event layer. Very similar to Phil's system, should work great for what I need it to do.

H'ok so. I've never finished a full game in python (although I have some near complete prototypes if I'd bother to finish the levels), and I figured I might as well give myself a reason to make a full game. I had a feeling the robot theme would win, but I actually didn't come up with my idea until about 12 or so hours ago.

I love platformers, and most of my work has been there, so I figured that would be a good starting point. Then I decided to incorporate a sort of human-robot symbiosis element into the game for the purpose of puzzle solving and for some simple 2d shooter stuff, so that it wouldn't just be a platformer.... with a robotic main character.

It's coming along quite nicely on the coding side, and I already have my engine prototyped. As far as I can see, it'll just need refinement (and a lot of it). I've also got the robot and human playing quite nicely with each other, and at this point, I hope that most of my future hurdles will be level design and graphics.

I will write a new game in this week.

I am sorry! because I was don't follow the rule before.

:>

Things are moving right along, we have a stick figure robot that moves around in our tile based level. All graphics are placeholders, but are still pretty awesome I think :)

This is four Bubble Boom.

I started my planning 24 hours ago although the first day was mostly brainstorming and getting some of the basics in place.

We're going with pyglet and cocos despite never really having used either. I suppose that's a lot of trust to put in them, but learning them isn't a huge concern as I feel like looking over the tutorials/docs was plenty given my familiarity with OpenGL and the intuitive design of both libraries. I'm sure this means we'll run into quirks we're unaware of as we go along, but hopefully nothing show-stopping.

I've found some public domain code that allows for the save execution of python code, which is key to our game. Initially we were just going to say "if you write a script that rm -rf /'s yourself that's your own fault" since it's a 1 week competition, but sandboxing will be nice if people actually decide they enjoy our game and want to distribute scripts.

We're using google code: Super Robot Battle 200X

(The name is an homage to those awesome Nintendo era games where everything was so extreme, we're hoping to have art/music to match)

First real code check in. Solved the bottleneck problem - was a series of mistakes that led to me refreshing the entire lamina surface every frame. Solved the chain of problems and am now updating just the dirty rects. What was running at 4 fps before is now running at 60. Huzzah. Had our first art check in, so I can now start working on the game stuff. Hoping to get the robot moving and fighting tonight.