Table of contents
Validation Errors
Purpose
Validation errors explain why authored content is not ready for bake, preview, runtime loading, or server-authoritative gameplay. The command-line entrypoint for a full bake failure check is cargo run --bin aether-bake -- --fail-on-diagnostics.
Steps
Read the first blocking error and identify the authored source path, catalog id, or scene entity it names. Use the relevant editor validation surface for local feedback, or run cargo run --bin aether-bake -- --fail-on-diagnostics for the full bake check. Fix authored source rather than generated output, then rerun validation before chasing follow-on errors.
Expected Outputs
After fixes, validation should produce no blocking errors for the changed domain, and bake output should update without stale references. The bake CLI should complete without fail-on-diagnostics errors, and remaining warnings should be understood and owned before content ships.
Common Mistakes
Authors can fix generated files, ignore the first missing id, change runtime handling without updating authored data, or assume one clean page means dependent catalogs have also been validated.
Recovery Paths
Return to the authored source named by the report. If the report points at a generated artifact, trace it back to the catalog, scene, or editor input that feeds it, then rerun the relevant editor validation surface and cargo run --bin aether-bake -- --fail-on-diagnostics.