清单文件(用于描述构建中使用的所有资源包)的路径(可选)。
When you call BuildPipeline.BuildAssetBundles to create your AssetBundles, it also creates a manifest file describing the bundles produced. You can assign the path to this manifest file to assetBundleManifestPath
to ensure that a player build does not strip any types used in the asset bundles from the build.
BuildPipeline.BuildAssetBundles creates the manifest file in your AssetBundle output path, with a filename matching the parent directory name and ".manifest" as its extension. You can specify the path to the manifest using an absolute path or a path relative to the project directory.
You do not need to set this property when you generate asset bundles using the Scriptable Build Pipeline package.
See Also: BuildPipeline.BuildAssetBundles, AssetBundleManifest.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.