Install via UPM

Add to Unity Package Manager using this URL

https://www.pkglnk.dev/test-package.git
Test Package

README Markdown

Copy this to your project's README.md

Style
Preview
pkglnk installs badge
## Installation

Add **Test Package** to your Unity project via Package Manager:

1. Open **Window > Package Manager**
2. Click **+** > **Add package from git URL**
3. Enter:
```
https://www.pkglnk.dev/test-package.git
```

[![pkglnk](https://www.pkglnk.dev/badge/test-package.svg?style=pkglnk)](https://www.pkglnk.dev/pkg/test-package)

Dependencies (1)

README

#Custom Unity Package

UPM Unity Package Manager is Unitys equivalent of NPM. This is the process required to create custom Unity packages distributed via UMP. UPM packages must adhere to UPM standards and convensions for them to function properly.

see Unitys docs

###Creating a new embedded package Follow these instructions if you want to create a custom package inside your project folder.

  1. Open the Unity Hub, and create an empty project on your computer. You can also use an existing project on your computer, and embed the package under your project or install the package from a local folder. However, starting with a new project makes the package contents less prone to errors.
  2. Using your computer’s file manager (for example the Windows File Explorer or the macOS Finder), navigate to your project folder and locate the Packages subfolder.
  3. Create a new subfolder for your package inside the Packages folder using a name that matches the package name. For example, if your package is called com.example.mypackage, the subfolder should also be called com.example.mypackage. Note: This is particularly important if your package contains assets, because the AssetDatabase looks for an asset path that matches Packages//Assets, regardless of what the actual folder is called.
  4. Open your preferred text editor and create a JSON file called package.json.
  5. Save it under the new package root folder you created.
  6. Fill out all required and mandatory fields in the package manifest (package.json) file.
  7. Layout your package structure to adhere to the package layout convension

###Package Manifest Example

{
  "name": "com.unity.example",
  "version": "1.2.3",
  "displayName": "Package Example",
  "description": "This is an example package",
  "unity": "2019.1",
  "unityRelease": "0b5",
  "dependencies": {
    "com.unity.some-package": "1.0.0",
    "com.unity.other-package": "2.0.0"
 },
 "keywords": [
    "keyword1",
    "keyword2",
    "keyword3"
  ],
  "author": {
    "name": "Unity",
    "email": "unity@example.com",
    "url": "https://www.unity3d.com"
  }
}

###Package Layout Example

<root>
  β”œβ”€β”€ package.json
  β”œβ”€β”€ README.md
  β”œβ”€β”€ CHANGELOG.md
  β”œβ”€β”€ LICENSE.md
  β”œβ”€β”€ Editor
  β”‚   β”œβ”€β”€ Unity.[YourPackageName].Editor.asmdef
  β”‚   └── EditorExample.cs
  β”œβ”€β”€ Runtime
  β”‚   β”œβ”€β”€ Unity.[YourPackageName].asmdef
  β”‚   └── RuntimeExample.cs
  β”œβ”€β”€ Tests
  β”‚   β”œβ”€β”€ Editor
  β”‚   β”‚   β”œβ”€β”€ Unity.[YourPackageName].Editor.Tests.asmdef
  β”‚   β”‚   └── EditorExampleTest.cs
  β”‚   └── Runtime
  β”‚        β”œβ”€β”€ Unity.[YourPackageName].Tests.asmdef
  β”‚        └── RuntimeExampleTest.cs
  └── Documentation~
       └── [YourPackageName].md
``

Comments

No comments yet. Be the first!