More like chapter 14.  Add two new labels. Game Over, Restart.  Add references in the GameController object too.   They are both blank at the start of the game.   They change when game over occurs.

That Works. You’ve got game!

Inside

You’ve seen it before.  Add these publics to the the GameController.

Then Add the components on the screen, then drag and drop.

Include UpdateScore() in the Start routine.

Outside

Make a public addscore routine in game controller

In any routine that needs to add a score, get a reference to the GameController, then at the right time, call the new routine. ( the AddScore() routines above doesnt match below, but  you get the picture.)

Music… Drag and drop the music to the GameController Object(play on awake, loop)

Drag and drop audio into the prefabs like explosion and you don’t have to program anything.

Then drag and drop the audio clip and confirm “play on awake” is checked.

That takes care of explosions. Now shooting.

Drag and drop the audio clip onto the player object.(no play on awake)

We a single control by adding loops

while(!gameOver)

for(i=0;i<#per4 wave; i++)

spawn rock

Part 2 – Removing those explosions after a few seconds

1.  Create a “DestroyByTime” Object
2. Attach that to the prefab for each of the explosions.

Game Controller (spawning waves)

It sits at the top of the game view as a new object with a script called “GameController”

At start it shoots off a random asteroid.  We will

Creat the script with two params (where to launch the asteroid) and what to launch(asteroid prefab)

Asteroid continued  – Now add pretty explosions including the fatal player collision.

Expand on the collision script…

To make it blow up by spawning an explosion

Using tag to identify Player,  and have it blow up

Then reuse the Movement code by dragging and dropping it onto the Asteroid. then setting speed in negative direction.

Create Opponent

1. Setup a template asteroid object (chapter 8)
2. Save it as a Prefab (chapter 9)
3. Expand programming so it happens in groups

Part 1

Create Placeholder Game Object called Asteroid(reset transforms, change z above player object so we can see them relative to each other)

Drag and drop the model for an asteroid into it(reset transforms)

[ This continues the pattern of Parent object holds the program, child is what to render.]

Back at “Asteroid” Add rigidbody(no gravity, no angular drag) , Capsule collider and scale it.

Back at “asteroid” add a new c# program with “start” routine so we can set a random tumble for the object when it starts

That takes care of start. But what about hit?  New Object for that that has a collider trigger like the boundary(but enter not exit variety)

So on the same “asteroid” object, create another c# script called DestroyByContact

Debug.Log(other.name);

Create a boundary around the game play area so the shots can be removed from play after they fall off the field.

1. Create a box larger than the play area
   1. Create Cube
   2. Scale it
   3. Make sure it has a box collider
   4. isTrigger is checked
   5. Remove the Cube(mesh filter)
   6. Remove the mesh renderer.
2. Create script(to handle the trigger) DestroyByBoundary
3. Edit and add the OnTriggerExit routine.  When triggered, it will destroy the other object.
4. Easy

Shooting shots.

Create an game object called “shotSpawn” as a child of our player.  This will become the origin for the shot when started, but we need a way to communicate between the object and the c# program, so we make a couple helpers

Edit “PlayerController”

Object:

Positon:

Rotation:

We need a way to fill those in.

In the c#

public GameObject shot; // what gets shot

public Transform shotSpawn; // the object to use to get the shot

In Unity

Make an empty game object called ShotSpawn as a child of the Player object. Adjust it to the tip of the nose.  This is where the initial location comes from.

Drag the bullet from the Prefabs into the new “shot” reference

Drag the ShotSpawn into the new shotSpawn reference

That is the setup.

Now to shoot.

Instantiate the shot when button is clicked (but include a pause) so we dont fire one every frame