Asset Pipeline

User-facing reference for the Asset Pipeline tool.

v0.9.4Godot 4.7 stable4.6.3 supportedReference
Tool pages are written for users and buyers; they explain what to use, what to avoid, and where v0.9.4 boundaries are.

Asset Pipeline

Status: Stable
Category: Asset
Use it when: you need to import/process user-owned or generated assets into project content.

First task

Import a user-owned image/audio asset and prepare it as project content.

Inputs

A file you created, own, or are licensed to use.

Outputs

Processed/imported project asset and metadata.

How it connects

Connects to converters, Generated Asset Browser, UI/Audio/VFX workflows.

Common mistakes

Importing unlicensed assets; saving into addon folder; skipping preview.

Validation

Validate path, rights, file type, and assignment target.

First safe task

  1. Open the tool from Dreamcatcher.
  2. Start with one tiny project-owned output.
  3. Save or apply only one change.
  4. Run Content Validator or Quick Play before expanding.

Success looks like

The output exists in the expected project location, related references are visible in the Inspector/tool UI, and no validator error points to a missing path or deleted resource.

Common mistake

Stacking several generated outputs or gameplay connections before checking one simple result first.

v0.9.4 boundary: use this tool through visible Dreamcatcher UI, generated assets, resources, templates, and validation workflows. Avoid editing plugin scripts directly unless official advanced documentation specifically tells you to.