https://github.com/binghamtonuniversity-cs110/final-project-fall18-null
https://docs.google.com/presentation/d/1AVce37pHPzFCRRY02xs4VrK7y-_1ZnEUsCldTv6Gjgo/edit#slide=id.p
Our project is a galaxy shooter type of game. One player is controlling a ship that will shoot a bullet each time they press the spacebar while enemies fire back. The player must avoid the enemy shots. In total there will be three different repeating waves of enemy fighters, and each wave increase in difficultly; for example the third enemy wave will be able to shoot three bullets going in different directions at once. Defeating an enemy is also worth a certain amount of points based on the wave it is from. For example defeating an enemy from the first wave is worth one point, defeating an enemy from the second wave is worth three points, and defeating an enemy from the final wave is worth five points. The goal of the game to get as many points as possible, and at the end the player will be presented with the amount of enemies they defeated and their high score. The player has three lives total, and will lose a life if they are hit with an enemy bullet, if they collide with an enemy or if the enemy reaches the other side of the screen without being defeated. The game is over when the player loses all three lives.
- Main Menu Screen
The start screen is the first thing the user sees. There will be two options that will allow the user to either start playing the game (“Play”) or exit the game (“Quit”).
(Add GUI concept)
- Gameplay Screen
This screen is where the game takes place. The enemy ships will immediately begin generating once the user presses “Start” on the Main Menu screen. The first wave of enemy ships will move straight and left, and shoot bullets that shoot straight ahead. The second wave of enemy will move up and down and also shoot bullets that move left and straight. The final wave of enemy ships will generate and shoot three bullets at once, one moving up, one moving down and one moving straight ahead. If the hero ship hits the enemy with a bullet the enemy will disappear. The hero ship loses a life if it is hit by a bullet, collides with an enemy ship, or if an enemy ship reaches the opposite end of the screen without being defeated by the hero ship. If the hero ship loses three lives, the game is over; the amount of remaining lives the hero has will be displayed on the gameplay screen.
(Add GUI concept) 4. Game Over Menu
This screen will appear when the hero ship loses all its lives. The user be presented with the number of enemies they defeated, their high score and the option to start the game over by clicking “Play Again” or exit the game by pressing “Quit”.
(Add GUI concept)
Pygame (https://www.pygame.org/) - A module set incorporating many common game development functions into python, developed by Pete Shinners and Pygame Community. Includes crucial graphical elements as well as a musical playback functionality.
Controller- a class that defines the “rules” and logic of the interlocking relationships between the other classes and UI, as well as establishes the data permanence of the high score and opening the main menu, the gameplay screen, and the game over menu. Defines how the game updates based on which key is pressed; for example how and when the hero ship moves and shoots when the user presses the arrow keys or space buttons, or whether or not the background music is playing if the user presses "x" or "s". This class also keeps track of the user's health count, the numbers of enemies that are defeated, and when each wave of enemies begins to randomly generate.
Hero- a class that defines the hero ship; an image of a ship that can move left, right, up and down, and takes damage or loses a life whenever it collides with a bullet. The class also defines the size and speed of the image.
herobullet- a class that defines the bullets that the hero ship is shooting out. This class also defines the size and speed of the image of the bullet, as well as its starting location relative to the hero ship.
enemyBullet- a class that defines the bullets that the enemies are shooting out; the class also defines the size and speed of the image of the bullet, as well as its starting location relative to the enemy.
enemy1- a class the defines the first wave of enemies. The first wave of enemies has two functions: to move left as the screen updates and to fire enemy bullets moving in the left direction that are faster than the enemy ship is.
enemy2- a class the defines the second wave of enemies. The second wave of enemies has two functions: to move leftward in the direction of a sin curve as screen updates and to fire enemy bullets moving in the left direction that are faster than the enemy ship is.
enemy3- a class the defines the third and final wave of enemies. The third wave of enemies has two functions: to move leftward in the direction of a sin curve as screen updates and to fire three enemy bullets. All three enemy bullets will move faster than the enemy ship, however one bullet will move leftward and straight and the other two will move leftward and diagonally.
- Decide upon a class interface for the classes in your project.
- A simple drawing that shows the class relationships in your code (see the sample Proposal document for an example).
- This does not need to be overly detailed, but should show how your code fits into the Model/View/Controller paradigm.
- You should have a list of each of your classes with a description.
Worked to develop methods of testing and writing the Acceptance Test Procedure. She has also worked to update the README as the logistics of the project have been determined, and worked with the Front End Specialist and Back End Specialist on developing general concepts and ideas for the program. In addition, she implemented sound effects to the controller model to add background music fighting and video game sound effects to the program.
Front-end lead used her knowledge on pygame to create and edit visual aspects of the game, such as buttons, sprites, on-screen text and sprites. She used this information to design and program a consistent UI to help the player navigate the title screen, the the gameplay screen, and the “GAME OVER” screen. In addition to implementing a majority of the visual elements in the methods, she also collaborated with the Back End Specialist to fix any errors and bugs that presented itself when developing the program.
The back end specialist developed the “Model” portion of the program by writing the major classes that would be used in the main game, as well as incorporating pygame preformance into each other them. He was also responsable for establishing basic and essential game mechanics, such as the shooting function in both the hero and enemy ship, the movement of the enemy ships, and the size and speed of all sprites. He worked on the implementation of the classes into the Controller file, which he worked on partially with the Front End Specialist.
First we run Controller() and ensure that the Main Menu opens normally and is functional; the background music should immediately begin playing We will click the “Start” button to make sure the actual gameplay screen opens and begins immediately generating enemies that shoot bullets. Then we will toggle sound effect by using the “x” and “s” keys. Clicking “x” should turn off sound and “s” should turn sound back on. Next we will press and hold the right arrow to make sure hero ship moves in the right direction. We will repeat this process using the left arrow, the up arrow and the down arrow to make sure the hero ship moves left, up and down respectfully. Then we will press the spacebar to test to see if the hero ship expels a bullet that move straight and forward; a shooting sound effect should also play normally.
When testing gameplay, we have to make sure that enemies “die” or disappear when the colliding with the hero ship’s bullet. The hero ship must also lose a life each time it is shot at, when it collides with the enemy, or when the enemy exits off the opposite end of the screen. The amount of lives the hero ship has left will be indicated with a “live left” countdown visible constantly on the gameplay screen. After 30 seconds a different wave of enemies must also appear on the screen, with three waves total. The first wave of enemies should shoot bullets that move straight, the second wave should shoot bullets that move up and down, and the third wave should shoot three bullets at once. Background music should remain constant during gameplay, and whenever the hero ship defeats an enemy, collides with an enemy or collides with an enemy bullet an explosion sound effect sound begin playing.
When the hero ship loses all three lives, the Game Over Menu should open normally and display the words “Game Over”, the amount of enemies they defeated during gameplay and the player's high score. Each button on the Game Over Menu should be functional, including “Play Again”, which relaunches the game, and “Quit”, which quits the game with no problems.
We will reopen the game to make sure the “Quit” button on the Main Menu page quits the game successfully. Finally we will click the “X” button in the top right corner of the window to make sure the game quits properly. This concludes the testing protocol.
| Step | Procedure | Expected Results | Actual Results |
|---|---|---|---|
| 1 | Run Controller() | 1) Main Menu opens normally and is functional 2) Background music begins playing | |
| 2 | Click “Start” button | When “Start” is pressed the game screen opens and enemies begin generating/shooting at hero | |
| 3 | Click “x” button | Background music stops playing | |
| 4 | Click “s” button | Background music begins playing | |
| 5 | Press RIGHT ARROW, hold RIGHT ARROW | The hero ship moves in the right direction without exiting the screen | |
| 6 | Press LEFT ARROW, hold LEFT ARROW | The hero ship moves in the left direction without exiting the screen | |
| 7 | Press UP ARROW, hold UP ARROW | The hero ship moves in the up direction without exiting the screen | |
| 8 | Press DOWN ARROW, hold DOWN | The hero ship moves in the down direction without exiting the screen | |
| 9 | Press SPACE BAR | 1) The hero ship shoots out a bullet that shoots straight and forward 2) Shooting sound effect begins playing | |
| 10 | General playtesting | 1) Enemies “die” or disappear when the hero shoots at them 2) The hero ship loses a life each time it is shot at, as indicated by the “lives left” countdown on the gameplay screen 3) If the enemy collides with the hero ship, the hero ship loses a life 4) If the enemy exits to the opposite end of the screen, the hero loses a life 5) After 30 seconds a different wave of enemies begins generating 6) The first wave of enemies should shoot bullets that move straight, the second wave should shoot bullets that move up and down, and the third wave should shoot three bullets at once 7) Explosion sound effect begins playing whenever the hero ship bullet collides with an enemy ship, when the hero ship and an enemy ship collides, or when a hero ship and an enemy bullet collide | |
| 11 | Game Over Menu | 1) When the hero ship loses all three lives the game over menu opens normally and is functional 2) A game over sound effect should begin playing normally | |
| 12 | Test each button on the Game Over Menu | 1) Menu displays the words “Game Over” as well as a “Play Again” button and a “Quit” button 2) Menu also displays the number of enemies the hero ship successfully defeated during gameplay and the player's high score 3) “Play Again” relaunches the game with no problems 4) “Quit” quits the game with no problems | |
| 13 | Re-open game to test QUIT buttons on MAIN MENU pages | When “Quit” is pressed the game quits successfully | |
| 14 | Click red “X” button in top right corner of window | Game closes out properly |