Skip to content

ZodiacEngineHub / Panzerfaust Integration

Status: External-tool integration note. ZodiacEngineHub owns generated project configuration; its implementation is not in this repository. Source of truth for project schema/defaults: ZodiacEngineHub.

Current renderer-engine contract

Obelisk accepts:

--launchEditor
--projectConfigFile <path-to-project.json>

The application stores the supplied config path and passes it to the normal application initialization flow. This repository does not contain ZodiacEngineHub/Panzerfaust source, so it cannot document that tool's UI, registry, project scaffolding, build button, or implementation details as current facts.

Generated configuration boundary

project.json is generated by ZodiacEngineHub. Do not hand-edit it merely to change an engine default, and do not make RendererEngine documentation prescribe undocumented keys, directory layouts, project-manager caches, or a game-DLL/Lua workflow.

The current engine consumer recognizes the configuration handed to it. The environment lighting key rendering.environment_lighting_budget_mb is a project-level GPU policy whose current generated value may be retained. Schema names, validation, and default changes belong in ZodiacEngineHub.

Issue-tracker correction (2026-09-17): RendererEngine issue #821 correctly tracks the missing environment-lighting settings UI, but its proposed direct persistence of generated project.json conflicts with this boundary. The engine may show the configured and effective read-only policy and request/reload a new Hub-generated configuration; schema, default, and persistence changes belong in ZodiacEngineHub or in a revised cross-tool handoff.

Integration requirements

  • Pass paths as distinct process arguments with correct quoting; do not build an executable command line by string concatenation.
  • Report missing executable/configuration, invalid configuration, process launch failure, and non-zero exit status with actionable diagnostics.
  • Preserve user project data on cancellation and do not write generated configuration from RendererEngine as an implicit side effect.
  • Version the handoff contract between the tool and the engine and test it with sample generated projects, including paths containing spaces and non-ASCII characters.
  • Keep editor scene serialization separate: scenes are authored through the engine's versioned scene-document contract, not through project-manager metadata.

Out of scope here

Game DLL reload, Lua host, plugin marketplace, Steam, template directory structures, and tool-specific cache/registry formats have no current implementation contract in this repository. They require their own approved designs and, where relevant, implementation in ZodiacEngineHub or the owning product repository.