Jam Rules


These rules are laid down to allow a fun, entertaining and fair event for everyone. They are subject for iteration and improvement. These rules apply to all jams, unless otherwise stated.

The admins may remove games if they do not conform to these regulations.


Every game jam can be divided into the following states:

  • Announcement (usually ~2 weeks before the jam)
  • Programming (usually 48 hours)
  • Packaging (usually 24 hours)
  • Voting (usually 1 week)
  • Finished


The theme will be randomly chosen from suggestions from the previous jams, from IRC and from the subreddit. It will be announced at the beginning of the contest here, in the BaconGameJam subreddit and on IRC. Everyone may suggest a theme.

Participants who have registered with the option to receive email notifications will also receive the theme by email.

All games must have something to do with the theme. We won't be fussy about that, though, so it's ok if the theme is not the main thing of your project, but it has to be visible. Browse the list of jams to see what has been chosen as theme previously.


Freely available, external artwork may be used as long as a source is provided in the posted game. The artwork authors should be credited. This applies to sounds and graphics likewise.


Making a cross-platform game is strongly encouraged. However, you are not required to make your game cross-platform in order to participate. Be aware that the community does not consist only of Windows users. A user may downvote your game if it can't run on the user's platform.


Any freely available external libraries may be used for your game. The library doesn't need to be FOSS but it can't be payware. Proprietary engines like UE4 and Unity are alright.

Snippets/personal Code

Usage of snippets/personal code is allowed, as long as its not game related code. You can code your engine/toolset before the jam, but you should not code the game before the jam starts.

Hardware compatibility

Your game will be run by netbook users as well as high-performance desktop users. If you make a game full of shaders and fancy graphics stuff, do not expect everyone to be able to run it. You are free to do this, though. Be sensible.


When packaging, you are not required to provide the full source of your game with the release, it is encouraged however. Game jams are a learning effort for everyone and the games created for it provide excellent and small working examples. Do not be scared about losing your copyright, even if you choose a copyleft license. The code is still yours and you may use it commercially afterwards, regardless of the license you choose for this game jam. External libraries should be included in the most sensible way. A small library like zlib may be put directly into the sources if this is more convenient. A bigger library like Ogre3D should only be referred. You will get some extra time (usually one day) for packaging your game after the jam has ended. Ask in IRC if you need help with compiling/packaging.

Source control

Use of a publicly accessible source control system is encouraged but not required. Github is recommended. To make this clear, you are not required to share your source but again, you are encouraged to do so.

Team size

Solo jams: You have to work on your own. All content that is being created for your game within the time of the game has to come from you. That includes the source (except external resources or older snippets available to the public), artwork, sound and everything else.

Team jams: You can work in teams. The team size is stated in the jam description, if not, it's unlimited. Your team can include coders, artists, game designers, composers, anyone.

Time limit

The time limit is stated in the jam details. A normal jam runs for 48 hours, starting from the announcement of the theme in IRC. Any work after the deadline is purely minor bug fixing, compatibility fixing and packaging. No gameplay changes allowed.