Fighting Game · Guides & deep dives

V2 Cook Server

A guides & deep dives document in the Fighting Game library.

0sections1 minread

On this page

V2/ue/Build/Cooking/v2-cook-server.json defines the headless daemon used for editor cook-on-change. The server watches source assets, cooks on change, and serves hot assets back to editor clients through /hot-assets/{assetId}.

serve-v2-cook-server.py has a dry-run planning mode for CI and a minimal HTTP mode for local editor integration. The editor endpoints are /healthz, /cook/changed, /hot-assets/{assetId}, /invalidate, and /metrics.

The cook-on-change pipeline detects source changes, runs incremental planning, builds dependency closure, schedules parallel cooking, validates cooked assets, publishes hot assets, and updates the cook report.

Required gates:

  • cook-server-plan-generated
  • cook-server-watch-root-coverage
  • cook-server-editor-endpoints
  • cook-server-hot-asset-serving
  • cook-server-pipeline-coverage

The CI validator is:

bash
python3 V2/ue/Tools/check-v2-cook-server.py