Skip to content
← Back to work

03 — Technical Art & Tools

LinkFlow

A Blender dashboard for external libraries — health scores, dependency graphs, overrides and batch relinking.

Year
2026
Role
Design · engineering · release · support
Context
Blender Extensions (Light) · Superhive (Pro)
Type
Technical Art & Tools
Software
Python · Blender API · Asset Libraries · CI
Blender Extensions Superhive (Pro) Documentation
LinkFlow hero shot

Platform

Blender 4.5 – 5.2 LTS

Editions

Light (free) · Pro

Scope

40+ libraries in one panel

Stack

Python / Blender API

Demo

30 second capture: open a scene with 40 linked libraries, run the health check, batch-relink the broken ones.

.webm / .mp4

The production problem

  1. Pain

    Nobody could audit a scene

    Scenes linked libraries from three artists and two NAS paths. Answering 'what is this scene linked to?' meant going link by link through the outliner.

  2. Pain

    Broken paths surfaced too late

    A moved folder only showed up as pink geometry at render time — usually on the day of the delivery.

  3. Pain

    Overrides grew silently

    Local overrides accumulated across passes with no record of who made them or why.

  4. Result

    One panel instead of a ritual

    Health, dependency, override and batch operations moved into a single view with undo support.

Workflow before and after

Before — brokenAfter — batch relinkBefore — brokenAfter — batch relink

Same scene, four dead paths. Batch relink resolves them from the project root in one pass, with undo.

Inside the panel

Library list with live status badges
Library list with live status badges
Dependency graph — who uses what
Dependency graph — who uses what
Health dashboard + score
Health dashboard + score

How it works

LinkFlow reads the dependency graph directly from Blender's data API rather than parsing .blend files, so the panel reflects the live scene — including libraries linked after the file was opened.

Health checks run as a non-blocking pass: missing paths, stale caches and unexpected override states are flagged with severity, then offered as batch fixes. Every batch operation pushes onto Blender's undo stack, which is the difference between a tool artists trust and one they avoid.

The Pro edition adds dependency graph visualisation, custom views, library groups and CSV export for pipeline reporting; Light covers list, health and batch relink for free.

How the tool helps an artist — a real case

  1. Case

    Season handover, 40 libraries

    A scene passed between two artists had 40 linked libraries, four of them pointing at a folder that moved during a server migration.

  2. Before

    Grey-box hunt

    Traditional fix: click every object, find the pink ones, guess which library broke, re-link manually, re-check by eye.

  3. After

    Health check → batch relink

    Open the panel, run health check, four issues listed with paths, batch relink from the new root. Under a minute, verified by the score going green.

  4. Underneath

    Reversible by design

    Everything is undoable, and the dependency view shows which objects would be affected before anything is touched.

1Panel, every library
40+Libraries in one pass
0Objects clicked to diagnose
5.2LTS supported