MODULES // SPATIAL.COMPILER 0.4.1

Spatial Compiler modules

A module is one kind of asset the compiler makes. Each one reads a spec file and runs through the same spatial-compiler commands, the same strict checks and the same JSON report.

  • MODULE // PYROAVAILABLE ยท 0.4.1

    Pyro

    Pyro bakes fire, smoke, explosion and dust flipbook sheets, lit from six directions, from a .pyro.toml spec.

    • emitters
    • forces
    • obstacles
    • values over time
    • godot 4 wire

What every module shares

  • spatial-compiler check validates a spec without the GPU, and each error names the key and the nearest valid key or the range.
  • spatial-compiler schema prints every field, range, default, warning and metric as JSON.
  • stdout carries the report JSON and nothing else, and the same report is written to bake_report.json.
  • The same spec, seed, version and machine give the same bytes.

Over MCP, the same commands are typed tools (bake, check, schema, sweep, wire). See MCP tools and Add it to Claude.

Questions

What is a Spatial Compiler module?

A module makes one kind of asset from a spec file, through the same spatial-compiler commands, checks and JSON report as every other module.

Which modules are available?

Pyro is available today. It bakes fire, smoke, explosion and dust flipbook sheets lit from six directions.

Can an agent call a module over MCP?

Yes. Over MCP, the pyro commands are typed tools: bake, check, schema, sweep and wire.