This jam is now over. It ran from 2021-04-18 04:00:00 to 2021-04-30 03:59:59. View results

This jam is for students of GAME1007. Share your work for others to enjoy and comment on!

Create a game page, fill it out with a description or details, set your own price, and upload a build for others to play! 

Instructions:
In the files section at the bottom of the page creation, you should upload a built executable for Windows 32-bit, (and other versions if desired). available for free or pay-what-you-want. The build must not contain source code or other unnecessary files. That means you cannot just submit your project folder.. The correct way to do this is to build the game, take the .exe file it produced, then put it together in a NEW folder with the .dll files and all your assets. No .lib files, no .cpp files, no .h files, no .vcxproj files. Only assets (sounds, images), dynamically linked libraries (.dll), and the executable (.exe). keep in mind that relative file paths when running the exe will be relative to the .exe, which is different from when you run it in editor. Please note that if you share your source code online, and anyone else in the future downloads it and tries to submit it for an assignment, you are guilty of cheating, whether or not you gave them permission, and that comes with consequences which reach farther than one course, or even one year. 

With that out of the way, on the game page, I recommend you include the following (but it's up to you):

A banner image or gif of the game
Short, catchy description: Something that makes people excited to play your game!

How to Play: includes a description of everything needed to play the game. Controls, mechanics, etc. Include any special cheats included with the game. Or bugs you would like to re-cast as “cheats”

Credits: shows the names and student numbers of the creators, as well as their specific contributions to the assignment as a whole.

Licensed Assets: If you did not use any external assets, make a declaration of this. Otherwise, list all licensed assets, regardless of whether or not the asset license requires attribution. Include:

  • The IP holder (e.g. Kenney.nl)
  • The specific assets or asset pack used (e.g. Simple Space)
  • The licenses under which each individual asset is used (e.g. CC0)
    Note that while I will not do the checks to enforce it here, I do not endorse violating copyright laws

    This Jam is optional and purely for fun--to provide you with a place to share your work with each other. It is not an official part of the course, and does not have any grading associated with it.