This course covers the theory and practice of designing and developing computer games, from generating initial concepts to creating a fully playable game. Computer games are interactive environments that serve a specific goal: some enable player fun, some convey rich emotions, and some change the way that people think about the world.
The emphasis of this course will be team-based collaboration, with each team working to design and develop a game from the start to the end of the course. In support of this process, each team will progress through a structured sequence of challenges during lab time, as guided by the concepts that are discussed and practiced during class.
There is no course textbook, but you have access to several books in the library: Game Programming Gems 1 through 8 (various), GPU Gems 3 (Nguyen), and CryENGINE 3 Cookbook (Tracy). You also have access to Game Developer's Magazine (several years). There are also many helpful tutorials online, hosted by the makers of game engines like Unity, Unreal, and Godot.
Upon completion of the course, students should be able to:
The term will consist of three major events. On “Pitch Day” (December 1, morning), each student team will present their game idea to the class and receive feedback from a panel of judges (comprised of both their peers and industry professionals). On “Alpha Day” (December 8, morning), each student team will conduct an evaluation of a playable prototype of their game with their peers as test participants. On “Demo Day” (December 18, likely early evening), each student team will present their finished game demo and run a station where students and guests can play their game.
During week 1 of classes (November 27 to December 1), each student team is expected to analyze the design of some specific commercial games (TBD). Each team will hand in a short document discussing the results of these analyses (due by 18:00 on November 29).
During weeks 2 and 3 of classes (December 4 to 15), each student team is expected to demonstrate their activity on their project using the course project tracking software (Trello). All updates to Trello for a given work period are due by 7:00 on the weekday following that period (e.g., 7:00 on Wed for work done on Tue).
Before Alpha Day, each team is expected to write and submit an Alpha Testing Plan (due by 18:00 on Dec. 5). NB: Any team that fails to submit their Alpha Test Plan on time will be eligible to receive at most half of the maximum grades for both the Alpha Test Plan and Alpha Day.
On Demo Day, each team is expected to submit their game project for evaluation (due by 00:01 on Dec. 18), including all source code, assets, launch & gameplay instructions, and an attribution list for all found resources that they used.
After Demo Day, each student is expected to write and submit a Post-Mortem that gives their personal account of working on their team’s game (due by 23:59 on Dec. 19). Late submissions of Post-Mortems will incur a penalty of 15% per day including weekends and holidays.
|Game Analysis||Document (2-3 pgs)||1 per team||Wed Nov 29 (by 18:00)||3%|
|Pitch Day||Presentation||1 per team||Fri Dec 1 (morning)||7%|
|Daily Updates||Progress on Trello||n per team per day||Mon Dec 4 to Mon Dec 18 (by 7:00 daily)||5%|
|Alpha Test Plan||Document (1-2 pgs)||1 per team||Tue Dec 5 (by 18:00)||5%|
|Alpha Day||Testable Prototype & Alpha Test||1 per team||Fri Dec 8 (morning)||10%|
|Demo Day||Hand-in + Presentation & Public Demo||1 per team||Mon Dec 18 (Hand-in by 00:01, Demo Time TBA)||30%|
|Post-Mortem||Document (3-5 pgs)||1 per student||Tue Dec 19 (by 23:59)||20%|
Please use this course discussion system for posting questions regarding lectures or your projects, rather than sending us emails. That way we can build a shared repository of useful questions/answers (you can of course still send us emails, but consider first whether you can post things here instead).
On both Pitch Day and Demo Day, each team will deliver a presentation. During each presentation, each student will be graded individually on their presentation ability. For each student, the two resulting scores will have a combined weight of 5% on their final grade. The two scores (scorePitch and scoreDemo) will be combined as follows: if scoreDemo is higher than scorePitch, scorePitch will be ignored and the final score will be based entirely on scoreDemo. Otherwise, the final score will be based equally on both scores.
Please note that attendance during both morning and afternoon sessions is required. Please inform the instructors if this is hard for you for some reason, such as scheduling conflicts or sick leave.
The participation grade will be based on: (1) Attendance (both mornings and afternoons), and (2) Participation in online discussion. To the extent possible, this will also be based on how actively the student participates in in-class discussion (based on the instructors' subjective assessment).
The base participation grade will be calculated as 7.5 * (portion of mornings attended) + 7.5 * (portion of afternoons attended). The instructors can then add possible bonus points to this base grade based on a subjective evaluation of the student's participation throughout the semester (into which the online discussion may factor).
NB: To pass the course, it is necessary to earn a grade of at least 50% (i.e., 5/10) across all Individual Work (see calculation and table below). If a student's Individual Work Grade is less than 5/10, this grade will count as their grade for the entire course.
The student's Individual Work Grade will be calculated via the following formula:
Individual Work Grade = [(Participation Grade)*15% + (Student Speaking Grade)*5% + (Post-Mortem Grade)*20%] / 40%
|Part of Course||Total Weight|
|Alpha Test Plan||5%|