Bundled Profiles

Each build ships with a usable subset of SimulationCraft's profiles/ tree. Submitted profile text can reference these bundled files.

#Manifest

GET /v1/simc/builds and GET /v1/simc/builds/{id} return a profiles.manifest array listing the profile filenames this build accepts (e.g. MID1_Mage_Arcane.simc). To use one, reference it in your submitted profile text either on its own line or as input=<filename>. SimC resolves the file against the bundled tree at simulation time.

#Manifest freshness

The bundled set can change between builds. Channels (latest, nightly, weekly) point at whichever build is current when a job is picked up, which may be newer than the build whose manifest you fetched. If a profile is critical, fetch the manifest shortly before submit rather than caching it across long-lived sessions.

#Build-time validation

Every profile in the manifest is verified at build time: it's simc run must exit cleanly. Profiles that fail to parse or sim are dropped from the manifest before the build is published.

Patch-driven breakage between build time and submit time can still happen. If a profile errors at runtime, try another profile for the same spec or report it upstream.

#Validation

Filenames not in the manifest are rejected at submit time with input_sanitized_rejected. To avoid the round-trip, fetch the manifest for the target build and check membership before submitting.