# Introduction The Unity asset ecosystem is vast — but most tools are designed as standalone solutions. They are excellent at what they do, yet completely unaware of the workflows surrounding them. The **Integration Series** changes that. It is a family of Unity packages that **connects third‑party assets to each other** — without requiring you to write glue code, manage version conflicts, or understand the internals of either asset. You install an integration, enable it in the inspector, and the assets start cooperating. {% hint style="info" %} Each *Integration Series* package is a self‑contained bridge between two or more assets. Install only what you need — there are no mandatory dependencies beyond the assets being integrated. {% endhint %} *** ## Business Value ### You gain features without writing code Enabling an integration immediately unlocks behavior that would otherwise require deep knowledge of both assets' APIs, event systems, and update loops. That expertise is already baked in. ### Your project stays maintainable Every integration hides asset‑specific implementation details behind a stable, version‑agnostic interface. When an asset publisher releases a new major version, only the relevant adapter needs updating — your scenes, your code, and all other integrations remain untouched. ### You are protected against breaking changes The *Integration Series* architecture is built around the assumption that third‑party APIs will change. Version‑aware adapters compile conditionally based on what is actually installed in your project. Unsupported or missing versions fail gracefully and are reported clearly in the inspector — nothing silently breaks. ### It scales with your project Start with a single integration between two assets. As your project grows, add more integrations independently. Each one follows the same architecture and the same inspector workflow, so onboarding new team members or extending the setup requires no additional learning curve. *** ## What Is in This Documentation {% content-ref url="../core-features/setup" %} [setup](https://qhun-gaming.gitbook.io/integration-series/core-features/setup) {% endcontent-ref %} How to add the *Integration Series* component to your scene and activate integrations — including the one‑click automatic setup. {% content-ref url="../core-features/orchestrator-component" %} [orchestrator-component](https://qhun-gaming.gitbook.io/integration-series/core-features/orchestrator-component) {% endcontent-ref %} A walkthrough of the main inspector UI: enabling integrations, managing adapters, configuring settings, and understanding the version‑agnostic loading system. {% content-ref url="../core-features/compiler-define-symbols" %} [compiler-define-symbols](https://qhun-gaming.gitbook.io/integration-series/core-features/compiler-define-symbols) {% endcontent-ref %} A reference of the compiler symbols available for debugging and developer tooling. {% content-ref url="../architecture/overview" %} [overview](https://qhun-gaming.gitbook.io/integration-series/architecture/overview) {% endcontent-ref %} The high‑level four‑layer architecture — Core, Asset Integration Layers, Cross Integration Layer, and Ecosystem Layer — and the reasoning behind the hexagonal design. {% content-ref url="../architecture/adapter" %} [adapter](https://qhun-gaming.gitbook.io/integration-series/architecture/adapter) {% endcontent-ref %} How an adapter wraps a single third‑party asset behind a version‑agnostic interface, and what it looks like to implement one. {% content-ref url="../architecture/integration" %} [integration](https://qhun-gaming.gitbook.io/integration-series/architecture/integration) {% endcontent-ref %} How a cross‑integration connects two adapters, declares its dependencies, and handles the enable/disable lifecycle. {% content-ref url="../the-vision/vision-of-integration-series" %} [vision-of-integration-series](https://qhun-gaming.gitbook.io/integration-series/the-vision/vision-of-integration-series) {% endcontent-ref %} The philosophy behind the project and the long‑term goals that guide its development. {% content-ref url="../the-vision/compatibility-and-unity-version-support" %} [compatibility-and-unity-version-support](https://qhun-gaming.gitbook.io/integration-series/the-vision/compatibility-and-unity-version-support) {% endcontent-ref %} How Unity version support is determined, what full LTS support means in practice, and how breaking upstream changes are handled. {% content-ref url="../the-vision/update-and-upgrade-policy" %} [update-and-upgrade-policy](https://qhun-gaming.gitbook.io/integration-series/the-vision/update-and-upgrade-policy) {% endcontent-ref %} What is delivered free of charge, and under what conditions a larger expansion may be released as a separate upgrade. *** ## Links * Homepage: * Discord: * Publisher Profile: