auto-authoring

What problem does it solve?

AutoAuthoring eliminates repetitive Unity DOTS Baker boilerplate by automatically wiring an authoring Inspector class’s fields to a runtime IComponentData struct when the mapping is direct.

Core Features & Use Cases

• Zero-boilerplate Baking: Generates the Baker via reflection for a field-for-field Inspector → IComponentData mapping, so simple components don’t need custom Bake methods.
• Inspector-driven Entity field resolution: Resolves Entity references from Inspector GameObject references using PropertyContainer, accelerating authoring-to-entity workflows.
• Graduation path to explicit logic: Helps you switch to an explicit Baker<T> when conversions, Blob assets, nested assets, or DependsOn registration become necessary, keeping your pipeline correct as requirements grow.

Use it when prototyping data-oriented components where authoring fields map directly to runtime fields with no special conversion logic, and when the IComponentData struct is marked [Serializable].

Quick Start

Use the auto-authoring skill to create an IComponentData struct and an AutoAuthoring<YourComponent> authoring class so the Baker is generated automatically from matching Inspector fields.