Support

Difficult to say, it primarily depends on changes made to Unity. If an asset completely falls over in a new version it may be supported up to that version. If this means a large revision is needed, a revised (paid) upgrade or successor is considered for further development and support.

• On the asset store, you should always go off what the description says it does, and supports what it says it supports on the day you purchase a license for it. Indefinite support is not realistic, paid upgrades for continued support are reasonable to expect. Updates and new features are complementary, this applies to any and all assets on the store.
• Historically, assets have had a development lifetime of 3-6 years. After which, their backlog is usually exhausted and they’ve reached complete maturity, or revenue is no longer sufficient to warrant further time investment.
• Assets that are no longer actively developed, yet work fine in new Unity versions, will continue to receive minor updates and fixes (usually to fix code warnings). If this is the case, this will be noted in an asset’s description.
• More often than not, many lessons will have been learned after a few years of development. A new asset, to succeed it, will become a pursuit to consider.

On the store page, the minimum required Unity version is listed:

Unity’s Package Manager will still allow you to import it into older versions! This is completely your own responsibility! Script compile- or shader errors may occur.

Please always check the “compatibility” page linked in the description! This goes into detail about which versions are supported.

The minimum supported version will be raised when/if:
– Support for a newer version makes backwards compatibility a nightmare.
– Unity drops support for it (LTS term has ended).
– The percentage of spending users on the Asset Store, using this version drops below 10%.
– Console SDK’s (Playstation, Xbox, Switch, etc) no longer allow games to be published using this version.

Alpha, beta and preview versions of Unity are to be used at your own risk, they are not supported. Once a release version is available, support will be verified and an update may follow with fixes.

A maximum supported version may be set if:
– Compatibility with a new version of Unity isn’t possible, where a redesign is required (eg. new rendering API, deprecating the current one).
– Backwards compatibility with older versions cannot be provided.

Please do feel free to ask for clarification on any of the listed features, or about anything not explicitly mentioned.

On the store page, the “Technical Details” section also holds some key information worth checking.

There is often a “compatibility” page linked at the top of an asset’s description. This covers all known details extensively and is updated should anything change.

Regarding refunds, please see the asset store refund policy first.

Requests for free vouchers really aren’t constructive and will have to go unanswered.

For educational purposes, or events, you should contact the asset store staff directly. They may (after inviting publishers to participate) provide you with a number of vouchers.

Only 12 vouchers are made available every year, so they are strictly used for publisher collaboration, and organized giveaway events.

Asset store publishers have no means to create discount codes, or create upgrade discounts for individual accounts.

Though the consideration is appreciated, I’m not looking to pick up contracting/commissioned work in the foreseeable future. The asset store really does occupy all of my time and interest 🙂

Everything within an asset’s package is equal, demo scene content included. Please do keep in mind that demo scenes are built strictly… as demo’s. Meshes may not contain LODs or colliders.

If the content falls under a different license (eg. CC0 or Unity Companion License) this will be noted in a “license.txt” file in the folder, and in the asset’s store page description.

(This applies to everything on the Unity Asset Store)