Game Asset Pipeline Runner

Execute automated game asset processing pipelines for texture compression, model optimization, and platform-specific packaging.

When to Use This Command

Run this command when you need to:

• Process raw game assets (textures, models, audio) into optimized platform-specific formats
• Run incremental asset builds that only reprocess modified files since the last build
• Validate asset quality, naming conventions, and memory budget compliance across all assets

Consider alternatives when:

• You need to create new art assets rather than process existing ones
• Your game engine's built-in asset import pipeline already handles all optimization

Quick Start

Configuration

Copy
name: game-asset-pipeline-runner
type: command
category: game-development

Example Invocation

Copy
claude command:run game-asset-pipeline-runner --platform mobile --action build

Example Output

Asset Pipeline: Mobile Build
Source Assets: 1,247 files (3.8 GB)
Modified Since Last Build: 34 files

Processing:
  Textures (18 modified):
    [+] Compressed to ASTC 4x4 format
    [+] Generated mipmaps (6 levels)
    [+] Sprite atlas: 4 sheets packed (92% efficiency)
  Models (8 modified):
    [+] Generated LODs: LOD0 (100%), LOD1 (50%), LOD2 (25%)
    [+] Optimized mesh topology (avg 12% reduction)
    [+] Validated bone hierarchies
  Audio (8 modified):
    [+] Compressed to Opus format (48kbps)
    [+] Categorized: 5 SFX, 2 music, 1 voice

Validation:
  [OK] Memory budget: 184MB / 256MB limit
  [OK] Naming conventions: 1,247/1,247 compliant
  [WARN] 2 textures exceed 2048x2048 resolution

Build complete in 2m 18s (34 assets processed, 1,213 cached).

Core Concepts

Asset Pipeline Overview

Aspect	Details
Texture Processing	Compression (ASTC, DXT, ETC2), mipmaps, atlasing, resolution limits
Model Processing	LOD generation, mesh optimization, bone cleanup, collision meshes
Audio Processing	Format conversion, bitrate optimization, streaming classification
Incremental Builds	Hash-based change detection to skip unchanged assets
Platform Targeting	Mobile, PC, console, and web each get optimized output formats

Pipeline Execution Workflow

  Raw Assets
       |
       v
  +-------------------+
  | Change Detection  |---> Hash comparison with cache
  +-------------------+
       |
       v
  +-------------------+
  | Format Validation |---> Naming, resolution, file type
  +-------------------+
       |
       v
  +-------------------+
  | Platform Process  |---> Compress, LOD, convert
  +-------------------+
       |
       v
  +-------------------+
  | Budget Validation |---> Memory, disk, draw calls
  +-------------------+
       |
       v
  +-------------------+
  | Package Output    |---> Asset bundles / packages
  +-------------------+

Configuration

Parameter	Type	Default	Description
platform	string	required	Target platform: mobile, pc, console, web
action	string	build	Pipeline action: build, validate, clean, report
incremental	boolean	true	Only process assets modified since last build
memory_budget_mb	integer	256	Maximum total memory budget for processed assets
quality	string	balanced	Quality preset: fast, balanced, maximum

Best Practices

1. Always Run Incremental Builds - Full asset rebuilds on large projects take 30+ minutes. Use hash-based change detection to process only modified assets, keeping iteration cycles fast during development.

2. Set Memory Budgets Per Platform - Mobile devices have far less available memory than PCs. Define platform-specific memory budgets and validate against them during every build to catch overages early.

3. Enforce Naming Conventions Automatically - Assets with inconsistent names are impossible to manage at scale. Validate naming patterns (type_name_variant_size) during the pipeline and reject non-compliant assets.

4. Generate LODs Automatically - Manual LOD creation is tedious and often skipped. Automatic LOD generation with configurable reduction ratios ensures every model has appropriate level-of-detail variants.

5. Version Control Large Assets with LFS - Raw game assets (PSD, FBX, WAV) should be tracked with Git LFS, not stored directly in the repository. This keeps the repository clone fast while still versioning asset files.

Common Issues

1. Texture Compression Artifacts - ASTC or DXT compression produces visible banding or block artifacts on gradients. Increase the compression quality or use a higher block size for assets where visual quality is critical.

2. LOD Popping Visible In-Game - The transition between LOD levels is noticeable. Adjust LOD distance thresholds and consider using cross-fade transitions between levels to smooth the visual switch.

3. Build Cache Invalidated Unexpectedly - A platform or quality setting change invalidates the entire cache, causing a full rebuild. Cache keys should include the platform and quality parameters so changes only invalidate affected assets.