So, I’ve gone and produced my warm-up game.    It’s called Driver Hunter, and it’s laughably abysmal, but I figured it’d be worth doing just to see if I could actually produce a working executable.  Don’t trust  that fancy tool you’ve been told does the trick, because it doesn’t.  Distributing pygame is like fighting an angry dwarf.  In my case, it turns out pygame doesn’t like my system font.  Don’t ask why.  So my game now uses Arial, because I’m hip like that.  If  Pygame2exe isn’t working, maybe it’s worth trying for you too.

So yes, lesson 1) check you can actually publish your damn game.  Do you want to release to mac?  To Linux?  To Windows?  Try it, and make sure it bloody works.

Lesson 2?  Sound.  I’ve never done any of my own sound before, but seeing I’m trying to enter the compo, looks like I’m going to have to!   I discovered automata thanks to this post, and it worked flawlessly, producing something that was at least barely passable as game music.

Other than that?  I’m good to go!  Timetable is cleared, tools are ready, fridge is stocked with diet coke.  I’ll be producing a timelapse if I can

Tags: lessons, pygame, pygame2exe, timelapse, tips, warmup

This entry was posted on Wednesday, December 12th, 2012 at 3:38 pm and is filed under LD #25. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.