Assignment | REFLECTÂ | Due Date | Grace Period | 10% Penalty Period | 30% Penalty Period |
---|---|---|---|---|---|
Pixel Pusher | Reflect | Tue 1/21 | 1/22-1/23 | 1/24-1/25 | 1/26-1/27 |
Critical Analysis #1 | Reflect | Thu 2/13 | 2/14-2/15 | 2/16-2/17 | 2/18-2/19 |
PICO-8 Game Jam | Reflect | Thu 2/27 | 2/28 - 3/01 | 3/02 - 3/03 | 3/04 - 3/05 |
Press Start | Reflect | Tue 3/04 Before Exam | None | None | None |
Team Declaration Form | None | Thu 3/20 | 3/21 - 3/22 | 3/23 - 3/24 | 3/25 - 3/26 |
Game Design Document | TBA | Tue 3/25 | 3/26 - 3/27 | 3/28 - 3/29 | 3/30 - 3/31 |
Physical Prototype | TBA | Thu 3/27 Before Lecture | None | None | None |
Quest Log | TBA | Due Every Sunday Starting 3/30 | |||
Unity Game Jam | TBA | Thu 4/03 | 4/04 - 4/05 | 4/06 - 4/07 | 4/08 - 4/09 |
Working Game Demo | TBA | Thu 4/10 Before Lecture | None | None | None |
Critical Analysis #2 | Reflect | Thu 4/17 | 4/18 - 4/19 | 4/20 - 4/21 | 4/22 - 4/23 |
Team Game | TBA | Tue 4/22 Before Lecture | None | None | None |
Quest Submission:
- All assignments are due by 11:59 pm ET on the specified due date.
- Submission instructions will be provided with each assignment.
- Reflect Forms: For each quest, fill out the associated reflect form.
Code Style & Documentation:
Your grade will partially reflect the readability of your code. Follow these guidelines to ensure your program is clear and professional:
- ReadMe File: Provide a descriptive and detailed README. Clearly explain your program’s purpose, functionality, and any key design decisions.
- Comments:
- Add meaningful comments for each function, explaining its purpose and key logic.
- Include comments for complex or significant code sections to make them easier to understand.
- Variable Names: Use descriptive and meaningful variable names. For example, use
gravity
instead ofx
to convey purpose clearly.
Readable code is essential for collaboration and maintaining high-quality projects. Aim for clarity, not just functionality!