# Versioning scheme

<figure><img src="https://3428853154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvxVSjyzvP6F7c9h_Hu%2Fuploads%2F8IifQ2KxgZin0ppZf4ws%2Fimage.png?alt=media&#x26;token=102f9dd7-bf3b-4990-972a-c3cb04acb3c8" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="158"></th><th></th></tr></thead><tbody><tr><td>Type</td><td>Description</td></tr><tr><td>Patch</td><td><p>It consists of fixes of all kind (bugs, comments, typos, descriptions, etc.). </p><p>This update is <strong>always recommended.</strong></p><p></p><p>Risk: <strong>Zero</strong> <span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></p></td></tr><tr><td>Minor</td><td><p>It consists of new features and improvements. Unfortunately, such changes could introduce API incompatibilities, and because of that, it is always recommended to follow the corresponding upgrade guide.</p><p></p><p>Risk: <strong>Low to medium</strong> <span data-gb-custom-inline data-tag="emoji" data-code="26a0">⚠️</span> </p></td></tr><tr><td><p></p><p>Major</p></td><td><p>A re-design of the asset. Compatibility will be compromised for sure.</p><p>Important: A major release will be introduced as a new (asset store) package. This means the new release doesn't replace the old one.</p><p></p><p>Risk: <strong>Maximum</strong> <span data-gb-custom-inline data-tag="emoji" data-code="2622">☢️</span></p></td></tr></tbody></table>

## How to update

Even though Unity is smart enough to replace all modified files, the recommended way to update the asset is by **deleting the&#x20;*****Character Controller Pro*****&#x20;folder** and then import the new version.

{% hint style="info" %}
It is always recommended to update to a newer version of the package whenever possible, unless the **risk** of doing so is high enough for your particular project.
{% endhint %}

{% hint style="warning" %}
The demo content included with the package does not follow any versioning scheme.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://lightbug14.gitbook.io/ccp/package/versioning.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.