Thank you for purchasing Unity in Action. Please post any errors, other than those listed below, in the book's Author Online Forum. We'll compile a comprehensive list and publish it here for everyone's convenience. Thank you!

Last updated August 18, 2017

• Page 31, in listing 2.1:

  For those unfamiliar with C#, the 'f' after the number may be confusing. The text afterward should have this added explanation:
  
  First there's the variable for speed added toward the top of the class definition (the 'f' after the number tells the computer to treat this as a 'float' value; otherwise C# treats decimal numbers as a 'double').

• Page 34, end of section 2.4 intro:

  A sentence explains:
  
  Use the Axes menu to switch between code branches while working through the code.
  
  That wording is unclear about what to do; this wording explains better:
  
  Use the Axes drop-down menu in the Inspector to switch the direction of rotation.

• Pages 35 and 40:

  A sentence on page 35 explains:
  
  If you play the script now, the view will spin around just like before (only a lot faster, because the Y rotation is 9 instead of 3).
  
  That explanation doesn’t mention the Axes menu; this wording explains better:
  
  Set the Axes menu of the MouseLook component to horizontal rotation and play the script; the view will spin as before.
  
  Similarly, on page 40 change:
  
  When you run the new script, to:
  
  When you set the Axes menu and run the new code,…

• Pages 115 and 116, Listing 5.13:

  The wrong mouse event method was used in the code. In Listing 5.13 change OnMouseOver() to OnMouseEnter() to correct the code. Then the two mentions of MouseOver in the text should be changed to MouseEnter.

• Page 150:

  The third paragraph says Quaternion.LookDirection() but should say Quaternion.LookRotation().

• Page 184, in Listing 8.15:

  The code says Managers.Inventory.AddItem(name) but should say Managers.Inventory.AddItem(itemName)

• Pages 190, in Listing 8.21:

  The random character ‘B’ is a typo, so delete that.

• Page 198:

  Clarify the instruction
  
  ...but select Shader instead
  
  by changing it to
  
  ...but select a standard Shader instead

• Page 204, in Listing 9.5:

  The error check says
  
  if (www.error != null) {
  
  But that no longer works right; change it to:
  
  if (!string.IsNullOrEmpty(www.error)) {

• Page 235, explanation of Listing 10.5:

  The description says:
  
  ...choose OnSoundVolume() under Dynamic Float.
  
  That's the wrong function name; it should be:
  
  ...choose OnSoundValue() under Dynamic Float.

• Page 252, Listing 11.6:

  Change the 20.0f to 25.0f, and change the 1.5f to 1.75f

• Page 260, in Listing 11.14:

  While this code is correct in Unity 5.0, a change in Unity 5.1 breaks this code. Look for the two lines:
  
  trigger.delegates.Clear();
trigger.delegates.Add(entry);
  
  Those lines are correct for Unity 5.0, but Unity 5.1 will throw errors. The lines should be changed to:
  
  trigger.triggers.Clear();
trigger.triggers.Add(entry);

• Page 272, near the bottom:

  The beginning of the paragraph says:
  
  Finally, add buttons to use functions...
  
  For more clarity, add to that description:
  
  Finally, in Level1 add buttons to use functions...

• Page 274, in the TIP:

  Towards the end of the paragraph it says:
  
  ...don't touch the Scene folder...
  
  That folder name is wrong (or rather, the name can vary) so that description should be changed to:
  
  ...don't touch the lighting folder...

• Page 279, addition to bottom:

  This page should explain how to quit the game, so at the bottom add:
  
  TIP Quit fullscreen games with Alt+f4 on Windows or Cmd+Q on Mac. Finished games should have a button that calls Application.Quit().

• Page 283, section 12.2.3:

  The methods described here are legacy; in some cases they still work, but in some cases they are no longer supported. The recommended approach now is to use a jslib; these changes are all explained here.