Implementing Points, Jumps, and UI

Refer to About the Challenges and Solutions for more information about readings of this type.

For this challenge, you will complete and submit your project for review and grading by your peers. Before starting the peer review, be ready to implement the required features in your project:

Shooting Asteroids should earn the player points. When an Asteroid is smaller, it should be worth more points, as outlined in the Requirements Doc.

When the PlayerShip collides with an Asteroid, the PlayerShip should disappear (it teleports away from danger) and reappear in a safe section of the screen after a short time (a Jump). When the PlayerShip jumps, the number of Jumps remaining should be depleted. When the PlayerShip jumps, the Asteroid that hit the PlayerShip should be destroyed, and the children of that Asteroid should be promoted to top-level Asteroids (as in the previous challenge). When the PlayerShip collides with an Asteroid with 0 Jumps remaining, the Player Ship should be destroyed. When the PlayerShip is destroyed, the game should end and the Scene should reload after a short delay.

The HUD should show the number of Jumps remaining The HUD should show the Current Score Be sure to implement the 9-slice boxes around each Text field

Use professional scripting practices, such as descriptive method names and comments, to make sure your code is easy to read by other programmers. Use professional scripting practices, such as descriptive method names and comments, to make sure your code is easy to read by other programmers.