I’m about to publish a Blender addon in my store and I get an error that I don’t understand: “Listing promotion requires at least one asset format”. I have read all the guides and Fab documentation and it doesn’t say anything about it. Before trying to publish it I contacted Fab and they told me that the platform allowed to publish Blender addons without any difficulty. I interpret the error as that my product should have some file in UE or Unity format, but obviously this doesn’t apply to a Blender addon.
The only file I have included in Additional Files is a ZIP file containing the addon, but if that is causing the problem, doesn’t the documentation say that zip files are accepted? Why is this happening? Is there any restriction? Is it part of a bug in the platform? What is a Listing Promotion? What is meant by asset format?
What type of bug are you experiencing?
Publishing
Steps to Reproduce
Upload the zip file of your product and click submit for review
Expected Result
The expected result is that they will let me submit my Blender addon for review and publication.
Observed Result
Error while sending to review: Listing promotion requires at least one asset format.
Hi @binatheis . Thanks for explaining the issue. Is the file that you’re attempting to upload a .blend? Or some other format?
For context, when you started your listing, if you selected “Tools & Plugins”, you have to upload at least one UE or Unity file. If you attempt to only include other formats as “Additional Files”, you won’t be able to submit the listing for publication.
If your add-on is a .blend, for example, then you could try uploading it as a Smart Asset instead.
The file is a ZIP format that contains a folder with all the Python code for a Blender addon. Fab support told me that the platform supports Blender addon and the Blender addons are like what I have been describing: his ZIP contains a folder that contains all the python code.
Ok. I’m sorry to say that we can’t support Blender add-ons yet. Keep an eye out, though, as it’s on our list of things to add support for.
And apologies for the message from support - I think the question was not understood by our team in the way that you meant it and that’s why you received the response that you did. Thanks for taking the time to discuss this.
Oh, too bad, I was so excited to be able to share my addon with the Fab audience. I’ll keep an eye out for any updates. Isn’t there an estimated time to add that compatibility?
