This is your last project in CS151! It will be more open ended than the previous projects. The goal is to create a video game using turtle. Be creative and have fun!

• Project 11: Video game
  • 1. Create a video game
    • Project with no planned extensions
    • Project with planned extensions
      • Option 1: Better Asteroids
      • Option 2: New Game
        • New Game Guidelines
      • Game Demo
  • 2. Written Report
    • a. Abstract
    • b. Design
    • c. Implementation
    • c. Gameplay testing
    • d. Conclusion
    • e. Sources and collaborators cited
    • f. Gameplay demo
  • Extensions
  • Congratulations!
    

---

1. Create a video game

You have several options for your final project in CS151, depending on whether you intend on doing extensions.

Project with no planned extensions

To complete the base project expectations, you should "finish" the previous project and fully implement asteroids. In particular, this means implementing:

• A title screen with a button to start the game and instructions on how to play the game (including keyboard controls).
• The ability to shoot the asteroids.
• A loss screen if the ship hits an asteroid.

You should submit:

• Your code
• Your written report (see 2. Written Report)

Project with planned extensions

You will be graded on:

• Your code (pick Option 1 or Option 2 below)
• Your written report (see 2. Written Report)
• In-class game demo (see Game Demo)

Option 1: Better Asteroids

Implement Asteroids as described above, but include a few other features. See Extensions below for some ideas. Be creative, but keep it simple.

If you did extensions for Project 10 you can include the implementations this week, but they will not be counted as extensions this week.

Option 2: New Game

Implement a game other than Asteroids, using inheriting from the provided Abstract Class Game. The more detail, gameplay elements, and/or complexity the more extension credit. As usual, code organization and design play a big role and you should follow the standard best practices.

Your game should inherit from the Abstract Class Game. From a grading perspective, I should not see lots of duplicate code in Game and your other game class. Make use of inheritance and extend the basic game mechanics if it makes sense!

New Game Guidelines

• Keep it simple!
• Your game should have a start screen, end screen and interactivity.
• Before you start coding, design your game. Your design does not need to be "final", but you should at least roughly outline the main game elements before driving in. I suggest breaking things down through top-down design.
• Follow the design pattern from projects where you repeatedly test your game as much as possible. Use top-down design! Do not wait until the very end of your implementation to start testing! That's overwhelming! Always think about places where you can test modular pieces of your implementation before you add many moving parts together, any one of which might have bugs.
• You should use object-oriented design. If you find it useful to create additional parent and child classes, feel free to do so!

Game Demo

Everyone doing extensions will be expected to demo your work to the class on Friday December 8th. The goal is to have fun and give us an opportunity to celebrate your work!

• Your presentation should be limited to 2 minutes or less.
• Your demo should be informal: you should walk us through your game as you play it, explaining what you designed and briefly outlining key design decisions. You do not need to show us any code.
• Please let me know that you plan on presenting by Wednesday December 6th. This will give me time to organize the presentation schedule.

---

2. Written Report

In addition to submitting your code, you will be expected to include at least the following elements in the report. Your report should be about the same length as a usual project report.

a. Abstract

The usual abstract — summary of what you made and what concepts you used to do it.

b. Design

Write whether you completed the base game (no extensions), asteroids with extensions or a new game.

If you completed asteroids with extensions, describe the extensions that you completed.

If you implemented a different game, describe the game. Explain how the game is played and what the rules are. Include links to relevant resources about the game.

Extensions that you completed for Project 10 will not be counted as extensions this week.

c. Implementation

Describe your implementation — how you organized your code (e.g. key classes, important methods) and made key parts of the game work (e.g. events, how you solved problems to get key elements of your game working). This should be somewhat similar to the typical Results section of project reports.

d. Gameplay testing

Explain how you tested the gameplay in your report, and describe any modifications you made to the program after having someone else try to use it.

This means playing your game! Iteratively refine the controls, rules, difficulty, and artwork. Try to partner with someone and test each other's implementations. Discuss how to improve your programs to make them more responsive or interesting or fun.

No one writes perfect code the first time! If you don't change anything after someone else uses your program, you probably aren't listening to feedback closely enough.

e. Conclusion

The usual section.

f. Sources and collaborators cited

Please provide URLs and sources for any images and artwork you used in your game. This is important and points will be taken off if these citations are missing in your report.

Also cite the usual including students, TAs and faculty you discussed your code with and websites you used as reference.

g. Game Video/Image Documentation

Include in your project submission ZIP file a maximum 90 second screen recording video of you playing and demoing your game. This should include the start screen, game play, and results screen.

In your report, include at least three still images (Required Images 1, 2, and 3) — one image for each phase of your game: start, main, and end.

Link to detailed turn in instructions and more information about what should be contained in the report

---

Extensions

• Update your asteroids implementation to inherit from the Abstract Class Game.
• Prevent the player/enemies from leaving the screen boundaries.
• Add and maintain a score.
• Make enemies move along linear or prescribed paths.
• Spawn new enemies periodically.
• Create a type of enemy that requires more than 1 bullet fired by the player to vanish.
• Add obstacles / barriers.
• Make the background artwork change or an element in it move when the player moves to a special location.
• Make your program replayable so the user can return to the start screen from the final screen and replay the main phase.
• Make your program/game have more than one level.
• Add a two-player mode
• Add a physics engine to your game. You could simulate the way that gravity (easy), momentum, and/or spring forces and damping (impressive!) would influence the motion of objects on your screen.

Congratulations!

Congratulations on your first video game! Thank you for your hard work and creative problem solving this semester. It’s been an honor to work with you, and I hope to see you again in other CS courses in the future. 😃

---