Book Image

Extending Unity with Editor Scripting

Book Image

Extending Unity with Editor Scripting

Overview of this book

Table of Contents (18 chapters)
Extending Unity with Editor Scripting
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Preparing the environment


In a normal development situation, if the custom tools that we will create are meant to be something reusable, the best decision is to deal with them as independent projects. Let's do this with the AppBuilder tool.

First, create a new Unity project with the name AppBuilder and then move the files related to this tool from the Run & Jump project here.

Your project must look like this:

We used this folder structure here just to match it to the structure we have in Run & Jump. However, as a good practice, always use a root folder with the name of the tool you want to share, if possible.

Note

Here, we are assuming that you have the Run & Jump project integrated with Git. It is necessary that you go through the Sharing code using Git submodules section. After reallocating the AppBuilder files from the Run & Jump project, commit the change in Run & Jump.