So we finished our Second Ludum Dare! It feels great
Boy was this one FRUSTRATING
But we learned SO much……
-POST – MORTEM-
First the things that went WRONG
-1. LIMIT THE AMOUNT OF BETA SOFTWARE USED-
Heres the first thing I did wrong. I am running on a OS 10.9 beta. I am writing my code in Xcode 5 beta
Besides all of the crashing, one night I hit a total dead end bug in Xcode where I could not distribute my app. I almost QUIT the dare.
-2. MAKE SURE IF YOUR STREAMING/TIME LAPSING THAT ITS SET UP AND WORKING BEFORE THE JAM-
I spent too long trying to make sure my stream was exactly the right way, plus because of rule 1, it kept crashing, total productivity bust
-3. PREPARE YOUR TOOLS/CODE BASE/LIBRARIES BEFORE THE JAM-
This jam I switched over to SDL for the first time. I hit so many little snags that were simply because SDL works different, a number of times my productivity stopped was because SDL would be handling Floats as Integers, and leaking memory when it renders text, or flat out dropping sound because of an extra curly bracket.
Things that went RIGHT!
-1. Work with friends-
Luckily I had the support from two close friends of mine. Both of which worked with me in the previous jam, but had dedicated time this jam to help. Having three people working on the game felt nearly perfect. The conversations were always motivating and productive. Also having two other people critique your code/sound/music/art is always great. A number of times Id find myself implementing something , and because of lack of sleep/reality/food one of my friends would remind me that what I did looks or sounds RIDICULOUS
-2.Have a Plan-
My friends and I prepared better for this jam. Last jam we did not realize the theme was announced so soon, so we scrambled after work to get together. Not this time, we were together as soon as the theme was announced and spent a good 3 hours whipping up ideas. I have a HUMONGOUS white board that worked so well in capturing and reducing our ideas to the very best ones. We could then get down to work, and glance at the checklist of things we needed to do on the whiteboard.
-3. Share often -
Try to have people test your game as soon as you can, some of the weird little things you know about the games rules or how it plays may not be apparent to others. You have to develop a sense of “communication” to your player , and there is no better way than to see how another player plays your game.
Overall, I feel extremely accomplished having finished a second dare. This time the pieces fell together much better than before. We had the idea down the first night, then got cranking the next two days. My friends and I discovered new talents and developed some since the previous jam. We look forward to finding out when the next jam is, and now I can’t wait to try some of your games!
—Don’t forget to try our game FSCK! Bit needs your help!—-