# Compatibility & Unity Version Support

### 🌐 General Compatibility

The compatibility of this integration depends primarily on the integrated third‑party assets it connects. Since both assets evolve independently, their supported Unity versions define the technical boundaries of what this integration can support.

My goal with the **Integration Series** is to maintain compatibility with every Unity version that **the integrated assets** support simultaneously. As long as the underlying assets function correctly in a given Unity release, the integration aims to function there as well.

***

### 🛠️ Unity Version Support

**✔️ Full LTS Support**

Long‑Term Support (LTS) versions of Unity are the primary target for stability and reliability. Full support for all relevant LTS releases is guaranteed.

**✔️ Non‑LTS Support Whenever Possible**

While not guaranteed, I actively work to maintain compatibility with non‑LTS Unity versions as long as both integrated assets support them. When both publishers keep their assets functional on a non‑LTS release, the integration will typically work there too.

***

### ⚠️ Dependency‑Driven Compatibility

Because this integration does not modify or replace any part of the integrated assets, compatibility may be affected if:

* a publisher removes or significantly changes a feature the integration relies on
* APIs are restructured, renamed, or deprecated
* Unity introduces breaking changes that affect either asset

In such cases, I will update the integration where feasible. However, long‑term compatibility ultimately depends on the underlying assets continuing to provide the required features.

***

### 🤝 Collaboration With Asset Publishers

To ensure the best possible experience, I stay in active communication with the publishers of both integrated assets. This ongoing exchange helps:

* maintain long‑term stability
* react quickly to breaking changes
* align the integration with evolving APIs and workflows
* identify opportunities for new or improved features

While compatibility is inherently tied to the underlying assets, I do my best to keep the integration stable, future‑proof, and aligned with the direction of both publishers.