In this class, we made a bunch of small games, which you can see here:
We also produced seven final games, which are linked below. You can also check out the trailer.
Computer Game Programming will help you build the programming skills needed to turn ideas into games. This means we'll be covering both runtime systems and the asset pipelines to fuel them, along with some game-design exercises (with an eye to thrifty code).
Previous years with similar content: Game Programming '19, Game Programming '18, Game Programming '17, Game Programming '09.
Students will be graded out of 20 + 3N + 3 points, divided as follows:
You will be reading lesson materials asynchronously, then discussing the material in class; there is a small number of points associated with completing in-lesson exercises. Small games will be assigned roughly weekly to highlight basic game-related functions. The Final Game will be larger undertaking by groups of 3-4.
There are no late days; however, there is enough slack in the grading to support completely missing one small game.
Being sick isn't fun. University health services often has flu vaccine available starting in September (though this year things may work a little differently). Your standard anti-SARS-CoV-2 measures might also work well against influenza.
Mental health is an important aspect of physical health. CMU's CaPS services exist to help you manage your mental state.
If you have a disability and are registered with the Office of Disability Resources, I encourage you to use their online system to notify me of your accommodations and discuss your needs with me as early in the semester as possible. I will work with you to ensure that accommodations are provided as appropriate. If you suspect that you may have a disability and would benefit from accommodations but are not yet registered with the Office of Disability Resources, I encourage you to contact them at email@example.com.
Using other people's code or data without giving credit is a form of plagiarism. Plagiarism is an immoral activity that I take very seriously. If you plagiarize, you will fail the class, and I will do my best to make sure you are removed from CMU entirely.
All you need to do to avoid plagiarism is to make sure to give credit for the code and data you use in you project.
Something as simple as the comment "
//based on https://wiki.libsdl.org/SDL_CreateWindow" can save your academic career from ruin.
Additionally, most human-created works are covered by copyright and thus subject to some sort of license agreement. Make sure that code and data you use has a license agreement compatible with this course. For example, I am unwilling to pay for a license for a library so I can compile your code, or sign a non-disclosure agreement so I can read it.
This is a course that involves writing a lot of code. Please, by all means, work together!
The course does not have a textbook. However, there are several documents available on the internet that you may find useful:
There are also some great, cross-platform content-creation tools that we will use in our asset pipelines:
And some places to get free game assets:
(NOTE: schedule subject to change.)