Bulk Asset Tools add options in the Asset Browser to allow editing the data of multiple assets at the same time, even if they do not exist in the same file. Add metadata, tags, etc. Move them between asset categories too.
Fix error on exit.
This extension requests the following permission:
Add-on expects to have access to filesytem.
Version 1.7.1 now installs and works with Extensions locally.
Nice add-on. I'm approving it for now.
If you want the user interface to be more aligned with Blender you should remove the=== Bulk Asset Tools ===
. To still convey the idea of bulk actions you could:
Great, I'll do that.
if bpy.context.preferences.addons['bl_ext.user_default.bulk_asset_tools'].preferences.background == True:
This is incorrect as bl_ext
isn't hard coded, please use the modules __package__
, see:
https://docs.blender.org/manual/en/dev/extensions/addons.html#extensions-and-namespace
uploaded new version: 1.7.2
We've added new mandatory fields: Featured Image and Icon. Featured Image is shown at the home page instead of the first preview image, and icon is shown in the extension's title (and later will be shown in Blender as well).
Could you please update your extension with an icon and a featured image?
Apologies for the late heads up.
uploaded new version: 1.7.3
This is marked as "Awaiting Changes" for some reason
Hey everyone,
Just a heads-up about a recent change regarding the licensing of add-ons on the Blender extension platform. Moving forward, all add-ons will need to be released under the GNU/GPL 3.0 license (SPDX:GPL-3.0-or-later). This is mainly to keep things simple and consistent across the board.
Previously, we accepted various licenses as long as they were compatible with Blender’s distribution. However, to avoid any confusion and streamline the process, all add-ons using the bpy API should now be presented as GPL 3 (the same license the Blender bundle is distributed). Regardless of whether the original code was under GPL 2, or something else like MIT or ZLIB.
Existing add-ons versions won't be affected. However, new updates will need to comply to the revised requirements.
Thanks for understanding, and feel free to reach out if you have any questions.
Sign in to comment.
The
blender_manifest.toml
isn't located in the same directory as the__init__.py
so the extension installs but fail to enable. Please check the extension works locally before uploading.Note that this was failing silently, now an error is reported.