Skip to content

AssignmentREFLECT Due DateGrace Period10% Penalty Period30% Penalty Period
Pixel PusherReflectTue 1/211/22-1/231/24-1/251/26-1/27
Critical Analysis #1ReflectThu 2/132/14-2/152/16-2/172/18-2/19
PICO-8 Game JamReflectThu 2/272/28 - 3/013/02 - 3/033/04 - 3/05
Press StartReflectTue 3/04
Before Exam
NoneNoneNone
Team Declaration FormNoneThu 3/203/21 - 3/223/23 - 3/243/25 - 3/26
Game Design DocumentTBATue 3/253/26 - 3/273/28 - 3/293/30 - 3/31
Physical PrototypeTBAThu 3/27
Before Lecture
NoneNoneNone
Quest LogTBADue Every Sunday Starting 3/30
Unity Game JamTBAThu 4/034/04 - 4/054/06 - 4/074/08 - 4/09
Working Game DemoTBAThu 4/10
Before Lecture
NoneNoneNone
Critical Analysis #2ReflectThu 4/174/18 - 4/194/20 - 4/214/22 - 4/23
Team GameTBATue 4/22
Before Lecture
NoneNoneNone

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 of x to convey purpose clearly.

Readable code is essential for collaboration and maintaining high-quality projects. Aim for clarity, not just functionality!