I like eugman's additional challenges, but even before he posted them I was thinking up my own challenge since I was a tad bit disappointed in 'robots.' I decided to spend a half hour writing as many game ideas as I could in haiku form.

I ended up with 11 of them - most all of them are terrible. I'm going to wait until my teammate has seen them to post them in case one ends up being our idea, the other 10 will be up for grabs!

So I'll add to eugman's list of challenges: write a haiku, then base a game entirely on those 17 syllables.

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)

i hate the process of coming up with art, this is my first time doing any game dev in a long time and the process of finding/creating art reminds me why I quit. I know it isn't the biggest deal, but it annoys and distracts me.. that is all