Installation

• Scoped registry (recommended). You add the Playtolia registry one time. The package then behaves like a built-in package. You can find it in the Package Manager and install it by name. The Package Manager also shows a one-click Update button for each new version.
• Git URL. You get a tagged version directly from the distribution repository. This method needs no registry, but you must change the tag manually for each update. The Package Manager shows no Update button.
• Tarball (.tgz). You download a self-contained archive one time. This method is good for machines without a network connection. It is also good when you want the exact bytes in your own storage.

​

Requirements

• Unity 6000.0 or later (developed and tested with 6000.0.32f1)
• iOS builds: Xcode and CocoaPods, with deployment target 13.0 or later
• Android builds: Android SDK, with min SDK 24 (Android 7.0)

​

Install with the Package Manager

• Scoped registry (recommended)
• Git URL
• Tarball (.tgz)

A scoped registry tells Unity where to find the Playtolia packages. You add the registry one time. You then get every future version and the Package Manager Update button.Add the registry from Project Settings (no file changes). Open Edit ▸ Project Settings ▸ Package Manager. Expand Scoped Registries. Then do these steps:

1. Click the + button to add a new registry.
2. Type these values in the fields:
   • Name: Playtolia
   • URL: https://dist.playtolia.com/unity-sdk
   • Scope(s): com.playtolia
3. Click Save.

Then install the package from Window ▸ Package Manager ▸ My Registries ▸ Playtolia ▸ Playtolia SDK ▸ Install. As an alternative, use + ▸ Add package by name… with com.playtolia.sdk.

Prefer to edit manifest.json directly?

Add the same registry and the package to Packages/manifest.json. If the scopedRegistries array is not there, create it:

{
  "scopedRegistries": [
    {
      "name": "Playtolia",
      "url": "https://dist.playtolia.com/unity-sdk",
      "scopes": ["com.playtolia"]
    }
  ],
  "dependencies": {
    "com.playtolia.sdk": "1.4.0"
  }
}

A registry dependency uses normal version numbers ("1.4.0"), but a Git URL does not. The Package Manager thus shows every available version. It also shows an Update button after a newer version becomes available. This is the easiest way to stay current. The latest version number is on the Releases page.

1. In the Package Manager, click + ▸ Add package from git URL…
2. Paste the repository URL with the version tag that you want. Then click Add:

https://github.com/Playtolia/unity-sdk.git#vX.Y.Z

Replace vX.Y.Z with the version that you want. The latest tag is on the Releases page, for example #v1.4.0. Unity clones that tag and adds it to your project.

Use a fixed tag. Git URLs do not support version ranges. The C# code of the package matches one specific iOS framework version and one Android (Maven) version. A fixed #vX.Y.Z keeps all three in agreement and makes the builds reproducible. Without the fragment, Unity resolves main at the moment you add the URL, and then locks that commit in Packages/packages-lock.json. That commit does not update automatically, and a tag is clearer and safer.

You can also add the same line to Packages/manifest.json directly:

{
  "dependencies": {
    "com.playtolia.sdk": "https://github.com/Playtolia/unity-sdk.git#vX.Y.Z"
  }
}

An install from a Git URL needs a Git client on your machine. The client must be on your PATH before you run Unity. The Unity Install from a Git URL guide gives more details and troubleshooting steps.

1. Download playtolia-sdk-X.Y.Z.tgz from the Releases page.
2. In the Package Manager, click + ▸ Add package from tarball…
3. Select the downloaded .tgz file. Then click Open.

Unity copies the archive into your project and resolves it in place. The tarball is self-contained and already includes the iOS core.framework. After the download, the tarball works without network access.

CAUTION: Do not move or delete the .tgz file. Unity refers to the tarball by its file path, not by its contents. A move or a deletion makes the package fail to resolve at the next import. Keep the .tgz file in a stable location in your project or next to it. Many teams commit the file to a Packages/ subfolder. The Unity Install from a local tarball guide gives more information.

​

Native dependencies

• Android. The External Dependency Manager for Unity (EDM4U) resolves the dependencies from Maven Central. The package ships an Editor/SharedAndroidDependencies.xml file that points to the matching com.playtolia.sdk:core-android version. EDM4U downloads that version at build time. EDM4U is a transitive requirement. If your project does not have EDM4U, install com.google.external-dependency-manager with Playtolia.
• iOS. The core.framework binary ships inside the package. The included build post-processor embeds the framework into your Xcode project automatically.

​

Test the install

​

Updating

• Scoped registry (the easiest method). The Package Manager shows a version list and a one-click Update button for each new version. You change no files manually.

• Git URL. Change the tag in Packages/manifest.json, for example #v1.4.0 to #v1.5.0. The URL changes, and Unity resolves the package again at the next window focus. Unity also updates the lock file. As an alternative, run + ▸ Add package from git URL… again with the new tag. You do not edit the lock file manually. A manual edit is necessary only when you track a moving branch and not a tag.
• Tarball. Download the newer .tgz file. Delete the existing package from the Package Manager. Then add the new archive.

​

Next step