User Defined Package Export

Without this feature, exported projects reference only the default set of Unity core modules. Whenever a user adds references to packages that their game used, the new packages will conflict with assemblies and scripts within the exported project. Deleting the conflicting exported files will break any asset references to those files.

There are third-party tools available to help fix broken script references, but they mostly rely on guessing the scripts from the MonoBehaviour fields. In addition, they do nothing to fix broken references for other asset types. That is the purpose of this feature: export asset and package references, so that the user doesn't have to fix broken references later.

Unfortunately, it is not feasible to datamine all possible packages, not even restricted to the official offerings from Unity. As such, users are responsible for mining the packages specific to their game. However, there are some resources to help them do the required datamining. https://github.com/AssetRipper/MarrowMiningDemo

This experimental feature can be enabled by going to the Configuration Files page, which can be accessed with "View/Configuration Files" in the file menu. To enable the feature, the user must upload package data json files appropriate for their game. Example json files are available in the Marrow Mining Demo I linked above.