A character pipeline should survive the second export. Before adding gameplay logic to an imported asset, decide which data comes from Blender and where the game-specific setup belongs.
Name the authoritative source for each change
Treat the Blender asset as the source for its mesh, skeleton and authored animation. Identify the Godot-side setup that belongs to gameplay, such as controllers, collision and scene organization. Follow Godot’s supported scene-import and inheritance workflows for your version.
Avoid relying on an unexplained edit to generated imported content. Even if it appears to work once, the next reimport is the test that matters.
Run a harmless revision test early
Change a small mesh detail in Blender without altering the skeleton. Re-export and inspect the character scene, animation references and gameplay behavior. Record what was preserved and what changed.
Then test a skeleton revision in a disposable copy. This is a separate, more disruptive case; do not assume it behaves like a mesh-only update.
Turn the result into a team rule
Document where artists change the source and where developers add game behavior. Include the expected import path and a short reimport checklist.
Keep a known-good asset revision so a broken handoff can be compared against it. A predictable update process saves more time than repeatedly rebuilding a scene after each character export.
For the bigger picture, use our free Rigify migration workflow and three-engine import test plan.
Official references and scope
Sources checked October 18, 2026. Interface names and capabilities can change; use the documentation for your installed version. The workflow above is an editorial checklist, not a published hands-on benchmark.

