FlowScope/Packages/com.flowscope.gamecore/Documentation~/installation.md

FlowScope Git Package Installation

Consumer Manifest

Add FlowScope, R3.Unity, and the NuGet R3 core dependency to the consuming project's Packages/manifest.json:

{
  "scopedRegistries": [
    {
      "name": "Unity NuGet",
      "url": "https://unitynuget-registry.openupm.com",
      "scopes": [
        "org.nuget"
      ]
    }
  ],
  "dependencies": {
    "com.cysharp.r3": "https://github.com/Cysharp/R3.git?path=src/R3.Unity/Assets/R3.Unity#1.3.0",
    "com.flowscope.gamecore": "ssh://git@git.zz.com:2222/Developer/FlowScope.git?path=/Packages/com.flowscope.gamecore#v0.2.0-preview.2",
    "org.nuget.r3": "1.3.0"
  }
}

Keep both R3 entries in the project manifest. Unity Package Manager can install a Git package from the project manifest, but Git dependencies declared inside another package's package.json are not resolved reliably. org.nuget.r3 supplies the core R3 and BCL DLLs required by R3.Unity.

Validation

After Unity resolves the package:

1. Confirm FlowScope.Runtime, FlowScope.Addressables, and FlowScope.Editor compile.
2. Open Tools/FlowScope/Diagnostics.
3. Confirm Addressables and UGUI dependencies are present.
4. Add a small probe script in the consuming project that references FlowScope.Container.Container and FlowScope.Flow.GameFlow.
5. Confirm the consuming project has zero compile errors and zero Console errors after package resolution.

Do not copy Assets/FlowScope into the consuming project when testing the Git package path. That would validate project-internal source import rather than package consumption.