The Game Jam is complete, and we are all recovered from it. Here is a collection of things relating to it!
This event caused us to get a lot of stuff up and running, including this blog and a wiki (I <3 wikis). Here’s the wiki page for the event, where future generations can learn about what past generations have done as they plan out their own endeavors (I <3 wikis :D). Check out that page to find out which game ended up most playable, where you can get the code and artwork, and what the teams would like to do next to improve their games. If you’re into our wiki enough, you can create an account and start writing content there yourself! (I <3 wikis!)
Who should come to a game jam?
I was describing the event to a friend at lunch, and he said, “That sounds cool and fun, but I’m just a normal person, not a programmer.” Dear Zach – I’m sorry for the diatribe that followed about how many roles there are to fulfill in a game jam. As I said to you then, you would be especially awesome as a team member because you think about games and what makes them fun.
I’m going to sum up what I said then by saying: If you’re interested in a game jam and would like to try participating, you should! There are a million ways to contribute, and your interest makes you a useful team member.
We ended the weekend with a retrospective made of three questions:
- What went well? (pink stickies)
- What would you do differently next time? (blue stickies)
- What did you learn? (yellow stickies)
You can check out what our attendees learned above – here are the main things we, as event hosts, thought that we should do differently next time:
- Events like this need someone driving them – to say what happens when. The people who come are interested in working on their games, not in coordinating demo time and pizza buying. Coordination makes things work better. This time, we waffled for too long on this and only started being more organized toward the end. Next time, we’d like to know who’s setting the schedule from the beginning.
- Demo time was awesome! It helped to drive the teams toward completing their work and thinking about the next important things. We tossed around the idea of Saturday demo, but ended up only doing end-of-event Sunday demo. Next time, we definitely want a halfway demo, too.
Thanks to the folks who made the game jam happen with your work and lack of sleep and entire weekend – we had a great time with you, and we can’t wait to host another one 🙂