Posts Tagged ‘lessons’

Lessons from the Warmup

Posted by (twitter: @crimsoneer)
Wednesday, December 12th, 2012 3:38 pm

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 :)

evolution escape – post mortem

Posted by
Wednesday, August 29th, 2012 3:47 am

This time we were not able to finish the game, but we do learn some important lessons :

1. make agreements with the team, believe on me : personal events during the ludum dare can ruin your tighty schedule, so before start make sure everybody involved is in the same pace, and with the calendar free.

2. practice the basics of the technology some days before, even knowing Unity3D, as it’s not my daily basis tool some basic activities took more than expected.

3. react fast, as we had some changes in the people involved in the project, instead of creating useless code while waiting for the artist, I should change the game plan and go with something that could be done with my own artistic resources.

4. share results on facebook is not that hard :) check on this https://developers.facebook.com/docs/guides/games/getting-started/

5. define as a team what will be the folder names for the game assets in unity, so when the export package all over the place madness start, you don’t loose precious time reorganizing files, materials all over the project.

6. don’t make reusable code for ludumdare :) make straight forward code, and then after the ludum dare, find some time to refactor and reuse wherever you like.

cheers.

[cache: storing page]