Verified:GitHub

wave8-baker-dependency-registration

6|Updated Apr 2, 2026

Search Tags:#dependency-tracking #scriptableobject #baking #subscene #incremental-build #dependsOn #unity-dots

Ready to run

npx skills add https://github.com/dyCuong03/unity-agent-team --skill wave8-baker-dependency-registration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wave8-baker-dependency-registration
Source: https://github.com/dyCuong03/unity-agent-team/tree/main/.claude/skills/unity-dots/wave8-baker-dependency-registration
Command: npx skills add https://github.com/dyCuong03/unity-agent-team --skill wave8-baker-dependency-registration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stale Unity DOTS baked data by ensuring a Baker explicitly registers external asset and component dependencies so Unity invalidates and re-bakes when those dependencies change.

Core Features & Use Cases

Dependency tracking for external inputs: Use DependsOn(...) for referenced assets and components that are read via raw Unity API rather than direct serialized fields.
Correct incremental baking behavior: Ensures SubScene baking re-triggers when ScriptableObjects, textures, or child components change—even when the primary authoring MonoBehaviour hasn’t changed.
Anti-pattern prevention: Avoids silent correctness bugs caused by missing DependsOn or relying on non-tracked reads (child traversal, raw GetComponent calls).

Use case: your Baker reads a ScriptableObject config plus a child MeshRenderer to author entities; without DependsOn, changing the asset or child component can leave the previously baked entity data stale until a manual reimport.

Quick Start

In your Baker, call DependsOn(...) for every ScriptableObject/texture or child component you read through raw Unity APIs so incremental baking invalidates correctly.

Frequently Asked Questions about wave8-baker-dependency-registration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does Unity DOTS incremental baking not re-trigger when a ScriptableObject changes?▼

Unity DOTS incremental baking misses changes when Bakers read external assets via raw Unity APIs without calling DependsOn. You must explicitly register ScriptableObjects and non-serialized components as dependencies to invalidate and re-bake correctly.

How do I fix stale baked entity data in SubScenes after modifying child components?▼

Fix stale baked SubScene data by calling DependsOn inside your Baker for child components obtained through raw GetComponent calls or child traversal. This registers the external component reads so Unity re-triggers the bake automatically.

When do I need to use DependsOn in a Unity DOTS Baker?▼

Use DependsOn in a Unity DOTS Baker when consuming referenced ScriptableObjects, textures, or components obtained through raw Unity API calls rather than direct serialized fields. Direct serialized field reads are tracked automatically and do not require explicit registration.

What are common anti-patterns causing silent correctness bugs during incremental baking?▼

Common incremental baking anti-patterns include relying on non-tracked reads like child traversal or raw GetComponent calls without DependsOn. Omitting explicit dependency registration for external assets leaves previously baked entity data stale until a manual reimport.

Does direct serialized field access in a Baker require explicit dependency tracking?▼

Direct serialized field access in a Baker does not require explicit dependency tracking because Unity handles automatic tracking for Baker API accesses. You only need DependsOn for external assets and non-serialized component reads.