Asset Pipeline Controller Config

Monitor game asset processing with real-time status for textures, models, audio, and pipeline health.

When to Use This Setting

Apply this setting when you need to:

• Track asset processing status across textures, 3D models, and audio files in game development projects
• Monitor file sizes and compression ratios to identify assets that need optimization
• Display pipeline health indicators that alert you when the asset volume exceeds recommended thresholds Consider alternatives when:
• Your project is not a game development or multimedia project with structured asset directories
• You prefer a simpler statusline that shows only git and model information

Quick Start

Configuration

Copy
name: asset-pipeline-controller-config
type: setting
category: statusline

Example Application

Copy
claude setting:apply asset-pipeline-controller-config

Example Output

Setting applied. Changes:
- statusLine: Asset pipeline monitor (textures, models, audio, health)
- Displays: [Model] Textures | Models | Audio | Processing | Compression | Health

Core Concepts

Asset Pipeline Monitoring Overview

Aspect	Details
Texture Tracking	Counts PNG files and reports total size in megabytes with icon indicator
Model Tracking	Counts FBX files for 3D model assets with size aggregation
Audio Tracking	Counts WAV files for audio assets with size measurement
Pipeline Health	Rates overall health as Optimal (<1000 assets), Large (1000-2000), or Massive (>2000)

Pipeline Status Architecture

+---------------------------+
|  Asset Discovery          |
+---------------------------+
|  Scan: Assets/**/*.png    |
|  Scan: Assets/**/*.fbx    |
|  Scan: Assets/**/*.wav    |
+---------------------------+
         |
    +----+----+----+
    |    |    |    |
    v    v    v    v
  Tex  Mdl  Aud  Pipeline
  Count Count Count Health
  Size  Size  Size  Rating
         |
         v
+---------------------------+
| [Model] Tex | Mdl | Aud  |
| Processing | Compress |   |
| Health                    |
+---------------------------+

Configuration

Parameter	Type	Default	Description
statusLine.type	string	"command"	Status line type, uses shell command for dynamic content
statusLine.command	string	N/A	Python script that scans asset directories and reports status
Processing Threshold (Light)	number	100	Texture size in MB below which processing load is rated light
Processing Threshold (Medium)	number	500	Texture size in MB above which processing load is rated heavy
Health Threshold (Large)	number	1000	Total asset count above which pipeline health shows warning

Best Practices

1. Organize assets in an Assets directory - The monitor scans for Assets/**/*.png as the primary path. Following the Unity or Unreal convention of a top-level Assets directory ensures accurate detection.
2. Monitor texture sizes for optimization opportunities - Large texture files are the most common source of bloated game builds. Use the texture size indicator to identify when compression or resolution reduction is needed.
3. Track pipeline health over time - As your project grows, the health indicator will shift from Optimal to Large. Use this as a trigger to implement asset streaming or level-of-detail systems.
4. Customize file extensions for your engine - The default monitor tracks PNG, FBX, and WAV files. Modify the script to include additional formats like .tga, .obj, or .ogg that your game engine uses.
5. Combine with build pipeline integration - Use the asset counts and sizes to set thresholds in your CI build pipeline. Fail builds when asset sizes exceed budget limits to maintain shipping quality.

Common Issues

1. No assets detected - The monitor looks for files in Assets/ subdirectory first, then falls back to the project root. If your assets are in a different directory, update the glob patterns in the command script.
2. Python3 not available - The statusline command requires Python 3. If you see errors, install Python 3 or modify the command to use an alternative scripting language.
3. Status line shows None for all categories - This occurs when no matching files are found. Verify your asset file extensions match the patterns in the monitor script.