domains / families / software-engineering / scenario-unity-pipeline-automation

scenario-unity-pipeline-automation

separate

Use when automating a Unity 6.3 content pipeline or build: importing an art drop (FBX, PNG) with AssetPostprocessor rules and naming conventions, generating prefabs or editing scenes from script with correct Undo and SetDirty, Addressables groups, labels and content builds, content-validation tests, batch-mode, command-line or CI builds (Build Profiles, GameCI, GitHub Actions, Accelerator), editor tools; or when textures import wrong or reimport every run, a scripted edit vanishes, bundles duplicate assets, a batch build ignores its defines, or CI cannot activate Unity.

When to use

• importing art drops with AssetPostprocessor rules
• generating prefabs or editing scenes from script
• configuring Addressables groups and content builds
• running content-validation tests
• executing batch-mode or CI builds
• fixing texture import issues
• resolving scripted edit persistence problems
• preventing bundle asset duplication

When not to use

• manual asset editing
• non-Unity engine pipelines
• runtime gameplay logic development
• network infrastructure setup

Skill page

Source