Theme/Rules: Your entire game (counting libraries and assets) must be no larger than 100KB (uncompressed, i.e. not the size of the CCGAME, ZIP, or RAR file you send me). The goal of the challenge is to see what type of game you’re able to create with such a limited amount of space.
Challenge Time: November 29, 2009 – December 6, 2009 (Entries due by 12:00pm PST (GMT-8) on December 7, 2009).
To Enter: Email your entry to contact@xna7day.com with the subject line “Challenge 3 Entry”.
Please see the About page for full rules/guidelines for the challenge.
#1 by ^DJ_Link^ on November 29, 2009 - 04:44
what means we have around almost 90k of code since xna standard project is around 10k
#2 by brando on December 7, 2009 - 09:18
I will never twitter so I’ll post my thoughts here.
Although I’ve been travelling the past couple of weeks, personally the thought of a size-imposed restriction on a relatively-bloated library just did not appeal to me. I kept on going with my rogue-like because it’s been so much fun!
These challenges have spurred me on in my engine development because they’ve shown me what is obviously missing — hard to make a game quickly without scriptable trigger volumes for example. But I’ve noticed a pattern of people getting excited, then getting overwhelmed, then running out of time, then promising they’ll get in the next one. Repeat. And I’m the same way. Make it a month-long challenge and the same thing will happen, just less often.
I’m a good coder (imho), I’m an okay designer, and I’m a TERRIBLE project manager. Just awful. So even 7 days is too long for me to wrap my head around…I think of all the crazy ideas I could implement and then end up with the easiest because I run out of time
Instead I’m more into a single day challenge, as impractical as that is for the rest of the group…but maybe they’d feel more compelled if they could pick a day and do it from start to finish rather than letting it hang over them all week. Just a thought.
It was my hope that these series of weekly challenges could be built on top of one another. It enforces how to maintain a codebase while adding new features to it, which is a skill in itself. And we’d get to see everybody’s game progress over the challenges. But then people would get behind or miss a week and enh. So maybe that’s just for me.
Not sure Nick, but you hold the contest and I’ll write the code.