Submission open from 2017-06-16 19:45:00 to 2017-07-18 20:45:00
Starts in

Often times in game jams, your resulting project ends up with terrifying code that only you are able to decipher. Well, until look back a month later at your code to see a monster of what will never be touched again.

This is because writing code as fast as possible on a small timescale does not give you manageable, scalable, or extendable results. The jam solves that by simulating what would happen if you were to die in the middle of a project, forcing someone else to continue your project, and vise versa. This means all your code, assets, and the game idea/direction itself must be well documented, easy to read, etc. This forces a fine balance between fast and manageable code, along with making everything from ideas, themes, direction, etc be vividly presented within the game/documentation itself.

Relay Jam, or, `You Died in an Airplane Crash and Someone Else Has To Work On Your Game` Jam is a team-based game jam event wherein you work on two games, with one other person, during the duration of four days. The event is like a relay race, where you switch games midway with your team-mate. To add in more challenge, you are not allowed to communicate with your teammate during the jam. You are given an additional submission hour to submit the game on the last segment. When the submission hour ends, voting commences.

There are two themes, the first is the global theme, applied to all games, where each person presents a theme and up/downvotes each other's themes. The theme you presented then becomes the theme for your other teammate. Keep in mind that if you choose a weak theme, it might affect how people vote on your game.

More details will be announced when we get closer to the jam date. Be sure to join the Kickass Programmers discord to keep up to date .


You are not allowed to work on a game unless you are its current relayer. This means you must work alone on that game for each relay segment.

At the end of two days, you must 'pass' your project to your teammate. The theme you work with on your first game must be your teammate's chosen theme.

You are NOT allowed to communicate with your teammate about the jam or related while the event is in session. This means that proper documentation must be provided in order to ensure that your teammate can work on your project properly. Be sure to put in build notes and everything else that they might need to know into your documentation!

Distribution of source-code to the other partner must occur at the start of the segment. You are free to share the same repository for a game, but only the current relayer may modify its content.

If someone decides to drop out and they unable to publish whatever work they have finished to their teammate or to the jam submission, then the game is permanently dropped.

You are free to start with any library, any tool, etc. as long as they are all open-source. Engines such as Unreal and Unity are permitted. Other than that, everything must be done in the timeframe allotted. The only exceptions are fonts and intro screens. The resulting games must be open-source, and any library or tool must be publicly accessible. NSFW content is allowed.

After the fourth day ends, you are allowed to port the game and fix bugs, and you are free to communicate with your teammate about the projects.


Once the sixth day has ended, and hopefully all the games have been submitted, voting starts. There will be more details on how voting works in the future.

There will be two winners, chosen after five days:

  • The team with the highest scoring overall game.
  • The team with the highest average score (only teams that have submitted all two games may win this)

The winners of the event get to set the theme of the next event