There is no need to rush; take as long as you need to finish this book. There are many topics in this book that can have a number of variations, so use the examples I have prepared and take your time to test them in your own way too.

This book is meant to be read twice; once for the 2D Game Kit, and a second time for the 3D Game Kit. The reader is not supposed to read both sections at the same time.

This is meant to be the basis for your game, so once each chapter is finished, you need to keep on working before starting the next one. If you read the book as fast as you can, you will definitely miss very important things.

Readers need to have a basic knowledge of interfaces and understand the virtual space and its rules. They also need to learn the behaviors and roles that each component must have in order to make a video game.

Readers should be willing to learn about video game development and create a video game without the need to learn any programming language.

We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: http://www.packtpub.com/sites/default/files/downloads/9781789538335_ColorImages.pdf.

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "We can use Game Kit's RocksPainter or Vegetation painter, which are placed in the Hierarchy."

Bold: Indicates a new term, an important word, or words that you see on screen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "In this case, we have to click on the Learn tab at the top left."