Publish an Asset Store item (Coming Soon)

An Asset Store item is a catalog card backed by a published package. The package delivers templates, scripts, Views, documents, and other shared content; the item chooses which of those package entries become the user-facing asset. Publish and verify the package first, then publish the card.

For installation instructions, including a complete Fortune Wheel example, see Asset Store.

Prepare the source package

1. In the source project, finish the feature in a development branch. For an event with a View, verify the game-event document, its View reference, the View's scripts and media, localization, and the resources they reference.
2. Open Project Settings → Packages → Manage and create or edit a package. Add the templates, documents, Views, scripts, assets, localizations, and other content needed by the feature. Add package dependencies for content owned by another package rather than trying to republish that content as your own.
3. Save and Publish the package. Resolve any missing-reference validation errors before proceeding. The error should identify the missing type and the referencing item; do not work around a missing dependency by publishing a broken card.

The Packages guide explains package versions and dependencies. In particular, package-owned content may have different update behavior from editable copies created from an asset. Review Static on Clone for templates and scripts before using it, because replacing managed content on an update can overwrite changes in a consuming project.

Create the catalog card

1. In the saved package's editor, find Assets in this package and click Create asset.
2. In Details, enter a clear title, a short description of what users receive, a category, tags, and the contexts where the asset works. Use the description to state any setup or testing requirements.
3. In Content, select the package entries that define the asset. For a Fortune Wheel-style event, select the event document and its View as Clone so each installation creates editable versions. Select content that should remain package-owned as Reuse. The list is limited to entries in the package; a missing item must first be added to and published with the package.
4. In Media & review, upload a thumbnail and real screenshots of the feature. Review the card and save it as a draft.
5. Click Publish on the saved card. A published card can be found in Asset Store by projects that are allowed to access its package.

Do not describe a card as a complete playable feature unless its package actually supplies the required event configuration, View, scripts, images, fonts, localization, and other dependencies. A preview image alone does not install those resources.

Verify as a customer would

Use a separate, preferably empty test project and a development branch. Open Discover → Asset Store, find the new card, inspect Contents and Dependencies, then use Add to this project and review the preparation plan. Confirm with Add selected content. Check that the editable items appear in the expected editor sections, deploy the branch, and run the feature in the Demo App. For an event, verify both its schedule and the View it opens. Record any unexpected replacement or missing reference before making the card public.

When releasing a new package version, repeat this verification in a project that already has the older version as well as a clean project. Existing editable copies do not automatically become identical to your new source document or View.