Using the Recorder¶
Recording a New Macro Set¶
The Recorder panel ready to record.¶
Expand the Recorder panel.
Click Start Recording (the button turns red and says “Recording Active”).
Perform any of the following actions to add macro entries:
- Right‑click method
Right‑click any button, property, or operator in Blender’s UI.
Choose Add Macro Entry from the context menu.
- Last Touched method
Click Get Last Touched to scrape recent commands from the Info area.
Select a command from the dropdown and click Add Selected, or click Add Sequence to add all commands.
- Asset methods
Click Append Asset, select a .blend file, then check the datablocks you want. Each becomes an entry.
Click Set Material to record an entry that assigns the most recently appended material (or the active object’s active material).
Click Set Geonode to record an entry that assigns the most recently appended node group (or the active Geometry Nodes modifier’s group).
After adding entries, you can reorder them using the Up/Down arrows, delete entries with the Trash icon, and edit each entry’s details (see Editing Recorded Entries below).
When you are satisfied, fill in the Name, Description, and select or create a Category / Subcategory.
Click Save Set to write the macro set to a JSON file.
The Recorder panel with several entries added.¶
Last Touched vs Direct Record Methods¶
Last Touched¶
The Last Touched method is a secondary way to record macros. It scrapes the Info Area for recent commands and converts them into macro entries.
However, it is not as comprehensive as the Direct Method, because not all Blender commands appear in the Info Area. For example, preference changes are not sent to the Info Area and therefore cannot be captured by this method.
Use Last Touched when:
You need to record an action after it has already been executed.
You need to record modal operators (e.g., Grab or Rotate) where the operator requires further input (such as mouse movement) before producing a final result.
You need to quickly record many default property values at once – for example, setting up the default values of a BSDF node.
Direct Recording¶
The Direct Recording method is the preferred way to record macros. It provides the most accurate context by capturing exactly what was clicked at the moment you add the macro entry. This results in more reliable and precise entries.
However, it does not record modal operators as comprehensively as the Last Touched method.
Use Direct Recording when:
You need to record an action before it executes.
You are changing most property values anywhere in the Blender UI, including Preferences.
Editing Recorded Entries¶
Select an entry in the Recorded Macros list to edit it.
Property entries show a live value widget. Adjust the value, then click Set Default, Set Min, or Set Max to update the stored values.
Operator entries allow you to edit the Python command directly.
Append entries let you edit the display name.
Set Material entries display the material name and slot index (read-only).
Set Geonode entries display the node group name and modifier name (read-only).
The Name field changes the entry’s display name.
The Command field shows the current Python command; edit it and press the checkmark to update.
The Toggle Path Type button (LINKED icon) converts property entries between absolute (bpy.data) and relative (bpy.context) paths. This is useful to make a macro set work across different scenes.
Tip
You can also use the Toggle Paths button at the bottom to convert all property entries in the cache at once.
Saving with Companion .blend¶
If your macro set contains explicit references to datablocks (e.g. bpy.data.materials[“MyMaterial”]), the extension will warn you when you save. It offers to create a companion .blend file that bundles those datablocks. The companion .blend is saved next to the JSON file and is automatically used when the set is played on another machine. This makes your macro sets truly portable.