I made a custom postprocessing and would like to include it into the AssetStore asset. The effect is based on LEGACY IMAGE EFFECTS
from Unity Essentials here:
Means my script derives from PostEffectsBase.
Means it can not be “normally” included into the asset folder, because it would generate errors. The instruction should tell the user to import the precedent asset and then what?
Should my file be zipped inside my asset to prevent compilation?
Or saved as .txt, and then tell to change extension?
How to properly manage this?
Do not save as .txt.
Do not put it in a zip file.
The Asset Store reviewer will reject your asset if you do either of these.
Submit the folder containing your asset. At the top of your asset’s description, state that it requires Legacy Image Effects. You can use < strong > and < a > tags in your description, so you could add it like this:
Thank for the answer.
I think the simplest would be to create an additional unitypackage available online for download. This is going to be a minor feature, and I wouldn’t like to make an additional hassle for those not interested. That way I should be able to put this minor feature in a separate scene in the demo, and then tell if you like this, please import the (selected files from) Legacy effect first and my unitypackage the second.
If the custom postprocessing is not the main part of your asset, include it in a .unitypackage file. The Asset Store allows this. This way your customers won’t have to download something extra from your website.