Game0: Not Pong

Game0 is an warm-up to get you used to our base code and how small game assignments work.

Your goal is to start with a fork of the game0 base code and develop a new game that isn't pong.

What You Need To Do

• [1pt] Design Roll Call (in class, Thursday, August 29th).

  Answer roll call with a no-more-than-two-sentence summary of what you are making. A good structure for this is to establish a reference point and then say why your game is new. (E.g., "I'm going to make a snake-eats-apples game, but with gravity.")

• [2pt] Implementation (before class, Tuesday, September 3rd).

  Place a check-out of your game repository into the your turn-in folder on AFS (see below).

How To Do It

Design Roll Call

Real-world programming tasks rarely come with specifications, especially in the world of games. And the choices you make in your game design can really influence how much work you'll be doing in the game code. We have design roll call to make sure you are thinking about this. You roll-call design is non-binding -- the game you turn in does not need to match it.

Implementation

For this assignment you should first get the base code working on your system, and then modify it to implement your new game. More detailed steps:

1. Fork the base0 code as a starting point. The NEST.md file in the repository explains how to set up your development environment to use the code.
2. Modify the code to implement your game.
3. Fill in the missing sections in README.md to document your project; replace screenshot.png with a screenshot of your game.
4. Place a checkout of your game repository into your AFS turn-in folder at /afs/cs.cmu.edu/academic/class/15466-f19/game0/ANDREWID/turn_in.