1st Ed – Errata – Mastering Unity 2D Game Development

Page

Ch 2/3/6

Error

The code “MonoBehavior” where it should be MonoBehaviour. The former is invalid code.

Correction

MonoBehavior spelling updated in affected areas document

Page

Ch 2/3

Error

Typos: Under the heading “Controlling the hero”, step 1:
“1. Add a RidgedBody2D component by navigating to Add Component | Physics2D
| RidgedBody2D in the player’s GameObject inspector.”

Correction

References to RidgedBody should be RigidBody

Page

From Chapter 7

Error

The GameState.CurrentPlayer property is named incorrectly in scripts

Correction

Rename: currentPlayer
To: CurrentPlayer
Wherever it is found

Page

From Chapter 7

Error

The GameState.PlayerReturningHome property is named incorrectly in scripts

Correction

Rename: playerReturningHome
To: PlayerReturningHome
Wherever it is found

Page

9

Error

Typo: Last paragraph, first sentence of page 9, the word “also” is misspelled.

Correction

Should just be “also”

Page

18

Error

Incorrect website address on page 18, in the 5th paragraph starting: “If you want to see a great comparison between the 2D and 3D physics systems, refer to this excellent post at…”

Correction

Correct URL should be:
http://x-team.com/2013/11/unity3d-v4-3-2d-vs-3d-physics/

Page

24

Error

The provided URL address redirects to new website:

Correction

Target site has updated, new URL is:
http://www.mono-project.com

Page

25

Error

Incorrect URL – on page 25, 1st paragraph, 3rd sentence:

The provided URL of:
http://Unity.com/unite/archive/2013

Should be corrected to:
http://unity3d.com/unite/archive/2013

Correction

Correct URL should be:
http://unity3d.com/unite/archive/2013

Page

55

Error

The screenshot Box Collider 2D, Size, X value doesn’t match the same value we were told to change it to (previously on page 54) – as the screenshot is intended to be used to verify all settings are correct.

Correction

Screenshot being updated.
Correct value is “X (0.41)”

Page

70-73

Error

The “Animator Dope Sheet” diagram at the bottom of page 70 is numbered, but those numbers then aren’t used anywhere following. I.e.. They aren’t then used to refer back to the diagram in the headings/text that describe it on pages 71-73. (Not sure if this is intentional – but otherwise, why specifically number the diagram?)

Correction

The Proceeding headers are ordered as per the bullets.
Update will have numbered headings

Page

76/55

Error

The image shows Fixed Angle as unchecked even though the text on the previous
page says you should check it.

Correction

Screenshot being updated.
Fixed Angle should be checked
(Else player falls over on hitting non trigger colliders J)

Page

80

Error

Code typo: On page 80, in the Update() function, the following line has a typo (missing word “float”) at the start of the line:
movePlayerVector = Input.GetAxis(“Horizontal”);

Correction

Code block on Page 56 updated to include a new variable:
float movePlayerVector;
Which fixes this script.

Page

80

Error

Code error: On page 80, the first 3 lines of code use “PlayerSprite” – however, “PlayerSprite” has not (yet) been created anywhere (and is first used on page 81 when the Player game object is renamed to “PlayerSprite”).

Correction

Ignore / remove the PlayerSprite reference in this script.  It’s added later

Page

81

Error

Typos/wrong names: On page 81, in the step 5 paragraph at the bottom of the page there are several typos – “MovementController” and “RigidPhysics2D” (the names don’t correspond with Unity or other instances in the book):

“Remove the MovementController, RigidPhysics2D, and Box Collider scripts from the PlayerSprite game object and add them to the Player game object again.”

Correction

Updated to:
“Remove the CharacterMovement script, RigidBody 2D and Box Collider 2D components from
the PlayerSprite game object and add
them to the Player game object again.”

Page

112

Error

Code typo: On page 112, the 10th line of code is intentionally commented out at this stage – but this means that the curly bracket “}” at the end of the line is ignored – so we don’t see the “Stay” button at all.

Correction

Trailing } bracket should be ignored

Page

115

Error

Code/Tag naming for “The Cave” both need to be identical.
The last line of page 115 asks the reader to update the tag for “The Cave” to “Cave01”, but the relating code says (line 7 on page 116) { “Cave”, “The deep dark cave”}

Correction

“Cave01” should read as “Cave”

Page

116

Error

Code issue – to enable code compilation : When creating the NavigationManager.cs script on page 116, we need to alter the 2nd line from:
using System.Collections;
to
using System.Collections.Generic;
(otherwise the code won’t compile due to the use of “Dictionary”).

Correction

Updated using statement to:
using System.Collections.Generic;

Page

132

Error

Typo: After the code at the top of the page, the next sentence has an unnecessary word “this”:

“The preceding code is just a very basic singleton implementation, which you can
attach this to any game object in the scene.”

Correction

The word “this” should be ommited

Page

133/122

Error

This line in error when uncommented
//Application.LoadLevel(1);}

Correction

Trailing } bracket should be ignored

Page

137/116

Error

This snippet needs to start with.
using System.Collections.Generic;
Else Dictionary can’t be used.

Correction

Using statement shold be added to start of script:
using System.Collections.Generic;

Page

149

Error

Tip states that:
“Coroutines, by default, do not run the same thread as the normal game”
This is incorrect.

Correction

Line should read:
“Coroutines, by default, run the same thread as the normal game”
Note: Coroutines are not Threaded and run on the same thread (processor) as the Unity game loop. if used incorrectly they can kill your game.

Page

150

Error

Typo: On page 150, remove the typo word “a” from the 1st sentence after the diagram:
“The benefit of this is that you can wait for the last update or draw a cycle to finish before running your process.”

Correction

Line should read:
“The benefit of this is that you can wait for the last update or draw cycle
to finish before running your process.”
Ommiting the extra “a”

Page

155

Error

Typo – missing word “Folder” : On page 155, in the paragraph after the first section of code, 4th sentence of paragraph – I believe the word “folder” should be included in the sentence.

Correction

Sentence reworded, the sentence should now read
“Create a new script named PositionManager in the Editor folder under
Assets\Scripts (create it if it does not exist yet) and replace its contents with the following code:”

Page

163

Error

On page 163, the Layer name differs from that used previously: 1st bullet point:
“If you put Greybeard on the Character layer as I have done, the player will
appear behind him.”
This makes sense – but the “Character” layer has been named the “Player”
layer previously.

Correction

Text should read (image is correct)
“If you put Greybeard on the Player (format player KeyWord) layer as I have done, the player will
appear behind him.”

Page

177

Error

Unable to add NPC script to NPC GameObjects,  error returned by editor

Correction

Replacement NPC script should be implemented as follows:
using UnityEngine;
public class Npc : MonoBehaviour
{
public string Name;
public int Age;
public string Faction;
public string Occupation;
public int Level;
}
Will work as expected now

Page

209

Error

4th paragraph after “Transitions” heading, 1st sentence. The script FadeinOutManager should be created in the Assets\Scripts folder (not Assets as stated in the book). This matches the script’s location in the code download project for Chapter 6 – and it makes more sense to have the script in the actual script folder! The book version is:

“So, create a new FadeinOutManager C# script in the root of your project’s
Assets folder and replace its contents with the following code to create a
singleton manager that can be used by any scene:”

Correction

Reworded as requested by reader
“So, create a new FadeinOutManager C# script in your project’s Assets\Scripts
folder and replace its contents with the following code to create a singleton
manager that can be used by any scene:”

Page

209

Error

What page in the book does this errata appear?: page 209
Please describe the errata.:
Code missing: (2 lines missing compared with code download) for
“FadeinOutManager” section at bottom of page 209:
Code download has these 2 lines of code missing…

using UnityEngine;
using System.Collections;

Correction

Add the following using statements to the top of the new FadeinOutManager script
using UnityEngine;
using System.Collections;

Page

212

Error

Code case typo: On page 212, penultimate line of code:

“Fading = false;”

should be

“fading = false;”

Correction

Reword code line to:
fading = false;
(Lower case f for the variable Fading)

Page

213/214

Error

On page 213-214: Duplicated code function (and different versions of
preceding paragraphs for later “FadeToLevel” section – one of which is
included in error): The code section for StartFade is included in the book
twice – once at the bottom of page 213, then again as the first code block on
page 214.

Correction

Ignore duplicate code, it will be removed and tidied up in 2nd edition

Page

238

Error

StartCoroutine call using method name should include parenthesis

Correction

Replace the following line in the Start method
“StartCoroutine(SpawnEnemies);”
With the following
“StartCoroutine(SpawnEnemies());”

Page

262

Error

Incorrect web address – penultimate sentence from bottom of page 262 in
“Warning” box.

Correction

Site now redirects, direct URL is:
http://webarchive.nationalarchives.gov.uk/20140402142426/http://www.oft.gov.uk/news-and-updates/press/2014/05-14

Page

301

Error

The case statement is missing a trailing semicolon “:”

Correction

Replace the following line
“case BattleState.Intro”
With the following
“case BattleState.Intro:”

Page

370

Error

The type string is written as String, this causes an error when trying to compile with a missing using statement

Correction

Replace the following line in the MyEditorWindow class
“String windowName = “My Editor Window”;”
With the following
“string windowName = “My Editor Window”;”