Book Image

Unity 5.x Game Development Blueprints

By : John P. Doran
Book Image

Unity 5.x Game Development Blueprints

By: John P. Doran

Overview of this book

<p>This book will help you to create exciting and interactive games from scratch with the Unity game development platform. We will build 7-8 action-packed games of different difficulty levels, and we’ll show you how to leverage the intuitive workflow tools and state of the art Unity rendering engine to build and deploy mobile desktop as well as console games.</p> <p>Through this book, you’ll develop a complete skillset with the Unity toolset. Using the powerful C# language, we’ll create game-specific characters and game environments. Each project will focus on key Unity features as well as game strategy development. This book is the ideal guide to help your transition from an application developer to a full-fledged Unity game developer</p>
Table of Contents (19 chapters)
Unity 5.x Game Development Blueprints
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
Index

Adding a simple animated character


Now that we have our background in the world, let's add in our player sprite:

  1. From the Art Assets folder included in the example code for the chapter, bring the three sprites for the plane into the Project tab's Assets/Sprites folder.

  2. Then, from the Assets folder, create a new folder named Animations.

  3. From there, select all three images (hold Ctrl and then select each of them) and then drag and drop them into the Scene tab to bring them into the level. You'll see a new window pop up that says Create New Animation. From there, browse to the Animations folder we just created and then open it. Afterwards, change the File name: property to PlaneFlying and then press Save. This will create an animation and controller that will automatically play it. We will talk about animations in more detail in the next chapter, but currently, this will always just play an animation using these three frames over and over again unless we stop it via code.

  4. The plane looks a bit...