In this book, you will find several headings appearing frequently.
To give clear instructions of how to complete a procedure or task, we use:
This section explains what you will build, with a screenshot of the completed project.
This section explains why the project is cool, unique, exciting, and interesting. It describes what advantage the project will give you.
This section explains the major tasks required to complete your project.
- Task 1
- Task 2
- Task 3
- Task 4, and so on
This section explains any pre-requisites for the project, such as resources or libraries that need to be downloaded, and so on.
This section explains any preliminary work that you may need to do before beginning work on the task.
This section explains how the steps performed in the previous section allow us to complete the task. This section is mandatory.
The extra information in this section is relevant to the task.
You will also find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text are shown as follows: " We can change the Tiling by calling the material.mainTextureScale function to set the X tile and Y tile."
A block of code is set as follows:
public var f_speed : float = 5.0; public var loopSprites : SpriteManager[]; private var in_direction : int;
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
if (hit.collider.tag == "Key") {
if (!b_hasKey) {
//We hit our Key
audio.volume = 1.0;
audio.PlayOneShot(getKeySound);
b_hasKey = true;
Destroy (hit.gameObject);
}
}New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Click on the Continue button to break the prefab."