The "Path Maker" add-on allows you to write tags in some output paths. Tags will be replace at render time by a string generated with a line of code, a python script or an hardcoded string.
It supports:
For example: The tag <scene> can be replace by "bpy.path.display_name_from_filepath(bpy.data.filepath)" so that an Output Path like "C:/hello/<scene>/world" will now be "C:/hello/file_name/world".
Fix minor issues from last version
This extension does not require special permissions.
The addon works, and the information within the .toml
files is correct.
In the .toml
file, the email address is not enclosed in <>. I'm not sure if it's required, but you can replace maintainer = "Lucas Boutrot lucas.boutrot@gmail.com"
with maintainer = "Lucas Boutrot <lucas.boutrot@gmail.com>"
.
LGTM, nice little add-on by the way :)
The <> for emails is not being reinforced now, but would be welcome in future versions indeed. You can also optionally cleanup the manifest by removing all the optional parameter lines (the ones commented out with #).
Not the right place to ask indee :) better to go to one of the community support channels: https://www.blender.org/community/
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.
That's strange. MIT should have been accepted (SPDX:MIT).
Could you please report it as a bug? https://projects.blender.org/infrastructure/extensions-website/issues
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.
Description required.