Ship it, get candy
Requirements
Everything your game needs before it counts. A small finished game beats a big unfinished one: only shipped games get candy.
Your game must
- Start from the p5.js starter. Don't begin from a blank sketch: the core loop (spawn → click → score) must already run.
- Be playable end to end. A start screen, a play state, and a game-over screen, even if bare-bones.
- Be ghost or Halloween-themed. Ghosts, pumpkins, bats, haunted houses: anything spooky.
- Add 1-3 upgrades of your own. Movement, sound, lives, power-ups, a boss. Not ten, just a few that work.
- Credit your assets. Self-made, or linked from a free-use source in your README.
Fair play
- Talk with your neighbor, but don't paste their file. Two people submitting the same code both need to have built it.
- AI is fine for unblocking a single line, not for writing your upgrade.
- Sound and art from OpenGameArt, Kenney.nl, or Freesound: link the source.
What to submit
- Playable link: the p5.js Web Editor share link, or a GitHub Pages URL.
- Source: the editor link already has it, or attach a repo.
- One GIF or ~20-second clip of the game being played.
- Two sentences: which upgrades you added, and why.
- Your name / Slack handle, so we know who to hand candy to.
Quick answers
- What if I don't finish?
- Ship what you've got. A working base game with zero upgrades still counts: the bar is a playable link, not a polished product.
- Do I need to install anything?
- No. Everything runs in the p5.js Web Editor in a browser tab.
- Is there a deadline?
- The end of the meeting. Submissions and candy happen live at the showcase.