Build Rigged Game Assets

Build one truthful actor package from source reference through gameplay and catalog proof.

Establish the contract first

Inspect repository truth before generating or editing files:

Locate the source image/model, runtime loader, skeleton conventions, action API, equipment system, collision system, catalog schema, review routes, budgets, and tests.
Classify the actor as character or monster.
Classify delivery as catalog-only, review-only, or runtime. Do not call an asset implemented until gameplay loads it.
Preserve immutable source artifacts separately from optimized runtime files.
Decide target formats before using a credit-bearing generator.

Copy the matching template from assets/, fill it in, and keep it beside the implementation or in the project’s asset metadata location: