Installation
Prerequisites
- Unity 6000.0 LTS or newer
- Build target set to iOS or Android — the SDK does not support Standalone, WebGL, or other platforms
- Registry token from your Tactile integration contact (for package access)
- PlayOps dashboard access to your project
1. Configure registry authentication
The PlayOps SDK and its dependencies are hosted on a private package registry. You need to configure authentication on your machine before Unity can download them.
-
Locate your Unity configuration file:
~/.upmconfig.toml%USERPROFILE%\.upmconfig.toml -
Open (or create) the
.upmconfig.tomlfile and add the following:[npmAuth."https://npm.pkg.github.com/@tactilegames"]token = "YOUR_TOKEN_HERE" -
Replace
YOUR_TOKEN_HEREwith the registry token provided by Tactile.
2. Add the scoped registry
Open Packages/manifest.json in your Unity project and add the Tactile Games scoped registry:
{ "scopedRegistries": [ { "name": "Tactile Games", "url": "https://npm.pkg.github.com/@tactilegames", "scopes": [ "com.tactilegames" ] } ], "dependencies": { ... }}This tells Unity to resolve any package starting with com.tactilegames from the Tactile registry. All other packages continue to resolve from Unity’s default registry.
3. Install the SDK
Add the SDK to your dependencies in Packages/manifest.json:
{ "dependencies": { "com.tactilegames.playops-sdk": "1.9.0" }}The latest SDK version is 1.9.0 — see the Releases — Changelog for the full history.
Unity will automatically resolve all transitive dependencies — no need to list them individually.
Alternatively, install via the Unity Editor:
- Open Window > Package Manager.
- Click the + button and choose Add package by name.
- Enter
com.tactilegames.playops-sdkand version1.9.0. - Click Add.
4. Commit BillingMode.json (Android)
The SDK sells in-app purchases through Unity IAP. On Android, Unity IAP reads Assets/Resources/BillingMode.json at runtime to pick the store. Unity IAP creates the file the first time the project opens in the Editor:
{"androidStore":"GooglePlay"}Commit this file to version control.
5. Verify the installation
After Unity finishes importing:
- Open Window > Package Manager.
- Switch the filter to In Project.
- You should see PlayOps SDK and its dependencies listed.
If you see authentication errors, double-check that:
.upmconfig.tomlexists in your home directory (not your project)- The token is correct and has not expired
- The
scopedRegistriesentry is present inmanifest.json
Next steps
Continue to the Quick Start to connect your project to the PlayOps dashboard and initialize the SDK.