Docs
Download

Add-on settings

Name, version, author and the other information Blender shows about your add-on.

The Addon panel in the node editor's sidebar (Scripting Nodes tab) names the add-on and holds what Blender shows about it in the Preferences and what the Extensions platform needs. The settings belong to the .blend file, like the node trees.

The Addon panel with Metadata open: tagline, author, version, tags, copyright, Blender version and permissions

Addon

Setting
Checkbox in the headerLive: runs the add-on in Blender while you edit it, rebuilt on every change. Turn it off to stop it running (the header says Addon (not running)); exporting works either way
Addon NameThe name shown in the Preferences. The add-on's Python module is made from it, shown below the field (import render_tools)
Persist AddonKeeps the live add-on enabled when you open another .blend file. Off: it's turned off with its file

Set the name before you share the add-on. Renaming it later renames the module, the class names and the operator ids (render_tools.my_operator), so users' shortcuts and scripts that call your operators break.

Metadata

Setting
TaglineOne line about what the add-on does. At most 64 characters, ending in a letter or digit
Author, EmailShown as the maintainer, Jane Doe <jane@example.com>. The email is optional
VersionMajor, minor and patch. Raise it with every release: Blender and the Extensions platform use it to offer updates
WebsiteA documentation or project page, starting with https://
LocationWhere to find the add-on in Blender, e.g. View3D > Sidebar > Render Tools
TagsCategories on the Extensions platform. The first one (alphabetically) is the add-on's category in the Preferences
CopyrightWho holds the copyright. Type a name and the current year is added (2026 Jane Doe); a year or range you type, like 2024-2026 Jane Doe, is kept
BlenderThe oldest Blender version the add-on works in. It starts at the version you build it in, because the generated code may use what's new in it
Up ToTurn it on to set the first Blender version the add-on doesn't work in. It has to be above Blender
PermissionsWhat the add-on does outside of Blender that users are asked to allow: Files, Network, Clipboard, Camera, Microphone. Each one turned on gets a Reason field

Permissions that nodes need are turned on for you and show Used by nodes: the file nodes need Files. Give them a reason anyway, like Saves presets next to the blend file; without one, a default reason is used. Python you write yourself (a Python node or a script) doesn't turn permissions on; do it here.

Add-ons are licensed under the GPL 3.0 or later, like Blender itself. Code using Blender's Python API has to be, and the Extensions platform only accepts it, so there's no setting for it.

Problems with the settings

Blender rejects add-ons whose tagline or reasons are too long or end in punctuation. Scripting Nodes shortens them when it writes the add-on. Settings it can't fix show a warning at the bottom of Metadata and are left out until they're fixed:

  • Email isn't an address
  • Website needs https:// and a domain
  • Copyright needs a year and a name: '2026 Jane Doe'
  • Tagline: 64 characters, end with a letter
  • Blender: Up To must be above the minimum
  • Give the add-on a name (Addon Name)

Overrides

The names in the generated code come from the Addon Name. Overrides sets them yourself, for example to keep them when you rename the add-on:

SettingDefaultUsed for
Module NameThe add-on name in lower case with _ (render_tools)The add-on's folder and Python module, and the extension's id
Class PrefixThe module name in upper caseClass names: RENDER_TOOLS_PT_render_tools
Idname NamespaceThe module nameOperator ids: render_tools.save_preset

Spaces and dashes become _, other characters are dropped. A name that would hide a Python or Blender module (math, bpy) gets _addon added.