Scope, files and capture-contract answers.

It is a browser-based capture interface for layered-sprite character packages derived from canonical Blender master scenes. It configures animations, equipment, directions and pixel output before exporting COLOR and DEPTH PNG atlases with JSON manifests.

No. This Studio belongs to the independent DTWorldz Blender Sprite Pipeline. It contains no Unity code and produces portable PNG and JSON output without requiring a Unity project.

Not currently. The Studio reads catalog-generated packages built from this pipeline’s canonical Blender masters. The current public catalog provides male and female packages rather than arbitrary .blend uploads.

The current browser catalog contains two body variants, 39 Actions and 25 equipment items per body package. Capture profiles support 2, 4 and 8 directions.

A quick Action export produces a ZIP with a JSON manifest and body, equipment and combined COLOR/DEPTH PNG atlas pages. Batch export writes reusable body and equipment layers, per-Action manifests and library status metadata to a selected folder.

No. Named profiles and the latest working draft are stored in browser localStorage. They are not uploaded or synchronized to a server.

Exact parity is not claimed for every procedural Blender material. The current browser torch package uses a static flame baseline, and full real-asset garment deformation remains a separate production validation gate.

The RG16 DEPTH map lets a downstream renderer compare body and equipment pixels consistently. This preserves authored front/behind relationships while keeping layers reusable.