GMTK Game Jam Next Weekend + Jam Tips

A game jam is a video game development marathon where you have a fixed amount of time to create a game that matches a theme. After the development period a rating period follows where people will play your game, rate it and offer feedback. It’s a great opportunity to experiment, show off your skill, get good feedback on a game, and all around have a fun time!

This coming weekend (July 15-17) the Game Makers Tool Kit (GMTK) Game Jam is happening: GMTK Game Jam 2022 -

This competition is one of the largest of the year and currently has over 15,000 people registered for it.

My friends and I have done this specific competition for the past two years and have created games like Drunk Thief (A Drunk Thief by IanGoGo, jaredmv) and Joining Forces (Joining Forces [Project 2021-7] by IanGoGo, jaredmv). I have my team pulled together for this year too.

Incase you are also interested in participating too, I thought this would be a good time to share some personal tips for this type of competition.

Biggest Tip:

  • Have fun! Don’t force yourself to do a competition like this or suck all of the enjoyment out of it by grinding for 48 hours straight on something. Take your time, enjoy it!


  • This jam uses a community rating system with the categories of Enjoyment, Creativity, and Presentation
  • People will most likely play your game for between 3 and 10 minutes, you have that amount of time to introduce your mechanic and make the game stand out from others
  • Don’t go around begging for ratings on your game, people tend not to like that and may give your game a lower rating if they do play it
  • Some people will offer ‘rate for rate’, this can be a double edged sword as these people will often speed through games and not give them much time


  • Graphics aren’t everything in a jam, what matters is consistency.
  • Lots of free art exists online from places like Kenny (Kenney • Free game assets) and openGameArt (
  • If you do use art from online, check the license for it
  • If you do decide to create your own art, finding a good color palette can add a consistent look to a project. A good website I use is lospec (
  • Don’t completely neglect graphics in a project, one of the categories for this jam is " Presentation" which covers both graphics and sound


  • Music is very effective at setting a mood for a game
  • Try to balance the audio between sound effects so things aren’t too loud / quiet
  • If a sound effect is used a lot (like foot steps) keeping it on the quieter side is alright
  • If a sound effect is used a lot, adding a random amount of gain or speed can help it from feeling repetitive
  • If you are using sound effects from online, check the license
  • Good royalty free music website (incompetech Music Search)


  • Stray away from the common interpretations of a theme, a little creativity can go a long way in making a project stand out
  • When brainstorming, make sure to write down your ideas incase you need to revisit the list later
  • If you are struggling to brain storm, look up the words in a thesaurus and try to envision ideas around those words
  • One of the rating categories for this jam is “Creativity” so spending a little extra time on this can help your game to stand out
  • It is okay to go with your first idea or a common take on the theme. What matters most is that you have fun, if you quickly think of a fun idea then go for it. Don’t get so caught up with the idea of winning that you take the fun out of it
  • Given the scale of this competition, making a quirky or unusual game can really help it to stand out from the flood of generic platformers and top down shooters
  • Be flexible, if you start a project and it’s not working, you can restart and search for a different theme, just keep in mind the competition lasts for 48 hours and restarting will eat up a lot of time
  • Adding more features doesn’t always make a concept more fun


  • Make sure concepts are well explained and logical. I once made a game where coins powered up a weapon. Many players were super confused on what to do and it hurt their enjoyment of the game.
  • Some sort of tutorial, even if you just use text labels in the background of a level, can help a player to understand a mechanic
  • Providing a safe area for a player to learn and experiment with a mechanic can help them to quickly learn
  • Showing is more powerful then telling. Example, having the player call onto a checkpoint both saves the game and teaches the player what a checkpoint does
  • Players tend not to like backtracking or tedious tasks
  • If a game is hard for the developer, it will be impossible for a casual player
  • If you go with a level based game, unlocking all levels from the start can let players skip a stage if they are stuck

Time Management:

  • The time limit for this jam is 48 hours, the game needs to be submitted before time is up
  • I recommend doing an early build (like half way through) to make sure you don’t have any build errors and so something can be submitted in the worst case scenario
  • Build a prototype first, test your mechanics in a temporary level to make sure they work (and are fun)
  • Don’t over scope yourself. It’s easy to envision something beyond what is possible for you to do in 48 hours
  • This jam does allow for some pre-existing code, it just can’t be written specifically for this competition. I personally have developed a ‘universal jam template’ with some libraries, level loading handler, settings menu, top down/ platformer character controller, and a blank collection I use for most jams now. It’s okay (and within the rules) to have this stuff ready to spin up a project quicker
  • It is better to have one or two really well polished and fun levels then a dozen broken and unfun levels
  • After the submission period is done, you can always continue to add to the game. You just cannot upload changes until after the voting period ends. Some creators love their jam entries so much they turn them into full games
  • It is okay to take breaks, make sure to still eat, go outside, sleep, etc. Sometimes taking a break can clear your head and give you a clearer solution to a problem


  • It is okay to have a deep story / lore for a jam. Just know most players aren’t going to sit and read walls of text
  • If you have cutscenes, provide a way to skip them
  • Don’t bury a tutorial in exposition, some players will miss it and be confused


  • If you are using a new library or tool, do a test HTML 5 build and bundle to make sure it works correctly
  • Make sure you are on the latest version of Defold to prevent bundling issues

General Tips:

  • Use some sort of version control when working. If your computer crashes or you break the entire project, it can be useful to revert to a slightly older build. I personally recommend github or gitlab
  • Make sure to have fun with it! The ultimate goal of doing something like this is to have fun. Don’t force yourself into doing something like this, or get super stressed thinking about it. This is an opportunity to have fun and create something to be proud of.

Best of luck!

If you have any other good tips then feel free to add them as a reply to this post!


(I skimmed your post so I’m sorry if you mentioned this already)

Since people will be playing your game for 3-10 minutes, make it easy. I’m serious. You’ll be testing it over and over and over again as you develop. You’ll get good. You’ll get so good you won’t notice the game is actually quite tricky. Do not put people off making your game too hard for newbies!


This is a great post with a lot of very helpful tips for game jams! With your permission I would like to reproduce it as a Defold blog post (with credit going to you ofc).


That’s a good tip, I mentioned something similar about difficulty but I like how you put it here!


That would be great! I give you full permission to reproduce this as a Defold Blog post!

1 Like

Thanks! We’ve published it now, with a few minor edits to make it useful to any game jam and not only the 48h GMTK jam.