Last weekend was the 27th edition of the game development jam Ludum Dare. The theme for this competition was “10 seconds”. As usual, I contributed with a game of my own – something called Hijack Humans Hastily. It was an AS3 game (made with Nape and Starling) in which the objective was to use a UFO to capture 10 humans using less than 10 seconds of thruster fuel. It was also mostly developed with the OUYA as a target platform, although there’s a web version of it. Here’s a gameplay video (sorry about the accidental music):
I managed to do real-time broadcasting and recording of the entire development, something of a tradition for Ludum Dare games. The whole set – around 20 hours of it – is available at Twitch.TV. Here’s the usual time-lapse, having the whole process condensed into 2 minutes:
I have a full post mortem posted on Ludum Dare’s website. However, I’d like to repeat the conclusion of it here.
I think this was probably my mostÂ well-roundedÂ Ludum Dare entry so far. Iâ€™m pretty happy with how it turned out, and I spent plenty of time watchingÂ my own time-lapse video of the development process. Itâ€™s great seeing it slowly transform before your eyes.
Still, the relative smoothness of this Ludum Dare made me realize something. Ludum Dare is a lot more about theÂ content, and Iâ€™m not sure Iâ€™m very happy with it.
Because of the limited time, itâ€™s better to have a great idea, create a lot of content and gameplay, and test it out until you have something fun. Some of the compo and jam entries Iâ€™ve tested were really fun to play, more than just being an interesting concept thatÂ couldbecome a game.
In my mind, I like to use Ludum Dares to explore new mechanics â€“ mostly in the form of newÂ codeÂ â€“ and almost as an excuse for learning something. And to be sure, Iâ€™ve done a lot of that; all Ludum Dares have been a great experience, even the ones where I didnâ€™t have anything very playable in the end. I learned a lot in a short period of time.
Still, having to be forced to spend more time with content and gameplay is something bums me out. Having to ignore bugs unless theyâ€™re showstopping, and having to get things to workÂ fastÂ (as opposed toÂ right) is something that, over time, Iâ€™ve almost forgot how to do. Nowadays, I like to get a cool system to work as a stepping stone. In a way, itâ€™s almost as if gameplay is secondary to that (in that it comesÂ afterÂ that, not that it isnâ€™t important).
Something else made me realize that. Over the past few months, Iâ€™ve been slowly developing a game prototype on my free time. It makes me really, really happy. I take my time to get some things right â€“ be it gameplay, animation, or lower-level systems â€“ and itâ€™s very rewarding. I do one thing at a time. Putting a pause in developing that to do Ludum Dare #27 was good in technical terms â€“ I ended up learning several features I plan on adding to my game, such as ray casting in Nape â€“ but I also realized I wanted to get some thingsÂ rightÂ rather than just getting them done. For example, my starling shape utility classes â€“ to transform imported Flash Sprites and MovieClip into Starling textures â€“ is a mess. It works, but there’s a lot of edge cases where it doesnâ€™t work as intended, or where there’s a lot of redundant code. And Iâ€™ve used it in 3 projects already, with no actual time for refactoring them and making themÂ elegant.
I know the usual solution for Ludum Dares it to use an engine. Some might say I should have used Flashpunk, Citrus, or any other engine. And they would be right. But the reality is that it wouldnâ€™t have been as much fun for me. As weird as it sounds, to me, Ludum Dare is an excuse toÂ writeÂ something from the ground up. Not just to get something done, but to appreciate theÂ journeyÂ of development. And Iâ€™m sure that, for many people, seeing something done is what motivates them over everything else. It surely motivates me. But Iâ€™m starting to realize that I care too much about getting systems right. Maybe itâ€™s an annoying developer thing. My own professional work is always done on tight deadlines, make no mistake, but over time Iâ€™ve learned to balance it all and use time well to get something thatâ€™s mostly right from the get go. It normally means a better, more stable project in the long run.
Iâ€™m very grateful for everything Iâ€™ve done and learned. Ludum Dare is an awesome idea. But Iâ€™m not sure what Iâ€™ll do with the next Ludum Dares. I might do them, but maybe as part of a team, or maybe without submitting anything. I may use it as an excuse to build a â€œdemoâ€ of a system â€“ e.g. my game controller classes, which need a few additional features â€“ rather than an actual game to be played. Weâ€™ll see.