![]() My game necessitates of a programmed objected shooter which constitutes with spawned Zombies “coming at you” non-stop until you run out of health and you obtain your high-score for the various zombies you have killed. The planning of my Java set game is to develop the enjoyment of Zombie survival arcade games that requires acknowledgement and the endlessness of high scoring gratification. Design is very important for developing computer games because it’s critical to how you format your game so you know what you’re working with. zip the entire scenario folder "asteroids-3", and rename the zip file as "JohnDoeHw9.zip", where John Doe needs to be replaced by your first and last name submit the zip file John Doe Hw9.zip to Moodle "homework 9 drop box”.For my design, I will create my Zombie survival arcade game which will include the formatting of narrative, pseudo-coding, flowcharting, action listing and graphical tooling using the Java software Greenfoot that has been required to be utilised. O The solution of them should co-exist in one project, and you don't need to comment out the solution for one or the other exercise. you can finish exercise 9.69 first, and then work on 9.70. This final score screen will show up after the rocket collides with any asteroid thus causing the game to end. to satisfy the requirement of exercise 9.69, you need to update the score counter on the lower left corner of the screen, and you need to display the correct score value in the final score screen. o For example, there should be a higher score for removing the last piece of an asteroid, compared to splitting an asteroid into smaller pieces. you should have reasonable scores for splitting asteroids and removing the last piece, respectively. If your code of calculating how many asteroids are left is placed directly in the act() method of a class, that means in every act() cycle your code of calculating remaining asteroids will run, and that is not considered efficient. ![]() For example, in exercise 9.70, you should insert the block of code for calculating how many asteroids are left in the world background, only at the place where it is necessary. And in this homework, you will have a chance to use generic programming, such as List o With homework #8 and #9, you have applied all the OOP principles and context into your won coding practice. In the previous homework, hw #8, you have applied all OOP principles and all the context of polymorphism, except for generic programming (static binding). for exercise 9.70, you may need to consider making use of the generic class type List. for exercise 9.69, you need to read the source code in class Counter, and find out which method to call in class Counter, in order to add a new score to the current counter value.provide the solution by modifying class Space and class Asteroid. It requires you to open the existing Greenfoot scenario folder "asteroids-3", and then modify its source code. work on these two exercises in textbook: 9.69 and 9.70. ![]() Follow the steps below to finish homework 9: CS2163 Java Homework 9 requirement Homework 9 needs to be finished on the Greenfoot platform. Maybe you get higher scores in later levels. Every time the asteroids are cleared, you go up a level. So in the second round, there are three asteroids, in the third round four, and so on. Maybe the game should start with just two asteroids, and every time they are cleared away, new ones appear, one more every time. Exercise 9.70 Add new asteroids when all have been cleared. Call this new method from the Asteroid class whenever an asteroid gets hit (you may want to have different scores for splitting the asteroid and removing the last little piece). This method should add a score to the score counter. To make the scoring work, you will have to do roughly the following: Add a method to the Space class named something like countScore. The counter is defined in class Counter, and a counter object is being created in the Space class. You have seen that there already is a score counter, but it is not being used yet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |