Skip to main content
Photo by Marcus Ganahl on Unsplash

A1: monster

Assignment 1 of COMP1720/COMP6720: build a monster that moves, using p5.js shapes, colour, variables and the setup-draw loop.

In this assignment you will create a monster that moves in p5.js.

Your goal is to make a monster that’s interesting, coherent, and has personality. It should seem like there’s a character behind your monster, that it’s more than a bunch of shapes on screen. Think carefully about how you use colour and shapes to create an interesting and coherent monster. Think about how you can use movement to communicate personality.

Outline

Requirements

Your monster submission must:

You can include a background (behind your monster), if you want, but it’s not a requirement.

And a few “must nots”:

The artist statement

Your submission must include a short (max 200 words) artist statement. This is a short document, written in the first person, which explains:

The artist statement is your chance to tell us what is interesting and artistic about your submission—don’t assume that we can guess. It’s you chance to explain how and why your work is interesting, coherent, and has personality.

You won’t receive a separate mark for the artist statement, but it will be used to judge how successful your submission is as a work of art and your abilty to design and construct a computer-based artwork.

Getting started

Here’s the process for working on the assignment:

  1. fork & clone the assignment 1 repo

  2. add whatever code you like to make a cool/interesting monster

  3. when you run the sketch, hitting spacebar will save a still image of the sketch (as a monster.png file in your Downloads folder)

  4. when you’re happy with your monster.png, copy it into your assignment 1 folder (this will overwrite the previous version) and commit the new version to the repo (and push it up to the GitLab server)

Submission process

  1. fork the assignment 1 template repository from the Gitlab server

  2. clone1 & work on your fork of the assignment 1 repo, regularly committing & pushing your changes to the GitLab server

  3. at the submission deadline, the latest commit2 pushed to the GitLab server (not on your local machine!) will count as your submission

Submission checklist

  1. my project satisfies the requirements

  2. my completed assignment has been pushed to the GitLab server, and all the required files (your versions of artist-statement.md, references.md, monster.png and sketch.js) have made it to the server

  3. my references.md file includes at least two references, and everything not mentioned in there is my own work

  4. i have viewed my submission on the test URL and it displays correctly

FAQ

How do I get started?

The first thing you should do is to fork the repo to your account, clone it, make very basic monster out of one circle, and push it back to GitLab. Hey, wow! You’ve started!

After that, try some of these ideas:

If you can do that, then you’ve proved to yourself that you can submit something (and you’ll save yourself some panic if you don’t do that until just before the deadline).

Does my monster have to be scary?

No, it can be a friendly monster, or an indifferent monster. Any emotional response is fine as long as your work communicates personality.

Can I change the size/dimensions of the canvas?

No, you need to use a square 800 x 800 canvas as set up by the template: createCanvas(800, 800)

Can I use images or sounds from the internet (e.g. as a background image)?

No.

Can I use insert advanced p5 feature here?

Yes, as long as it doesn’t involve using images (see above). We may not be able to help with some advanced p5 and JavaScript that isn’t included in the course so far.

Will I be marked on the monster.png image, or the sketch that created it?

The sketch.

How do I submit my references & artist statement?

The template repo contains “starter” files for both of these. You should change these files to put your own content in there, and commit & push the files up with the rest of your submission.

Basically, everything you need to submit is in that Git repository—as long as you make the changes in there, commit them and push them up to the GitLab server then you’re all good.

Footnotes

  1. make sure you clone your own fork (i.e. the one with your uni ID in the url) to your local machine, not the template (because obviously you aren’t able to change the template for everyone—GitLab won’t let you) ↩

  2. it’s the main branch which counts as your submission—which is the default anyway (if you’ve just followed all the instructions then you’ve been working on the master branch all along) ↩