Book Image

Mastering Unity 2017 Game Development with C# - Second Edition

Book Image

Mastering Unity 2017 Game Development with C# - Second Edition

Overview of this book

Do you want to make the leap from being an everyday Unity developer to being a pro game developer? Then look no further! This book is your one-stop solution to creating mesmerizing games with lifelike features and amazing gameplay. This book focuses in some detail on a practical project with Unity, building a first-person game with many features. You'll delve into the architecture of a Unity game, creating expansive worlds, interesting render effects, and other features to make your games special. You will create individual game components, use efficient animation techniques, and implement collision and physics effectively. Specifically, we'll explore optimal techniques for importing game assets, such as meshes and textures; tips and tricks for effective level design; how to animate and script NPCs; how to configure and deploy to mobile devices; how to prepare for VR development; how to work with version control; and more. By the end of this book, you'll have developed sufficient competency in Unity development to produce fun games with confidence.
Table of Contents (9 chapters)

Creating player waypoints

The remainder of this chapter focuses on creating the first input type, namely, player movement. The second type is explored in the next chapter. In building movement functionality, we'll bring together many Unity features operating harmoniously, including animation, Mecanim, scripting, and others. We'll start by creating empty objects (empties) in the scene, representing important locations for the camera to stop on its journey from the beginning of the level to the end. These are locations of attack and ambush; where zombies approach for combat. When a combat sequence is completed (by killing all zombies), the camera is free to move forward at the player's prompting. To create waypoints, create an empty object for each stopping point, and then parent all of those to a single object for organization. I have created five stopping points...