IN THIS ARTICLE
Open 3D Engine (O3DE) projects define and configure the set of code and assets that make up your game or other application. Gems that you enable for your project provide some code and assets. A project directory, sometimes referred to as the “project root”, contains your projects.
To create and manage projects, you can use either the GUI-based Project Manager tool or the O3DE command line interface (CLI). The topics in this section provide details on creating O3DE projects using either of these options.
|Understanding ||Get a detailed look at the fields in the project manifest, an important project configuration file.|
|Project Manager||Learn how to create and manage projects using a GUI-based tool.|
|Adding and Removing Gems||Learn how to add and remove Gems in your project.|
|Registering Gems||Learn how to register external Gems from sources outside of O3DE.|
|O3DE CLI Reference||Learn how to create and configure your O3DE environment and its objects, including engines, projects, and Gems, using the |
|Troubleshooting||Troubleshoot common issues that you might encounter during project configuration.|
To build projects, use either Project Manager or CMake. For more information, refer to any of the following resources:
- Introductory tutorials in the Get Started Guide.
- Project Manager and its Build command in the project drop-down menu.
- Configure and build topic in the Build section of this User Guide.
Each project’s root directory contains a project manifest file named
project.json. This file stores important project configuration properties. O3DE creates this file for you during project creation.
To change any of the properties in this file, you can either edit the file manually using a text editor, or edit individual properties using the
command. Additionally, you can edit the
display_name property in Project Manager.
The following table describes each of the properties in
project.json. The default value for many of the properties contains the project name given when you created the project. We indicate this project name as “<PROJECT_NAME>”.
|project_name||The name of the project. The ||“<PROJECT_NAME>”|
|origin||A URL for the project, such as the repository URL or project website. This field is intended for Project Manager to use.||“The primary repo for <PROJECT_NAME> goes here: i.e. http://www.mydomain.com”|
|license||The license that the project uses, and any copyright information that you want to include. Consider providing the URL for the license. This field is intended for Project Manager to use.||“What license <PROJECT_NAME> uses goes here: i.e. https://opensource.org/licenses/MIT"|
|display_name||The display name of the project in Project Manager.||“<PROJECT_NAME>”|
|summary||A short description of the project. This field is intended for Project Manager to use.||“A short description of <PROJECT_NAME>.”|
|canonical_tags||A standard field in O3DE manifests used to identify an O3DE object’s type. Examples: “Gem”, “Project”. Projects should use the “Project” tag.||[ “Project” ]|
|user_tags||Any keyword tags that you want to associate with the project. Examples: “Physics”, “Assets”, “AWS”. For examples of the standard set of tags that Gems use, refer to the Project Manager Gem Catalog. Project Manager uses these tags for documentation, search, and filtering.||[ “<PROJECT_NAME>” ]|
|icon_path||The path and filename of the project icon. Project Manager uses this icon. The file must be located in the project root directory, and the filename must be |
WARNING: Do not change the path or filename.
|engine||The name of the engine registered to the project. Register engines in your O3DE manifest, located at ||“o3de”|
|restricted_name||(Optional) The name of a restricted folder to associate with the project.||“projects”|
|external_subdirectories||(Optional) The path to one or more directories to include in the project build. You can use any directory with a |