Defeat!
nihilocrat on 2008/09/14 00:01
of Norwegian Blue
Unfortunately, we aren't going to gave a game this time around.
Lessons learned: a) Cars generally just make your life hell. Don't own one! b) Think through about how you are going to implement EVERYTHING in a game design before you settle on choosing one. Seemingly simple problems can actually be very, very, very difficult and thus make you not want to actually solve them. c) Corollary of b: you are probably best off making a stupidly simple base game concept, such that you could make that base game in the space of about two days (therefore it must be so stupidly simple that you'd predict you could make it in an afternoon). Act like the compo only lasts these two days, really try to lie to yourself (it's not pyweek, it's Ludum Dare!) so you can get a complete, shippable game done by that time. Use the rest of the week to polish and add all the neat game mechanics / level designs you might have thought of in the design phase.
I might seriously come up with some metrics for (c), like "the game can have no more than 2 behaviorally unique actors".
In the meantime between now and next pyweek, let's hope we can build some interesting libraries...
(log in to comment)
Comments
RB[0] on
2008/09/14 02:09:
LOL - maybe it was just the theme ;)
phren on
2008/09/14 00:04:
Yeah I feel like committing to a single idea that you're not really sure of is a bad idea. I feel like having a very early prototype (maybe some proof of concepts?) is very good in spotting the most difficult parts of development.