Solo Quests
| Assignment | REFLECT | Due Date | Grace Period | 10% Penalty Period | 30% Penalty Period |
|---|---|---|---|---|---|
| Pixel Pusher | Reflect | Fri 09/05 | 09/06-09/07 | 09/08-09/09 | 09/10-09/11 |
| Critical Analysis #1 | Reflect | Fri 09/19 | 09/20-09/21 | 09/22-09/23 | 09/24-09/25 |
| Pico-8 Game Jam | Reflect | Fri 10/03 | 10/04-10/05 | 10/06-10/07 | 10/08-10/09 |
| Press Start | Reflect | Fri 10/03 Before Exam | None | None | None |
| Critical Analysis #2 | Reflect | Fri 10/10 | 10/11-10/12 | 10/13-10/14 | 10/15-10/16 |
| Unity Game Jam | Reflect | Fri 10/31 | 11/01-11/02 | 11/03-10/04 | 11/05-11/06 |
Adventure Party (Team) Quests
Overview of the Adventure Party Quests
| Assignment | REFLECT | Due Date | Grace Period | 10% Penalty Period | 30% Penalty Period |
|---|---|---|---|---|---|
| Adventure Party Declaration Form | None | Fri 10/17 | 10/18 - 10/19 | 10/20 - 10/21 | 10/22 - 10/23 |
| Game Design Document Initial Draft | None | Fri 10/31 | 11/01 - 11/02 | 11/03 - 11/04 | 11/05 - 11/06 |
| Physical Prototype | None | Fri 11/07 Bring your prototype to class | None | None | None |
| Quest Logs | None | Due Every Sunday Starting (and including) 11/02 | |||
| Digital Prototype | None | Wed 11/19 Bring your prototype to class | None | None | None |
| Final Adventure Party Game | Reflect (Should be done individually by each member) | Fri 12/05 Bring your final game to class | None | None | None |
Quest Submission:
- All assignments are due by 11:59 pm ET on the specified due date (unless otherwise specified).
- 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:
- Game Design Document (GDD): Provide a descriptive and detailed GDD. Clearly explain your game’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 meaningful variable names.
Readable code is essential for collaboration and maintaining high-quality projects. Aim for clarity, not just functionality!
