MCP backend

Use when: Texture state animation, texture morphs, material state transitions, image sequence planning, masked wipes, glow reveals, texture registration, avoiding bad crossfades, GLB-compatible texture animation planning.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

Texture State Animation

This skill exists because “crossfade several full images” usually looks bad. Texture animation must be designed like motion graphics: registered states, constrained transition channels, and preview gates.

Failure modes to avoid

• Whole-frame crossfades between unrelated crops/compositions.
• Python frame handlers as the only playback mechanism when export/runtime support is needed.
• Texture swaps that change silhouette, camera crop, or scale at the same time as decorative motion.
• Mixing aura/background/HUD pixels into the avatar surface texture unless that is the intent.
• Morph pulses that break accepted geometry constraints such as constant depth.

Workflow