Assets, importing and deployment content
Section titled “Assets, importing and deployment content”An asset has a persistent identity, a canonical value and potentially loaded resources. Its source file, import metadata and generated artifact are related inputs and outputs, not interchangeable copies of the asset.
| Your task | Start here |
|---|---|
| Load an asset and retain it for an operation | Load and retain assets |
| Read generated bytes without exposing a cache path | Read artifact bytes |
| Change importer settings safely | Edit import settings |
| Copy an installed plugin sample into your project | Import a plugin sample |
| Open validated deployment content in a host | Read a content pack |
| Investigate Missing, failed imports or rejected exports | Diagnose asset problems |
Authoring and runtime
Section titled “Authoring and runtime”The authoring pipeline discovers sources, imports them and prepares content-addressed outputs. Runtime asset services read a validated deployment store and do not invoke source importers. Editor last-good content can remain useful after an import failure, but that failure cannot certify a new Player build.
For the underlying model, read asset publication and recovery. To add a format, read writing an importer. Exact host contracts live in the Assets, Assets Pipeline and Content references.