Chapter 1, Enter the Third Dimension: In this chapter, we will introduce you to the concepts of working in 3D and how game development works with Unity. Having covered how 3D development works, you will learn the core windows that make up the Unity Editor environment.

Chapter 2, Prototyping and Scripting Basics: In this chapter, we aim to get you started with a practical approach to learning Unity, by building a simple game mechanic prototype, and working with C# (pronounced C-Sharp) or Javascript scripting as you get to grips with your first Unity interaction.

Chapter 3, Creating the Environment: Now that you have a grasp on how to make use of Unity, and it's processes, in this chapter you will begin to design outdoor environments—using the Terrain toolset to create an island environment.

Chapter 4, Player Characters and Further Scripting: With our island environment completed, we will look at how Player Characters are constructed in Unity, looking at scripting for characters, and also learning further scripting concepts that will be essential as you continue to create further interactions in Unity.

Chapter 5, Interactions: This key chapter will teach you three of the most important processes in game design with Unity—interaction using Collisions, detection of objects using Ray casting, and collider intersect detection using Trigger areas.

Chapter 6, Collection, Inventory, and HUD: With a variety of interactions covered, we will put this knowledge into further practice as we learn how to make a simple inventory for the player, and an accompanying heads up display to record items collected.

Chapter 7, Instantiation and Rigidbodies: To put interaction into practice once more, we will make use of Unity's built-in physics engine, and learn how to combine this with animation to create a shooting mini-game.

Chapter 8, Particle Systems: Taking a break from scripting, we'll dive into some of Unity's visual effects to create a campfire using Particle systems-making systems for fire and smoke.

Chapter 9, Designing Menus: Every good game needs a user interface, and in this chapter we will take a look at two differing approaches to creating menus in Unity: with GUI Texture components and with the GUI scripting class.

Chapter 10, Animation Basics: To keep your Unity games looking dynamic, it's important to learn how to animate in Unity. In this chapter, we'll create a game ending sequence of titles and learn how to animate via scripting and also with Unity's Animation window.

Chapter 11, Performance Tweaks and Finishing Touches: Whilst it's important to get gameplay just right, it's also nice to make sure your game looks polished before it's ready to unleash on your audience. In this chapter, we'll look at further visual effects and optimization to make your game shine and perform well.

Chapter 12, Building and Sharing: In order to grow as a developer, it's really important to share your work with players, and get feedback. In this chapter, we'll learn how you can export your game as a standalone executable, and as a web player, so that you can do just that.

Chapter 13, Testing and Further Study: In this concluding chapter, we will look at ways of receiving feedback from your player, and give you some advice to stand you in good stead as you begin your career in development with Unity. This chapter also features some recommended further reading to cover as you progress from the confines of this book to becoming a fully-fledged game developer!

Glossary: The glossary contains descriptions of common terms that you might encounter and also serves as a handy reference

For this book you will be required to download the free version of Unity, available at:

http://www.unity3d.com/unity/download

Your computer should also meet the following specifications, as stated on the Unity website:

For the latest requirements, see the Unity website:

http://unity3d.com/unity/system-requirements.html

If you're a designer or animator who wishes to take their first steps into game development or prototyping, or if you've simply spent many hours sitting in front of video games with ideas bubbling away in the back of your mind, Unity and this book should be your starting point. No prior knowledge of game production is required, inviting you to simply bring with you a passion for making great games.

This book is written with Unity version 3.4.2 in mind, and is tested for that version. However, in some rare cases, despite stringent checks of the text, book releases may feature errors that cause confusion to readers. Also, as Unity evolves and new versions of the software are released, parts of this book may need updating.

To keep you totally up to date, we're providing you with the following website in order to give you up to date changes to what is written in the book, and also any changes that are made to Unity itself - making sure that this book is always up to date with Unity's latest practices. So if you stumble upon a problem you think may have changed, or simply need help understanding the book, visit the following URL:http://www.unitybook.net

In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text are shown as follows: "Set the fps variable to the Rounded value of frames."

A block of code is set as follows:

// Matches
private var haveMatches : boolean = false;
var matchGUIprefab : GUITexture;

Some code lines are long, and end up running onto new linesmake sure that you do not do this in your code. Remember that code lines are terminated by a semi-colon ; so wherever possible, keep code on a single line. In the example below, space restraints forces this to be displayed on two lines but in your script editor, you should not place a new line to achieve this:

new Vector3(Mathf.Lerp(xStartPosition, xEndPosition, (Time.time-startTime)*speed), transform.position.y,transform.position.z);

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Go to File | Save in the script editor, and switch back to Unity."

Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.

To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.

If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or e-mail <[email protected]>.

If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.