For more information, refer to Versioning. This value must respect Semantic Versioning. The package version number ( ).įor example, “3.2.1” indicates that this is the 3rd major release, the 2nd minor release, and the first patch. Note: The name identifier is different than the user-friendly name that appears in the list view in the Package Manager window. For more information about the naming convention, refer to Naming your package. PropertyĪ unique identifier that conforms to the Unity Package Manager naming convention, which uses reverse domain name notation.

If these properties aren’t present, either the registry refuses the package when it’s published, or the Package Manager can’t fetch or load the package. The manifest stores this information in a series of required, recommended, and optional properties. The Package Manager reads this manifest to find out the package’s contents, how to unpack its contents, and what information to display the user in the Package Manager window. Refer to the example for a sample package manifest file. The file’s format is similar to npm’s package.json format, but uses different semantics for some of its properties. The package manifest uses the JSON (JavaScript Object Notation) syntax to describe what’s inside the package. The earliest version of the Unity Editor the package is compatible with.A user-friendly name that appears in the UI.The package manifest also defines useful information to communicate to the user, such as: The package manifest is always at the root of the package and has crucial information about the package, such as its registered name and version number. Unity uses a package manifest file ( package.json) to manage information about a specific version of a specific package.

Extract tmpro assets from unity