Concept, prototype, polish.
The jam puts into practice everything discussed so far!
Day 1 — Decide what to make and plan how to make it.
Day 2 — Build the roughest possible working version. Start simple.
Day 3 — Add game feel and polish. Make the core action feel satisfying.
Pick the track that matches what you want to practice:
Design and prototype your own interesting mechanic.
Remake an existing game in Unity.
| Prototype (Design) | Remake (Tech) | |
|---|---|---|
| Day 1 — Concept | ||
| Delivery | A concept document about your core mechanic. | A technical document outlining your remake plan. |
| Day 2 — Prototype | ||
| Delivery | The simplest playable version of your core action. | |
| Day 3 — Polish | ||
| Delivery | A prototype that shows potential. The core mechanic is prototyped and could be expanded. | The core loop of the original game, present and as polished as possible. |
Start by picking a verb from this list:
Then think: how could this verb be turned into a game mechanic? Your concept document must answer:
You don't need the document ready by 14:30 — finish it by end of day or start of the next. But you must have picked a mechanic by end of Day 1.
Prepare a short document (or just notes) outlining:
The simplest possible minimum action, playable It doesn't need to look good! It doesn't neeed to feel nice. it just needs to be playable.
You must have another student try what you're building. Watching someone else interact with your mechanic for 60 seconds will teach you more than another hour of building alone.
Ideally, the core loop is already in place. If not the entire core loop, the main mechanics should work by the end of the day.
A prototype interaction that shows potential. What matters is that the core mechanic is prototyped — something that could be expanded, that demonstrates an interesting idea. Add game feel and polish if time allows: screen shake, particles, sound, animation, timing.
Today, the core loop must be present and as polished as possible. Get as close to the feel of the original as you can.
If you don't have a working version from Day 2, getting it playable is still your first priority. Polish whatever time allows after that.
The goal is designing mechanics and understanding interesting interactions.
✓ AI can write code for you
✗ AI must not design the game for you
The goal is learning the Unity pipeline.
✓ AI can help brainstorm and explain
✗ AI writing your code is discouraged