setup-engine

To pin a game engine version, configure and lock the chosen engine and version in the project's OPENCODE.md manifest. This ensures consistent tooling across the project setup by recording the exact engine version specification.

To get reference docs for a newer game engine version, the setup process automatically detects knowledge gaps and uses WebSearch to fetch or generate missing engine reference documentation. This populates the docs when the version exceeds training data.

Yes, you can choose a game engine without a version by running the setup with no arguments. This triggers a guided engine selection process based on your game concept and user preferences to determine the appropriate version.

The best way to ensure consistent engine choices is to pin the selected engine version in the OPENCODE.md file. This locks the tooling configuration and updates supporting technical documentation for agent readiness.

Detecting knowledge gaps during project setup identifies when the engine version exceeds the model's training data. This triggers an automatic WebSearch to populate missing reference docs, ensuring the project has up-to-date engine references.