Compatible with Blender 3.6 +
see all features
watch the tutorial
Ask for support on Discord
No changelog for this release.
This extension requests the following permissions:
Export objects and biomes to external blend files
Update from GitHub if installed as addon rather than extension
Thanks for submitting this add-on, a few remarks:
Add-ons should not be including their own updating functionality as this is is handled by Blender directly now.
The add-on is not working at the moment, please Install from Disk to test if everything is working well.
The error (NameError: name 'bl_info' is not defined) seems to be related to the auto-updater though.
I disabled the auto updating functionality, everything should work as expected. I included the copyright as the first commented line in the __init__.py
, should I include it in a different way?
Also, I changed my BlenderID name to orencloud but it doesn't seem to update, am I doing something wrong?
By the way, I'm running into a few issues with the add-on:
But also if all you are trying to do is to open the folder, you can probably do it by calling whatever Blender calls when you alt+click on a folder button, no?
I also get an error while clicking around on most of the Utilities operators. (which the default Cube, and a "painted" curve.
All that said maybe I just need to understand the documentation a bit more. Or maybe the add-on as it is is not supporting all the OSs (which is fine, we just don't have yet the field on the manifest to communicate that). That wouldn't get on the way of approving the add-on. But it is nice to know on which OSs it is working at the moment.
As for the copyright I was referring to the manifest. At the moment what you have is:
## Optional: required by some licenses.
#copyright = [
# "2023-2024 orencloud",
# "1998 Company Name",
#]
And I believe that what you want is:
copyright = [
"2023-2024 orencloud",
]
I just added some warnings when misusing the utilities operators. All the main features should work, I haven't had any reports out of hundreds of active users. I'm also developing on windows, so I'll look into the "startfile" equivalent for Mac users, but it's an inconsequential feature of the addon and it doesn't affect the workflow at all. I also fixed the copyright. Let me know if there's anything else and thank you.
Everything seems to work on my side (Windows)! You are just missing the Icon and the extension can be Aprouve
Other things that can be taken into consideration:
Hello!
In 4.2 new "Online Access" property was added in preferences. It's a read-only property that Blender and add-ons should refer to. Add-ons that access the internet are now expected to check for bpy.app.online_access
and not connect if user turns it off.
Could you please update your add-on to adapt to that requirement? You can read more here https://developer.blender.org/docs/release_notes/4.2/python_api/#additions
Can you provide a descriptive tagline for your extension? Using the name of your add-on as a tagline will not help the user understand what the extension does.
I noticed that you still have bl_idname = __name__
instead of bl_idname = __package__
. To properly convert your add-on as an extension, you can refer to the 4.2 add-on documentation.
Can you please put description inside the actual description instead of linking to external website? Users should be able to learn all about add-on without leaving the website.
While markdown on here doesn't offer as much customization as your website, it supports texts, images, and gifs. You can recreate what you have on your website here in some form. You can still have link to your website, but showcase add-on here so people can see what it is
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.
Extension is ready for initial review