For UL Gamejam 2 I joined a team with Dave Ryley and two of his brothers, Brian and Jono Ryley. Dave is a veteran game jam enthusiast, but this was both Brian and Jono’s first experience of a gamejam. Luckily we got a great theme for the first-timers; “Simplicity”.

Together we made Jam, The Game. Naturally, a game about jam is the simplest gamejam game you could make. Our game won the popular vote at the end of the jam, which was a wonderful achievement for our team! We walked away with some great prizes; a JetBrains 100% discounted license and some great books - like A Theory of Fun - which should have a place on every game designers bookshelf. A big thanks to UL Game Development Society for organizing all of this.

A new Gamejam Tradition is Born - Let’s Play

Dave thought about making a Let’s Play of your gamejam game because we had finished nice and early. Make a Let’s Play of a gamejam game at the same gamejam? Sounds fun to me! Luckily Dave had nearly everything necessary on his laptop to capture his screen and record audio of us talking. As it only took about 10 minutes to get it together and upload it to Youtube, this has become a goal of ours for each gamejam we do from now on! Enjoy!

The Jam

To be fair, Simplicity is a great theme. “Simplicity” inspires one to focus on a minimal game - something achievable in the limited time. Let’s cover some details about the jam itself.

The jam started out with a well-prepared introduction from Joe Greaney. He is currently a Game development student and Board Member of the University of Limerick Game Development Society. Joe dispensed some fantastic nuggets of wisdom during the introduction to get everyone’s brain juices flowing. I think the tips really helped. I’ll try to keep them in mind for future gamejams too. Here’s the list I quickly copied down (showing with permission):

  1. Focus
  2. Scope
  3. Get to the core gameplay loop in 30 seconds
  4. Complete a Loop in 90 seconds - e.g. 1 full level
  5. Innovate on 1 thing (e.g. new platform? => known mechanics crazy mechanic? => known platform)
  6. Beware the Rabbit Holes…
  7. Playtest Early & Often
  8. Infinite Brainstorming
  9. Feature Creep There was a nice flow chart, but essentially this:) Can it be done quick and dirty -> Yes -> DO IT! v No.

The theme announcement followed: Simplicity. The message was clear and concise! Now to get down to business.

Planning out the game, quickly!

15 minutes. We had one idea, chatted about it, and it was already way too complicated to make in PICO-8. Remembering the tips above, using them as a kind of razor, we came up with a super simple game like dig-dug. I showed the team a YouTube video of the ancient arcade hi-score chaser of my youth. Let’s just make a simpler version of that!

Here are some of my notes from those early moments.

Darren Kearney’s Handwritten notes for game design of “Jam, The Game” made at UL Gamejam 2

Darren Kearney’s Handwritten notes for game design of “Jam, The Game” made at UL Gamejam 2

Taking ownership of your tasks - trusting yourself and others

Each of us discussed what we would like to be working on for the game, and what roles we felt capable of doing. I was impressed by the go-getting attitude of the first-timers.

  • Art - Brian
  • Audio - Jono
  • Programming - Dave, Brian, Darren

Dave helped set up Brian and Jono with source control. We used git, which was also a first, but Dave helped set them up and I wrote out a little cheat sheet of commands. You can actually access the public git repository here: and you are welcome to fork it.

Working at the same desk it was easy to say to each other what we were going to work on next and negotiate the best course of action. When I realised we would have a bunch of different carts going, but have clearly defined carts for different roles, I thought of making the collaboration tool and wrote that first. The gamejam version is likely still in that git repo.

Doing the work

We worked away happily, headphones in or out, chatting amongst ourselves as need be. Each team member knew what they had to do and so we simply got to it.

Taking time for a break is important. We took them as we needed to, as a team or individually. UL Game Dev Soc provided pizza twice during the day’s scheduled lunch and dinner times. Quite a welcome treat!

A shared feeling among the team

At the wrap up of the jam, each of our team members remarked that they felt they had not done enough. Even Dave felt this, oddly enough, as he not only helped his brothers but also did a lot of the leading on the team - in my mind at least! Overall I think this feeling meant we worked well as a team. Nobody felt that they did all the work, and everybody contributed important things to the game. That’s a win!