|How do you use documentation throughout your workflow? Share your experience with us by taking this survey.|
You can disable a Built-in packageBuilt-in packages allow users to toggle Unity features on or off through the Package Manager. Enabling or disabling a package reduces the run-time build size. For example, most projects don’t use the legacy Particle System. By removing the abstracted package of this feature, the related code and resources are not part of the final built product. Typically, these packages contain only the package manifest and are bundled with Unity (rather than available on the package registry).
See in Glossary if you don’t need some modules and you want to save resources. However, when you disable a built-in package, the corresponding Unity functionality is no longer available. This results in the following:
To disable a built-in package:
Open the Package Manager window and select Built-in packages from the PackagesPackages are collections of assets to be shared and re-used in Unity. The Unity Package Manager (UPM) can display, add, and remove packages from your project. These packages are native to the Unity Package Manager and provide a fundamental method of delivering Unity functionality. However, the Unity Package Manager can also display Asset Store packages that you downloaded from the Asset Store. More info
See in Glossary drop-down menu.
Select the built-in package you want to disable. Its information appears in the details view.
Click the Disable button.
When the progress bar finishes, the check mark no longer appears next to the built-in package and the Disable button becomes an Enable button.
If you want to re-enable a disabled built-in package, click the Enable button.