Symptoms
- When I export a package using Assets -> Export package, it exports everything.
Cause
When exporting packages that include scripts, it includes all scripts that are in the project. This happens because there is no way to track dependencies between scripts. If you include dependencies and one of the dependencies is a script, then you need all scripts.
Resolution
You can use the function AssetDatabase.ExportPackage and multiple ExportPackageOptions. Please be aware that this workaround could cause some errors with missing scripts. Assets -> Export package is the suggested and secure option.
More Information
Comments
4 comments
This has been broken for almost four years now, so might I suggest something, that might sound a bit RADICAL to the Unity Team: Put down you coffee for five minutes, and FIX this issue. Yes, I know it sounds shocking, actually FIXING an issue, but, isn't that what you are paid for???
Dude you gotta chill and just do this http://unity3d.expert/tek-stuf-review-acer-takeapart-teardown-moto-motog-resolution-mouse-movement/export-package-only-include-dependent-files-unity/
Carl's suggestion works, but it really is silly. If the Project window can tell the difference, why can't the exporter?
Fast fix:
Assets/Select Dependencies
Assets/Export Package
Uncheck "include dependencies"
voila. Unity devs please fix this.
Please sign in to leave a comment.