To get the most out of this book
You will be developing a full project throughout the chapters of this book, and while you can just read the chapters, I highly recommend that you practice all the steps in this project as you advance through the book, to get the experience needed to properly learn the concepts we look at here. The chapters are designed so that you can customize the game according to your preferences, but do consider not deviating too much from the main idea.
The project files are split into folders per chapter and are designed in a cumulative way, each folder having just the new files introduced by the chapter or the ones that are different from previous chapters. This means, for example, that if one file doesn't change since Chapter 1, you won't find it in the folders for Chapter 2 onwards. You can open the scene file in each chapter folder to see how the game should look like at the end of that chapter. This allows you to see just what gets changed in each chapter and means that you can easily identify necessary changes. If, for some reason, you can't finish Chapter 3, for example, you can just pick things up again with Chapter 4 solved folder.
We advise you to type the code yourself or access the code via the GitHub repository (link available in the next section). Doing the latter will help you avoid any potential errors related to the copying and pasting of code.
Take into account that this book and its examples has been written using Unity 2020.1.0f1, the latest version available at the moment. This is the first Unity 2020 release, and while there might be newer versions, consider that if you use them, there might be slight differences in screenshots or steps depicted in the book, but nothing hard to sort out.