This post was previously written on my blogsite and has been slightly edited for Ludum Dare. For the full post, visit: www.acheronstudio.com
Foreword
In preparation for the upcoming Ludum Dare game jam I wanted to write up what I’ve learned from my previous experiences. I’m by no means an expert, as I’ve only participated in 2 proper game jams: one hosted online that I participated in from home (LD28), and one hosted locally (Global Game Jam). Both jams I completed on my own. Both games I produced were done using Unity, and my experience with Unity is about just over 6 months worth of full time work at the time of this writing (Around ~3 months worth during the time of the game jams).
For a list of my previous jam games, read the full post here: www.acheronstudio.com
Making the perfect submission
There are 3 important periods surrounding a jam; before (preparation), during (execution), and after (networking).
Preparation – before the game jam
When it comes to the actual game jam, you want all of your focus to be on creative development; working to get your idea playable. As such, when it comes down to it, you don’t want to be wrestling with tools or with the submission process.
I submitted this warmup game for Ludum Dare 28. I suggest submitting or preparing a warmup game prior to the actual jam as it gets you to actually use the tools you’ll be using while also getting down the submission process.
Another thing that’s important to do is to prepare a sandbox prototype. In my case, I made a very generic first person game with basic interactions. When it came time to actually make a game around a very specific theme, I didn’t have to code or problem solve basic interactions. Ideally, this is how you’d want to start your game jam.
When the jam actually starts, you don’t want to be doing things that you haven’t done before and have little experience with. To some, a game jam is a perfect time to try out a new tool or language they’ve never used before. If you have very specific motives then I’m not going to say you shouldn’t – but my opinion is that you want to be using tools and languages that you’re experienced and comfortable with. The exercise is in finishing a game, and the learning outcome is in going from nothing to a completed prototype in 48 hours.
If you can get a working playable prototype using a tool you’re comfortable with, and have it submittable in some form (web, or an executable), then you’ll be in a great position to start a game jam.
Lastly, you’ll want to consider the several different categories that games are rated against for Ludum Dare submissions:
- Overall
- Innovation
- Fun
- Theme
- Graphics
- Audio
- Humor
To get a good overall submission, you’re going to want to get high scores in all of these categories. Don’t forget about graphics and audio. My LD28 submission had NO audio, which automatically got me an N/A, or 1 star for Audio. That’s a significant hit to my overall score. The same went with graphics. Though my “art style” was intentionally minimalistic, you can still do things to make it look nice. Next time, I’ll pay more attention to these different categories. You’ll want to do the same.
Execution – during the game jam
So the theme has been announced and the jam has started. What now? My suggestion is to spend at least a couple of hours brainstorming ideas. Talk to friends and family and see if you can bounce ideas around. Check out what people are posting on the Ludum Dare blogs and see what people are saying on twitter. You want to be a part of the conversation.
Don’t over scope. Try to come up with a single unique focus. What might happen during your implementation process is that you’ll discover new and interesting things worth exploring. That’s good! You’ll want to explore the idea as much as possible and see what cool things come up.
Eventually, you’ll get to a point where you find a really unique hook or mechanic. When this happens, you’ll want to focus down and start implementing this thing. Start making levels, if your game has levels. Don’t digress and keep at it.
Try to aim for a deadline that is 2 hours before the submission deadline. I would usually say give yourself only 1 hour, but the hour where things go most wrong is during this hour, so you want a comfortable period to make any necessary changes and fixes while also trying to compile and submit your project. In these 2 hours you’ll also want to get yourself a game icon and some screenshots. If you’re up for it, maybe record yourself a gameplay video too. These are all part of the submission process, so give yourself ample time for them.
For uploading web builds: I suggest using Kongregate. It’s either that or dropbox – and dropbox will eventually stop allowing public downloads of your game when it’s reached a certain limit. This happened to me, and you don’t want that. So go with Kongregate.
Networking – after the game jam
Immediately after the deadline hits, you want to start reviewing other games. Review them and make comments! This will get the system to more likely present your game when others are browsing. I almost immediately got more plays of my game once I started reviewing them. Commenting on other games will get others to check out your games too. A rate for rate kind of thing.
Come back and rate at least 10 games each following day. This ensures your game is consistently among the findable games. What I also did was search for games that were similar to mine, commenting that they should play and rate my game.
Be active on social media and post your game on some forums; Unity and GameDev are good ones. Write up a postmortem and post that on Ludum Dare too. The weeks following the game jam is exactly the time others need to know about your game, so make sure you’re getting yourself and your game out there.
Conclusion
Be well prepared, stay focused and don’t over scope (you only have 48 hours!), make a game and tell everybody about it.
Let me know what your submissions were, how you did, and any advice you’d like to add 
Good luck everyone!
-Adam Thompson
www.twitter.com/AcheronStudio
www.acheronstudio.com
