2. Debugging | Mastering Unity Scripting

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Mastering Unity Scripting

By : Alan Thorn

4.5 (14)

Mastering Unity Scripting

4.5 (14)

By: Alan Thorn

Overview of this book

Mastering Unity Scripting is an advanced book intended for students, educators, and professionals familiar with the Unity basics as well as the basics of scripting. Whether you've been using Unity for a short time or are an experienced user, this book has something important and valuable to offer to help you improve your game development workflow.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Unity C# Refresher

1. Unity C# Refresher

Why C#?

Creating script files

Instantiating scripts

Variables

Conditional statements

Arrays

Loops

Functions

Events

Classes and object-oriented programming

Classes and inheritance

Classes and polymorphism

C# properties

Commenting

Variable visibility

The ? operator

SendMessage and BroadcastMessage

Summary

2. Debugging

2. Debugging

Compilation errors and the console

Debugging with Debug.Log – custom messages

Overriding the ToString method

Visual debugging

Error logging

Editor debugging

Using the profiler

Debugging with MonoDevelop – getting started

Debugging with MonoDevelop – the Watch window

Debugging with MonoDevelop – continue and stepping

Debugging with MonoDevelop – call stack

Debugging with MonoDevelop – the Immediate window

Debugging with MonoDevelop – conditional breakpoints

Debugging with MonoDevelop – tracepoints

Summary

3. Singletons, Statics, GameObjects, and the World

3. Singletons, Statics, GameObjects, and the World

The GameObject

Component interactions

GameObjects and the world

The world, time, and updates

Immortal objects

Understanding singleton objects and statics

Summary

4. Event-driven Programming

4. Event-driven Programming

Events

Event management

Code folding in MonoDevelop with #region and #endregion

Summary

5. Cameras, Rendering, and Scenes

5. Cameras, Rendering, and Scenes

Camera gizmos

Being seen

Orthographic cameras

Camera rendering and postprocessing

Camera shake

Cameras and animation

Cameras and curves

Summary

6. Working with Mono

6. Working with Mono

Lists and collections

IEnumerable and IEnumerator

Strings and regular expressions

Infinite arguments

Language Integrated Query

Linq and regular expressions

Working with Text Data Assets

Text Assets – loading from the local files

Summary

7. Artificial Intelligence

7. Artificial Intelligence

Artificial Intelligence in games

Starting the project

Baking a navigation mesh

Starting an NPC agent

Finite State Machines in Mecanim

Finite State Machines in C# – getting started

Creating the Idle state

Creating the Patrol state

Creating the Chase state

Creating the Attack state

Creating the Seek-Health (or flee) state

Summary

8. Customizing the Unity Editor

8. Customizing the Unity Editor

Batch renaming

C# attributes and reflection

Color blending

Property exposing

Localization

Summary

9. Working with Textures, Models, and 2D

9. Working with Textures, Models, and 2D

Skybox

Procedural meshes

Animating UVs – scrolling textures

Texture painting

Summary

10. Source Control and Other Tips

10. Source Control and Other Tips

Git – source control

Resources folder and external files

AssetBundles and external files

Persistent data and saved games

Summary

Index

Index

Customer Reviews

4.5 (14)

5 star

57.1%

4 star

35.7%

3 star

7.1%

2 star

0%

1 star

0%

Debugging with MonoDevelop – getting started

Earlier, we encountered the Debug.Log method of debugging to print helper messages to the console at critical moments in the code to help us see how the program executes. This method, while functional, however, suffers some significant drawbacks. First off, when writing larger programs with many Debug.Log statements it's easy to effectively "spam" the console with excessive messages. This makes it difficult to differentiate between the ones you need and the ones you don't. Second, it's generally a bad practice to change your code by inserting the Debug.Log statements simply to monitor program flow and find errors. Ideally, we should be able to debug without changing our code. Therefore, we have compelling reasons to find alternative ways to debug. MonoDevelop can help us here. Specifically, in the latest releases of Unity, MonoDevelop can natively attach itself to a running Unity process. In doing this, we get access to a range of common debugging...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Mastering Unity Scripting

Search

Your notes and bookmarks