smoke-gated on 5.2 LTS + 4.5 LTS · exit 0

Blender Python
that actually runs.

Skills, rules, snippets, and starter templates that teach Cursor and Claude Code the bpy that works — backed by runnable examples asserted headless on Blender 5.2 LTS and 4.5 LTS before they ship.

Claude Code
1 /plugin marketplace add TMHSDigital/Blender-Developer-Tools@plugin-dist
2 /plugin install blender-developer-tools@blender-developer-tools
Render Result 8 of 56 frames

Every render here is code that runs.

These aren't mockups. Each example runs headless on Blender 5.2 LTS and 4.5 LTS in the smoke workflow, asserts its own correctness, and exits non-zero if the API drifted. Each still was rendered by that same script.

69 examples: 56 rendered · 13 check-only (data contracts with nothing to see). List the check-only examples

Open the full gallery →

A smooth candy-red hatchback in front three-quarter view with tinted glass, a chrome sill, five-spoke alloy wheels, and matched headlamps and mirrors either side of one centered grille.
car-mirror-symmetry A stylized hatchback lofted as one half (52 stations, 13-point rings) and completed by the Mirror modifier, evaluated through the depsgraph. Wheels, lamps, grille, door mirrors and handles mirror about object origins parked on the symmetry plane; the grille is authored as a half and welded on it.
A white soccer ball with black pentagon panels and dark stitched seams, pressed into mown pitch turf on a chalked penalty spot with a touchline behind it.
soccer-ball-goldberg A soccer ball as a Goldberg polyhedron: a bmesh icosphere truncated at 1/3 per edge, faces ordered by link-topology walks, panels bound by face vertex count.
Twelve red-and-brass spotlight heads on low and high stands in an open ring, every lens swung to face a glowing amber orb on a brass pedestal.
damped-track-aim Aim constraints via the data API — Object.constraints.new('DAMPED_TRACK') with target and TRACK_Z, not bpy.ops.object.constraint_add in a headless loop. Gallery still: twelve spotlight heads on stands, all swung onto one glowing orb.
Two identical porcelain chess kings on dark plinths: the left, labelled LINKED, glows under an amber key; the right, labelled UNLINKED, stays cool grey.
light-link-studio One key, one hero: a light linked to a receiver collection lights only the hero, proven by two pixel renders in one pass. Linked: 3.6x luminance ratio; unlinked in the same check: the decoy rises 233% while the hero holds at 0.3% drift.
A red and yellow fire hydrant wrapped in a cyan wireframe convex collision hull.
collision-hull-proxy A fire hydrant street prop inside its compound collision shell: four convex pieces hulled by bmesh.ops.convex_hull from a coarse inflated cage. The dense render mesh is never hulled - its hull would measure 380 faces, over the 255-face per-piece engine budget. Closed-form plane tests prove containment, convexity, watertightness, outward winding, and Euler characteristic 2 per piece.
Three ribbed bellows hoses with brass collars on steel foot flanges, banded teal to amber to coral, standing straight, half curled and fully curled by an armature.
armature-bend Rigging end to end in the data API — edit_bones chain construction, name-bound vertex groups with smoothstep blend zones, posing, and depsgraph evaluation — bending a ribbed bellows hose through rest, half, and full curl.
A brass fourteen-tooth gear meshing with a blued pinion and a spoked gunmetal wheel, each bolted through a hub to a dark steel backplate on a walnut plinth.
bmesh-gear A 14-tooth gear built entirely with bmesh — profile ring, face, extrude — with bm.free() in a try/finally, exactly as the ownership contract demands.
A sci-fi corridor built from snapped modular segments, with painted teal wall panels, diamond-plate walkways, hazard-striped trim rails and a lit doorway at the far end.
modular-kit-snap A tiling corridor kit whose open-end boundary verts snap to the tile grid, so instances at 4 m multiples join with zero gap or overlap.
Install

Install it in your agent.

  1. Claude Code: /plugin marketplace add TMHSDigital/Blender-Developer-Tools@plugin-dist then /plugin install blender-developer-tools@blender-developer-tools. The 26 skills load when a task matches; the rules come along as the blender-rules skill
  2. Cursor: git clone --branch plugin-dist --single-branch https://github.com/TMHSDigital/Blender-Developer-Tools.git ~/.cursor/plugins/local/blender-developer-tools, then reload the window; Customize lists the 26 skills and 16 rules, and the plugin applies the rules for you. This clones only the 0.3 MB plugin build, not main
  3. Other agents (Codex, Copilot, Windsurf): clone the same slim build (git clone --branch plugin-dist --single-branch https://github.com/TMHSDigital/Blender-Developer-Tools.git) and copy its skills/* into .agents/skills/, append exports/AGENTS.md to your project's AGENTS.md for the rules, and for Copilot copy exports/copilot/blender-python.instructions.md into .github/instructions/
  4. Optional, live session: /plugin install blender-live-session@blender-developer-tools adds the official Blender Lab MCP server (needs uv and Blender 5.1+ with its add-on) so the agent can inspect and drive your open scene, plus a skill that has it read before it mutates and prove changes headless. See the README's Live Blender session
  5. Grab snippets/ and templates/ as starting points for add-ons and headless batch jobs
Showcase 6 of 80 pieces
What's new v0.159.0
Skills 26 loaded

Workflows the AI loads by name.

Each skill is the canonical pattern for one job — operators, panels, bmesh, geometry nodes, slotted actions — plus the mistakes AI assistants actually make there. Where 4.5 LTS and 5.x diverge, both code paths are shown.

addon-scaffolding Scaffold a Blender add-on as an Extensions Platform package: blender_manifest.toml, modular file layout, register_classes_factory, symmetric register/unregister.
When to use (4)
  • Wants to start a new Blender add-on
  • Mentions bl_info, blender_manifest.toml, "extension", "register_classes_factory"
  • Is migrating an existing add-on from the legacy bl_info format to the Extensions Platform
  • Is unsure which file layout or registration pattern to use for Blender 4.5+ or 5.x
ai-mesh-cleanup Ordered cleanup for an imported generated or scanned mesh before it goes to an engine: scene units, apply rotation and scale, origin to base, recalculate normals, evaluated triangle count, decimate to a budget, convex collider.
When to use (4)
  • Has a generated or scanned GLB/glTF/FBX that is not engine-ready
  • Mentions unit scale, unapplied transforms, triangle budget, LOD, or a collision hull
  • Wants a headless cleanup pass (import in, cleaned mesh out)
  • Is about to run mesh operators on an import without checking scale
bake-high-to-low Cage-bake high-poly surface detail onto a low-poly target as a tangent-space normal map with bpy.ops.object.bake (Cycles, selected-to-active, active Image Texture node, UV layer, save_render).
When to use (4)
  • Wants a tangent-space normal map from a dense source onto a game-resolution mesh
  • Mentions cage bake, use_selected_to_active, cage_extrusion, or bpy.ops.object.bake
  • Has an LOD from DECIMATE COLLAPSE (or a retopo) and needs the missing surface detail in a map
  • Is about to call bake from EEVEE, on GPU in CI, or with bake_type=
bl-info-migration Migrate a legacy bl_info add-on to the Extensions Platform in three steps, with a before/after diff and the dual-format pattern.
When to use (5)
  • Has an existing add-on with a bl_info = {...} dictionary at the top of __init__.py
  • Wants to publish to extensions.blender.org or distribute as a .zip for the Extensions Platform
  • Asks "is bl_info dead?" or "do I have to migrate?"
  • Sees a deprecation warning at install time about legacy add-ons
  • Mentions blender_manifest.toml, "Install legacy Add-on", or "the new extension system"
compositor-nodes Build and render through the scene compositor from Python across the 4.5 LTS to 5.x split: scene.use_nodes plus scene.node_tree and a Composite node on 4.5, a CompositorNodeTree node group assigned to scene.compositing_node_group with interface sockets and a Group Output on 5.x, a Render Layers to Glare (Fog Glow) chain, the Glare node's…
When to use (5)
  • Builds, edits or inspects compositor nodes from a script
  • Mentions scene.node_tree, scene.use_nodes, compositing_node_group, CompositorNodeTree, CompositorNodeGlare, CompositorNodeRLayers, or CompositorNodeComposite
  • Hits AttributeError on scene.node_tree after moving to 5.x
  • Sets glare.glare_type / glare.quality / glare.size on 5.x and gets AttributeError
  • Wants bloom and reaches for scene.eevee.use_bloom (removed in 4.2, absent on 4.5 and 5.x)
constraints-and-parenting Parent objects without moving them, aim them with constraints, and author empties as engine attach sockets, all on the data API: child.parent plus matrix_parent_inverse = parent.matrix_world.inverted(), stale matrix_world until view_layer.update(), Object.constraints.new('DAMPED_TRACK') read back through the evaluated depsgraph…
When to use (6)
  • Parents objects from Python with child.parent = ... and the child jumps
  • Mentions matrix_parent_inverse, matrix_world, matrix_basis, or matrix_local
  • Reads matrix_world right after editing location / rotation_euler and gets old numbers
  • Adds constraints (DAMPED_TRACK, TRACK_TO) or calls bpy.ops.object.constraint_add in a loop
  • Builds named socket empties (SKT_*) that a game engine or spawn system attaches modules to
  • Freezes a rig with transform_apply and the children's local transforms change
curves-and-text Build legacy Curve and TextCurve datablocks from Python: bpy.data.curves.new(type='CURVE' or 'FONT'), splines.new('BEZIER'), bezier_points.add, handle types, bevel_depth, bevel_resolution, resolution_u, use_fill_caps, extrude, TextCurve.body, align_x/align_y, the built-in Bfont, and reading the tessellated result through…
When to use (5)
  • Creates a curve or 3D text object from a script (bpy.data.curves.new, type='CURVE' or type='FONT')
  • Mentions splines, bezier_points, bevel_depth, bevel_resolution, use_fill_caps, extrude, TextCurve, body, align_x, or Bfont
  • Needs the vertex positions, bounds or face count of a beveled curve or extruded text
  • Reports that a tube renders as a hollow pipe, or that text dimensions do not match the numbers they set
  • Hits ReferenceError reading a mesh after to_mesh_clear()
custom-properties Define and bind custom properties with bpy.props annotations, PropertyGroup and PointerProperty, and choose where to store them (Scene, Object, WindowManager, AddonPreferences).
When to use (4)
  • Wants to attach data to objects, scenes, or other Blender datablocks that survives save and load
  • Mentions bpy.props, PropertyGroup, PointerProperty, "custom properties"
  • Is unsure where to store add-on settings
  • Sees a deprecation warning about property assignment
depsgraph-and-evaluated-data Read the evaluated geometry the user actually sees through the dependency graph instead of raw obj.data: evaluated_depsgraph_get, evaluated_get, to_mesh and to_mesh_clear lifetimes.
When to use (5)
  • Is writing an exporter, measurement script, or inspection tool
  • Reports that "modifiers are missing from my export" or "the vertex positions don't match what I see"
  • Mentions evaluated_depsgraph_get, evaluated_get, to_mesh, to_mesh_clear
  • Reads from obj.data.vertices and gets unexpectedly raw geometry
  • Needs final positions after armature deformation, shape keys, modifiers, or geometry nodes
drivers-and-app-handlers Drive properties from expressions with the Driver API (driver_add, driver_namespace for custom Python functions) and react to events with bpy.app.handlers (load_post, save_pre, frame_change_post, depsgraph_update_post, exit_pre in 5.1+).
When to use (5)
  • Wants property A to follow property B with some math (driver)
  • Asks about driver_add, FCurve.driver, driver.expression, driver_namespace
  • Wants to run code on file save, file load, frame change, depsgraph update, or process exit
  • Mentions bpy.app.handlers, save_pre, load_post, depsgraph_update_post, exit_pre
  • Has a driver expression that fails security checks because it tries to call a Python function
engine-export-presets Export presets for Unity, Godot and Unreal. glTF is +Y up and meters by spec, so every engine gets export_yup=True with no scale bake (Unreal converts to centimeters on import); FBX takes axis_forward/axis_up plus global_scale.
When to use (4)
  • Needs a Unity, Godot, or Unreal export from Blender Python
  • Mentions Y-up, Z-up, centimeter scale, export_yup, axis_forward, or axis_up
  • Is about to pass FBX axis kwargs to bpy.ops.export_scene.gltf
  • Wants a headless preset the later ai-asset-pipeline-template can call
extension-runtime-and-packaging Ship and run a Blender extension after its first install: bundled wheels, user data that survives upgrades via bpy.utils.extension_path_user, the network permission and bpy.app.online_access, bl_ext package names, and blender --command extension validate/build/server-generate in CI.
When to use (5)
  • Needs a third-party Python package inside an extension (requests, numpy, Pillow)
  • Writes settings, caches or downloads from an add-on and asks where they should go
  • Makes network calls from an add-on, or asks about the network permission
  • Builds, validates or publishes extension zips, locally or in CI
  • Hits ValueError: The "package" does not name an extension, or imports that work in a folder add-on but break once installed as an extension
geometry-nodes-python Build Geometry Nodes trees from Python: node_groups.new, tree.interface sockets, nodes by RNA identifier, links, Repeat and for-each zones, Bundles, and applying the tree as a NODES modifier including the 5.1 vs 5.2 modifier input API.
When to use (4)
  • Wants to build a Geometry Nodes tree from a script rather than the editor
  • Mentions GeometryNodeTree, node_groups.new, tree.interface, tree.links.new
  • Needs to apply a generated GN tree as a modifier on an object
  • Asks about Bundles, Repeat Zones, or for-each Element zones from Python
gpu-drawing-and-overlays Draw viewport overlays and offscreen images with the gpu module instead of the removed bgl: SpaceView3D.draw_handler_add/remove symmetry, gpu.shader.from_builtin names, gpu_extras.batch.batch_for_shader, gpu.state for blending, depth and line width (POLYLINE shaders), blf text, tag_redraw, and GPUOffScreen with gpu.init() for…
When to use (4)
  • Wants to draw lines, points, shapes or text over the 3D viewport or an image editor from an add-on
  • Has add-on code with import bgl, bgl.glEnable, bgl.glLineWidth, or gets ModuleNotFoundError: No module named 'bgl' on 5.x
  • Wants to render something with the GPU into an image from a script, including headless
  • Sees SystemError: GPU functions for drawing are not available in background mode
grease-pencil-v3 Create and inspect Grease Pencil v3 (GPv3) data from Python: the datablock address split (bpy.data.grease_pencils_v3 on 4.5 LTS, bpy.data.grease_pencils on 5.x), layers.new -> frames.new(n).drawing -> add_strokes([counts]) -> per-point position/radius/opacity/vertex_color, lazily materialized drawing.attributes, and the Line Art modifier…
When to use (5)
  • Creates Grease Pencil objects, layers, frames, or strokes from a script
  • Mentions grease_pencils, grease_pencils_v3, GreasePencil, GPencilStroke, drawing, add_strokes, or the LINEART modifier
  • Ports pre-4.3 GPencil code (frames that carry .strokes directly) to 4.5 LTS or 5.x
  • Hits AttributeError on bpy.data.grease_pencils_v3 (5.x), on frame.drawing (legacy data on 4.5), or on the Line Art modifier's thickness (5.x)
  • Gets zero Line Art strokes and does not know why
headless-batch-scripting Run Blender unattended with blender --background --python, arguments after the -- separator, --factory-startup and --python-exit-code, and temp_override for operators that need context.
When to use (4)
  • Wants to render, export, or process .blend files from a CLI or CI pipeline
  • Mentions blender --background, --python, "headless", "batch render", "no UI"
  • Has an operator script that fails with RuntimeError: Operator bpy.ops.X.Y.poll() failed, context is incorrect
  • Needs to pass arguments to a Blender Python script
images-and-pixels Create and edit bpy.types.Image pixel buffers from Python: bpy.data.images.new, Image.pixels bulk access with foreach_get/foreach_set, the flat always-RGBA bottom-left-origin layout, byte vs float_buffer storage, colorspace_settings, and saving PNG vs OpenEXR with alpha through Image.save (filepath_raw, file_format) vs Image.save_render…
When to use (5)
  • Creates an image with bpy.data.images.new and fills it from code (test cards, masks, lookup textures, bake targets)
  • Reads or writes Image.pixels, or mentions foreach_get / foreach_set, float_buffer, is_float, channels
  • Hits TypeError from pixels.foreach_set / foreach_get (wrong length: RGB stride, or a buffer sized before Image.scale())
  • Sees an image land upside down in the saved file, or pixels that changed after Image.save()
  • Saves PNG or OpenEXR and loses alpha, gets low-alpha pixels clamped to white, or finds save_render wrote a PNG despite image.file_format = "OPEN_EXR"
mesh-editing-and-bmesh Create, edit and read meshes efficiently: when to use bpy.data, bpy.ops or bmesh, the bmesh.new / try / finally / free pattern, foreach_get and foreach_set for bulk data, and evaluated meshes for modifier results.
When to use (6)
  • Wants to create, modify, or read mesh geometry from Python
  • Mentions bmesh, mesh.vertices, foreach_set, from_pydata, evaluated_get
  • Has a script that's slow and uses bpy.ops.mesh.* in a loop
  • Needs the mesh after modifiers (subdivision surface, mirror, geometry nodes) have been applied
  • Asks why their bmesh script crashes on the second run
  • Reads or writes sculpt automasking (use_automasking_*, mesh_automasking_settings) and hits AttributeError on 5.2
operators Author bpy.types.Operator classes: bl_idname naming, poll / invoke / execute / modal lifecycle, bl_options (REGISTER, UNDO, INTERNAL, BLOCKING), operator properties and defensive context handling.
When to use (4)
  • Wants to create a new bpy.types.Operator
  • Mentions bl_idname, bl_label, bl_options, "redo panel", "F6 panel", "operator props"
  • Needs an action triggered from a button, menu, keymap, or chat command
  • Asks why their operator's properties don't show up in the redo panel
porting-to-blender-5 Port an add-on or script from Blender 3.x/4.x to 5.x (5.2 LTS) while keeping 4.5 LTS working: a triage recipe that runs the code headless on the target version and maps each traceback to its fix, and one table of every break the pack covers (bgl, action.fcurves, use_auto_smooth, Principled sockets, sequences, context dicts, ID…
When to use (3)
  • Asks to "port", "upgrade", "update" or "make compatible" an add-on or script for Blender 5.x
  • Gets AttributeError, KeyError, TypeError or ModuleNotFoundError from code that worked on an older Blender
  • Wants one codebase that runs on both 4.5 LTS and 5.2 LTS
procedural-materials-and-shaders Build materials and shader node graphs from Python: bpy.data.materials, node_tree, Principled BSDF and its 4.0+ socket names, default values, links and shader node groups, for EEVEE and Cycles.
When to use (6)
  • Wants to create or edit materials from Python rather than the shader editor
  • Mentions bpy.data.materials, node_tree, ShaderNodeBsdfPrincipled, inputs[...].default_value
  • Needs to generate many materials parametrically (asset libraries, batch import, color variations)
  • Asks about EEVEE Next vs Cycles material differences
  • Restricts which objects a light illuminates (light linking, receiver_collection, blocker_collection)
  • Asks about "Layered Textures" or "the new shader system" (see version-correctness section)
slotted-actions-animation Create and edit animation from Python under Slotted Actions (Blender 4.4+): Action, slots, layers, strips, channelbags. Bind the action slot, then reach F-curves through a channelbag; action_ensure_channelbag_for_slot exists only on 5.0+, so use strip.channelbag(slot, ensure=True) on 4.5 LTS.
When to use (4)
  • Wants to create or edit animation from Python in Blender 5.x
  • Mentions Action, slot, channelbag, keyframe_insert, fcurves
  • Has older 4.x animation code (action.fcurves.new(...)) that no longer works in 5.x
  • Asks how to insert keyframes programmatically and have them persist
timers-modal-and-threading Run long or repeated work in a Blender add-on without freezing or crashing it: bpy.app.timers return values and persistent=True, modal operators driven by event_timer_add, and worker threads that hand results to the main thread through a queue.
When to use (6)
  • Wants something to happen later or repeatedly (polling, autosave, a progress readout)
  • Runs slow work (network, file processing, a solver) and the UI freezes
  • Calls bpy from a threading.Thread and gets crashes or corrupted data
  • Writes a modal operator, or one that never stops
  • Registers a timer in blender --background and it never runs
  • Loses a timer after File → Open or wm.read_homefile
ui-panels Author bpy.types.Panel UI: bl_space_type, bl_region_type, bl_category sidebar tabs, declarative draw(), layout row, column and split, sub-panels, and conditional UI with enabled and active.
When to use (4)
  • Wants a sidebar tab in the 3D viewport, properties editor, or any other space
  • Mentions bpy.types.Panel, bl_space_type, bl_region_type, "N panel", "sidebar"
  • Needs to expose properties or operators in a custom UI
  • Asks why a property is showing without a label or in the wrong column
uv-and-mesh-attributes Author per-loop and per-vertex mesh data from Python: UV layers (mesh.uv_layers.new, bmesh loops.layers.uv, the calc_uvs=True silent no-op), a second lightmap UV channel and its active / active_render flags, loop tangents (calc_tangents, bitangent_sign), color attributes and their CORNER vs POINT domain, shape keys (shape_key_add…
When to use (7)
  • Creates or edits UVs from a script (mesh.uv_layers, bm.loops.layers.uv, calc_uvs=True)
  • Builds a second UV channel for baked lighting, or runs uv.lightmap_pack / uv.smart_project on it
  • Computes tangents for a normal-mapped game asset (calc_tangents, bitangent_sign)
  • Writes vertex colors (color_attributes, the deprecated vertex_colors)
  • Authors shape keys or reads a blended shape
  • Caps skin weights at four influences per vertex for a game engine
  • Reports a textured mesh that renders as one flat color, a UV op that wrecked channel 0, a crash or garbage values after calc_tangents, or weights that sum short of one
vse-python Build and inspect Video Sequence Editor timelines from Python: SequenceEditor.strips vs the removed .sequences, new_effect length vs frame_end, strip transforms, and the 5.2 COLOR strip width/height bake from scene resolution.
When to use (5)
  • Builds or inspects a VSE / sequencer timeline from a script
  • Mentions sequence_editor, strips, sequences, new_effect, COLOR strips, or StripTransform
  • Hits AttributeError: 'SequenceEditor' object has no attribute 'sequences' on 5.x
  • Hits TypeError on new_effect kwargs (frame_end vs length)
  • Renders a sequencer composite whose COLOR cells ignore transform.scale_* after a resolution change
Rules 16 active

Anti-patterns, caught before they ship.

Guardrails that load whenever a matching file is open, for the failure modes that make Blender Python look right and run wrong: ops in loops, leaked bmesh, deprecated context dicts, per-vertex Python loops.

RuleScopeFlags
always-free-bmesh **/*.py Flag bmesh.new() calls without a paired bm.free() in a try/finally block. Blender frees an unreferenced BMesh only when its Python wrapper dies, which a traceback, global, closure or modal operator can delay for the whole session; an explicit free() in finally releases it deterministically.
branch-eevee-engine-id **/*.py Flag render.engine = 'BLENDER_EEVEE_NEXT' or = 'BLENDER_EEVEE' written without a version branch. EEVEE Next used the id 'BLENDER_EEVEE_NEXT' on 4.2 through 4.5 LTS and took back 'BLENDER_EEVEE' in 5.0; each id raises TypeError (enum not found) on the other side. Branch on bpy.app.version >= (5, 0, 0).
no-bgl **/*.py Flag import bgl and any bgl. call. The bgl OpenGL wrapper was deprecated in 3.x and is gone in Blender 5.x (importlib.util.find_spec('bgl') is None on 5.0, 5.1 and 5.2), so an add-on that imports it fails to register. Draw with the gpu module, gpu.state and gpu_extras.batch instead; see the gpu-drawing-and-overlays skill.
no-legacy-action-fcurves **/*.py Flag action.fcurves, action.groups and action.id_root on an Action. Blender 5.0 removed the flat legacy Action API (AttributeError on 5.x); F-curves live in a channelbag per slot. On 4.4/4.5 LTS the legacy path still runs but is a trap on a fresh Action (it creates a slot without binding it).
no-legacy-vse-sequences **/*.py Flag sequence_editor.sequences and .sequences_all. Both are gone in Blender 5.x (AttributeError on 5.0, 5.1 and 5.2), while .strips and .strips_all already exist on 4.5 LTS, so use those everywhere with no version branch. See the vse-python skill.
no-nodes-modifier-idprop-inputs **/*.py Flag writing a Geometry Nodes modifier input as an ID property (mod["Socket_2"] = value, mod[identifier] = value) without a version branch.
no-removed-normals-api **/*.py Flag the mesh normals API removed in Blender 4.1 — use_auto_smooth, auto_smooth_angle, calc_normals_split(), free_normals_split(), create_normals_split(). Each raises AttributeError on 4.5 LTS and 5.x. Use Mesh.set_sharp_from_angle, object.shade_auto_smooth, and Mesh.corner_normals (always current) instead.
no-unapplied-modifiers-on-export **/*.py Flag an export call on objects that still carry unapplied modifiers when the export arguments do not request evaluated geometry. The engine then receives the authored cage, not the modifier result.
prefer-data-over-ops-in-loops **/*.py Flag bpy.ops.* calls inside iteration over many objects, meshes, or frames. Each bpy.ops call triggers a full depsgraph evaluation and UI redraw; loops slow down by orders of magnitude. Use bpy.data.* and bmesh instead.
prefer-temp-override-over-context-copy **/*.py Flag uses of bpy.context.copy() to override context for an operator call. Passing a context dict to an operator was deprecated in Blender 3.2 and removed in 4.0, so it already fails on the 4.5 LTS fallback. Use bpy.context.temp_override(**overrides) as a context manager instead.
principled-v2-socket-names **/*.py Flag Principled BSDF inputs looked up by their 3.x names (inputs["Emission"], ["Specular"], ["Clearcoat"], ["Subsurface"], ["Transmission"], ["Sheen"]) or by index. Principled v2 (Blender 4.0) renamed them, so they raise KeyError on 4.5 LTS and 5.x.
target-extensions-platform-format **/__init__.py, **/blender_manifest.toml Flag new Blender add-ons that ship only a legacy bl_info dict without a blender_manifest.toml. New add-ons must use the Extensions Platform format. bl_info may appear alongside as a fallback for backward compatibility, but the manifest is the source of truth.
type-annotate-props-and-defend-context **/*.py Flag two related anti-patterns. (1) bpy.props defined as class-level assignments instead of type annotations (deprecated since 2.8). (2) Code that touches bpy.context.active_object without guarding for None, or that assumes the active object is selected.
use-correct-axis-rna-per-exporter **/*.py Flag export_scene.gltf calls that pass FBX axis_forward or axis_up, and export_scene.fbx calls that pass glTF export_yup. The two exporters do not share axis RNA.
use-foreach-set-for-bulk-data **/*.py Flag Python loops that set vertex coordinates, normals, UVs, or other bulk per-element data one element at a time. For meshes of more than a few thousand elements, this is 100x to 1000x slower than mesh.vertices.foreach_set("co", flat_array), which writes through to C-level storage in one pass.
validate-imported-mesh-scale **/*.py Flag a glTF or FBX import followed by mesh operations with no transform_apply and no unit-scale check. Generated files often arrive with non-identity object scale or a non-meter scene scale; mesh edits then bake the wrong size.
Snippets 31 patterns