24 hours in

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)

(log in to comment)

Comments

Hi James,
If you find a bug in cocos, or if you don't know how to do XXX with cocos, leave us a message here: http://groups.google.com/group/cocos-discuss .
We will help you.