Rules

• Team size of up to 4 members (You can do this on the GDSC Game Jam website)
  • Solo teams are permitted
• Game must be developed using the Python (You do not have to use PyGame. Feel free to use alternatives like arcade. Send a message on discord letting us know before you do this though).
• Extra python modules are permitted
  • Must be recorded with the submission
• Game Jam times are from 10am Friday 30th September - 5pm Sunday 2nd October
  • You may use as little or as much time within this period to develop a game
• All work towards producing the game must be completed within the Game Jam times
  • Exceptions:
    • Art assets, must indicate the source
    • Sound assets, must indicate source
    • Sample platformer from workshop 2
  • We allow these exceptions so that students that are not artistically inclined can produce quality submissions
• For further rules for submissions see the submission rules page
• Any team found breaking aforementioned rules will face disqualification from competition

Submission Details

For submissions, your team (or individual) will be required to submit a git repository to the website page. This is just in the form of your repository link. Please make sure your repository is public or add me as a collaborator to your Repo.

Alongside the git repository, we require a demo video (3 min max, to be uploaded to the website). You may (optional) provide a description and promotional video. While the promo video and description are optional, they may improve understanding and appreciation of your game and contribute towards marking in other categories.

Additionally, an informational game page may contribute towards winning the people’s favourite. Which we will take votes for at the end of the competition.

At the following game showcase event we will display the games at uni for other students to vote on, If you’d not like your game to be displayed and not in the run for people’s choice please indicate.

In your git repository, we will also require a requirements.txt file in the main directory/folder. Please fill this file with all the modules that you have used: one line for each module used (we have provided an example of this in the python workshop and should be in the python part of this page). We do not have any restrictions on the modules. We also recommend providing a detailed README.md file with a detailed installation and running guide for your game (especially should it vary from that shown in the workshops). This will help us run your games while marking.

If you have never heard of python, git, or PyGame, please do not let it discourage you from participating in our Game Jam event. As mentioned in the workshops, copy-pasting our sample code, changing the variable names, and possibly the sprites, is a task and a half in itself. Not frowned upon (as long as you change the code up a bit lmao). If that’s something you’d be comfortable please do that. As long as you are learning that is all that matters.

Any code that you use from another developer or art/sound assets that you find on the internet, you must attribute to the original author. This is to make sure proper credit is given for the work and so that markers know what exactly your team produced