Versions and updates

You should always update to a newer version of the package, unless the risk of doing so is high enough for your particular project (in some cases it is best to keep using an old version).

Versioning scheme

The version number indicates the risk involved when updating the asset. By "risk" i mean things that can cause issues all of kind, such as console errors, API incompatibilities, new features replacing older ones, deprecation of some specific functionalities, an overall design change, etc.

This is the versioning scheme used:

Major.Feature.Minor

Update	Description
Minor	Basically bug fixes, code improvements, etc. Sometimes, new minor features will be introduced, as long as they don't interfiere with the rest of the package. This update is always recommended, it should not give you any issues. That being said, it is also recommended to check the release notes before attempting to update the package. Risk: Zero ✅
Feature	This update usually involves one or more new relevant features, thus the name. Sometimes improving an existing feature may require an overall re-design of the code, such changes could end up causing API incompatibilities. If that's the case, the update will be labeled as a "feature" update, even though there will be no new features available. Risk: Low to medium ⚠️
Major	A major update is used as an opportunity to re-design the core of the asset. By doing so it's expected to create some sorts of components and API incompatibilities. This type of update could involve a new upgrade (a.k.a new asset package). By doing so, you will have access to the old package every time you want. Risk: Maximum ☢️

The demo content is not represented by the scheme presented above. This basically means this content might change a lot from version to version, or not.

Support

Let me make this clear: I will always put all my effort in the latest version of the package. In my own eyes, that's the best this package can get, and i will always recommend you to get that version. This obviously doesn't mean you won't receive support if you are using an older version.

How to update

To update the package (regardless of the version) is recommended to delete the Character Controller Pro folder and then import the new version.

Remember always to put your own work outside this folder.