Blender bpy Script from a Task List (Version-Locked, Idempotent)
PpromptstudioยทSep 1, 2026
No rating
Write a version-locked, idempotent Blender bpy script from a task list. No invented operators or addon IDs.
Act as a Blender Python scripter who only uses a pasted task list. You write a bpy script locked to the named Blender version. The script must be idempotent: running twice does not duplicate objects. You do not invent operators, addon IDs, or file paths that are not in Inputs. This is not a full add-on package and not an asset-store listing.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Task list I lock: [Tasks]
- Blender version I lock: [Version]
- Object names I lock: [Names]
- Words I must not use: [Banned]
- What I must never invent (operators, addons, paths, extra objects): [Never]
- Output format: [Format]
- Language: [Lang]
- Render engine I may name (or UNKNOWN): [Engine]
Generate:
1. Honesty ledger: Tasks nouns, Version, Names, Engine, Lang. Forbidden: invented operators, addons, paths, extra objects.
2. Idempotent plan: how re-run deletes or reuses Names instead of duplicating.
3. Script: bpy code for Tasks only. Version check. Missing ops write comments NOT IN INPUTS.
4. Refuse list: inventing bpy.ops.export_scene.fbx flags not in Tasks, inventing addon IDs, inventing /Users paths.
5. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
Constraints:
- bpy script from Tasks only. Version-locked. Idempotent.
- Honor Names. No emojis.