Create UGS Asset Store packages
This guide explains how to create assets and packages using Asset Store Tools and publish them to the Asset Store. Other users can then download the asset and deploy it to their own project using the Deployment package.
Create UGS assets
Create the UGS assets you wish to include in the Asset Store package. Refer to the corresponding documentation for the assets you can create. The following services are supported:
Install Asset Store Tools
Install Asset Store Tools to upload your package from the Unity Editor. Refer to Publishing to the Asset Store to learn more.
- Open the Unity Editor.
- In the Asset Store Publishing Tools page, select Open in Unity. This opens Asset Store Publishing tools in the Package Manager. To access this manually:
- In the Unity Editor, open Window > Package Manager.
- In the Package Manager, select My Assets to find Asset Store Publishing Tools.
- Select Download.
- Select Import. The Import Unity Package window opens.
- Select the assets you want to import and then select Import.
Upload package to the Asset Store
Refer to Creating a new package draft to learn how to upload packages to the Asset Store.
Set your dependencies
- Enable the
Include Package Manifest
toggle. A package UI opens. - Toggle the required service packages relevant to your package.
Choose your export type
You can upload your package directly from the assets folder, or from a pre-exported .unitypackage
file.
To upload from the Assets folder:
- Set
Upload type
toFrom Assets Folder
. - Select
Browse
on theFolder path
line. - Select the path from the popup (must be under the
/Assets
folder). - Select Export and Upload.
To upload from a .unitypackage
:
- Set
Upload type
toFrom Assets Folder
. - Select
Browse
on theFolder path
line. - Select the path from the popup (must be under the
/Assets
folder). - Select Export.
- Change
Upload type
toPre-exported .unitypackage
. - Select
Browse
on thePackage path
line. - Select the path of your recently exported
.unitypackage
. - Select Upload.
Service-specific intructions
Cloud Code modules
The recommended best practice is for Cloud Code modules to live outside the Assets
folder, or in a hidden folder (a folder name ending with ~
, such as Module~
). To successfully export to the Asset Store, you must choose a hidden path within the Assets folder. By default, hidden paths are not included in because .meta
files are not generated for the files inside a hidden path.
To generate the .meta
files and include the contents of the hidden folder to your Asset Store package:
- Open the module location in your file browser.
- Remove
~
from the folder name. - Select your Unity Editor window and allow the asset processor to finish.
- Go back to your file browser and add
~
back to your folder name. - Delete the
.meta
file for your folder. Otherwise, an empty, non-hidden folder is created.
Now your package is ready to be exported with an included Cloud Code module.
Deployment window
The Deployment window is part of the Deployment package and it offers a uniform interface to deploy assets for UGS. Refer to Deployment package to learn how to use it.
The UGS use cases samples project contains UGS assets that you can deploy using the Deployment window. For an example, see A/B Testing.