Syllabus
This course picks up where Harvard College’s CS50 leaves off, focusing on the development of 2D interactive games. Students explore the design of such childhood games as Super Mario Bros., Legend of Zelda, and Pokémon in a quest to understand how video games themselves are implemented. Via lectures and hands-on projects, the course explores principles of 2D graphics, animation, sound, and collision detection using the LÖVE framework and Lua programming language. By class’s end, students will have programmed several of their own games and gained a thorough understanding of the basics of game design and development.
Prerequistes
CSCI E-50, CS50x, or prior programming experience in any language.
Instructors
Colton Ogden
cogden@cs50.harvard.edu
David J. Malan
malan@harvard.edu
Schedule
subject to change
| lecture | section | office hours | assignment due | |
|---|---|---|---|---|
| Pong | 6/24 | 6/26, 6/27 | 6/28 | 6/30 |
| Flappy Bird | 7/1 | 7/3, 7/4 | 7/5 | 7/7 |
| Match 3 | 7/8 | 7/10, 7/11 | 7/12 | 7/14 |
| Super Mario Bros. | 7/15 | 7/17, 7/18 | 7/19 | 7/21 |
| Legend of Zelda | 7/22 | 7/24, 7/25 | 7/26 | 7/28 |
| Pokémon | 7/29 | 7/29, 7/30 | 7/31 | 8/4 |
Lectures
Pong on 6/24
- Lua
- LÖVE2D
- Basic OOP (Object-Oriented Programming)
- Drawing Shapes
- Drawing Text
- DeltaTime and Velocity
- Game State
- Box Collision (Hitboxes)
- Sound Effects (with bfxr)
Flappy Bird on 7/1
- Images (Sprites)
- Infinite Scrolling
- “Games are Illusions”
- Procedural Generation
- State Machines
- Music
- Mouse Input
Match 3 on 7/8
- Anonymous Functions
- Tweening
- Timers
- Solving Matches
- Procedural Grids
- Sprite Art and Palettes
Super Mario Bros. on 7/15
- Tile Maps
- 2D Animation
- Procedural Level Generation
- Platformer Physics
- Intro to AI
- Powerups
Legend of Zelda on 7/22
- Top-Down Perspective
- Infinite Dungeon Generation
- Events
- Hurtboxes
- Screen Scrolling
- Data-Driven Design
Pokémon on 7/29
- StateStacks
- GUIs
- Turn-Based Systems
- RPG Mechanics
Expectations
You are expected to
- watch six lectures online,
- submit six assignments online, and
- submit one final project online.
Grades
Final grades will be based on assignments (90%) and the final project (10%).
Lectures
Via lectures are the course’s concepts introduced every week.
Sections
Lectures are supplemented by weekly, 90-minute sections led by the teaching fellows, led both online and in person. Sections are an opportunity to discuss the course’s material, ask questions, and explore related material.
Office Hours
Office hours are opportunities for guidance and feedback from the staff on assignments as well as for discussion of the course’s material more generally.
Homework
Homework comes in the form of small weekly assignments, for which the goal is to modify the game demonstrated in class that week in some way.
Academic Honesty
This course’s philosophy on academic honesty is best stated as “be reasonable.” The course recognizes that interactions with classmates and others can facilitate mastery of the course’s material. However, there remains a line between enlisting the help of another and submitting the work of another. This policy characterizes both sides of that line.
The essence of all work that you submit to this course must be your own. Collaboration on assigned projects is not permitted except to the extent that you may ask classmates and others for help so long as that help does not reduce to another doing your work for you. Generally speaking, when asking for help, you may show your code to others, but you may not view theirs, so long as you and they respect this policy’s other constraints. Collaboration on the course’s final project is permitted to the extent prescribed by its specification.
Below are rules of thumb that (inexhaustively) characterize acts that the course considers reasonable and not reasonable. If in doubt as to whether some act is reasonable, do not commit it until you solicit and receive approval in writing from the course’s heads. Acts considered not reasonable by the course are handled harshly. If the course refers some matter for disciplinary action and the outcome is punitive, the course reserves the right to impose local sanctions on top of that outcome that may include an unsatisfactory or failing grade for work submitted or for the course itself. The course ordinarily recommends exclusion (i.e., required withdrawal) from the course itself.
If you commit some act that is not reasonable but bring it to the attention of the course’s heads within 72 hours, the course may impose local sanctions that may include an unsatisfactory or failing grade for work submitted, but the course will not refer the matter for further disciplinary action except in cases of repeated acts.
Reasonable
- Communicating with classmates about projects in English (or some other spoken language).
- Discussing the course’s material with others in order to understand it better.
- Helping a classmate identify a bug in his or her code at office hours, elsewhere, or even online, as by viewing, compiling, or running his or her code, even on your own computer.
- Incorporating a few lines of code that you find online or elsewhere into your own code, provided that those lines are not themselves solutions to projects and that you cite the lines’ origins.
- Sending or showing code that you’ve written to someone, possibly a classmate, so that he or she might help you identify and fix a bug.
- Sharing a few lines of your own code online so that others might help you identify and fix a bug.
- Submitting the same or similar work to this course that you have submitted previously to this course, CS50 AP, or CS50x.
- Turning to the web or elsewhere for instruction beyond the course’s own, for references, and for solutions to technical difficulties, but not for outright solutions to projects.
- Whiteboarding solutions to projects with others using diagrams or pseudocode but not actual code.
- Working with (and even paying) a tutor to help you with the course, provided the tutor does not do your work for you.
Not Reasonable
- Accessing a solution to some project to (re-)submitting your own.
- Asking a classmate to see his or her solution to a project before (re-)submitting your own.
- Decompiling, deobfuscating, or disassembling the staff’s solutions to projects.
- Failing to cite (as with comments) the origins of code or techniques that you discover outside of the course’s own lessons and integrate into your own work, even while respecting this policy’s other constraints.
- Giving or showing to a classmate a solution to a project when it is he or she, and not you, who is struggling to solve it.
- Paying or offering to pay an individual for work that you may submit as (part of) your own.
- Searching for or soliciting outright solutions to projects online or elsewhere.
- Splitting an assigned project’s workload with another individual and combining your work.
- Submitting (after possibly modifying) the work of another individual beyond the few lines allowed herein.
- Submitting the same or similar work to this course that you have submitted or will submit to another.
- Submitting work to this course that you intend to use outside of the course (e.g., for a job) without prior approval from the course’s heads.
- Viewing another’s solution to a project and basing your own solution on it.