Game Development Reference
In-Depth Information
Reflecting on our code changes
Before we can test our code properly, let's reflect on what we have done. While we
have made our game framework more flexible and extensible, we have also broken
some assumptions from before that need repairing as discussed in the following
points:
• The
MissionManager
class has been renamed to
Game
. This means that all
scripts that used to do a
GameObject.Find("MissionManager")
need to
be updated to
Find("Game")
.
• We have separated some objects into the
MAIN
scene and some into the
LEVEL1
scene. This means that objects that have a reference to an object
that is now in another scene will be broken. To repair these, we need to modify
the code for the object in the scene. See
SetupSceneOne
for an example of
this.
