Game-aware agents, honest engine status

Detects Unity, Unreal, Godot and browser game projects from their project files, including engine version, scene or level lists, asset counts and test frameworks.

Verified on fixture projects and a simulated GitHub; not yet run on production-scale game repositories.

Per-engine suggested build and test commands, capture settings and worker requirements, with an admin override layer.

Profiles are generated for all four targets. Engine commands for Unity, Unreal and Godot have not been run on a real engine.

Gameplay Engineer reports tunables it added. Game Designer is read-only and returns mechanics, rules and verification notes. Technical Artist reports asset budgets and needs approval to replace binary assets.

Approval gates on these roles are declared in the role and enforced where the platform has a mechanism, such as tool policy.

Agents can edit gameplay source files in any connected repository and open a pull request. For Unity, Unreal and Godot this does not include compiling, running tests or opening the editor.

Verified end to end against a simulated GitHub; verification against live GitHub is pending.

The reviewer receives the inventory change, files outside the declared scope and edits to serialized assets as part of its rubric.

Implemented for all targets. For Unity, Unreal and Godot the inventory comes from static discovery, not a live editor.

Your build and test scripts run as the project's validation command in the sandbox.

After validation, PWR serves the game, waits for the canvas, and stores desktop and mobile screenshots and a short video as run artifacts.

Screenshots are compared pixel by pixel with a baseline an admin approved. The result reports the changed percentage against your threshold and attaches a diff image.

Records paint and load timings, a frame-rate sample and console errors for each capture.

Driving input scenarios and verifying save data are not built.

A local HTTP bridge exposes editor tools with declared risk levels. Bridges register as integrations, so tools are approved, granted and audited like any other.

Verified against a simulated engine bridge only; this proves the PWR side of the protocol, not the engine side.

An editor package for scene inspection, serialized property edits with undo, prefab instantiation, test runs, player builds and screenshots.

Written but never run inside a real editor; validation on a provisioned engine worker is pending.

An editor plugin for level and actor inspection, transactional property edits, actor spawning, automation tests, builds and high-resolution screenshots.

Written but never run inside a real editor; validation on a provisioned engine worker is pending.

A headless driver for exports, test runs and scene capture, and an editor addon for typed property edits.

Written but never run inside a real editor; validation on a provisioned engine worker is pending.

Running builds, engine test suites, captures and frame-time sampling for Unity, Unreal and Godot requires provisioned and licensed engine workers.

Blocked until an engine worker is provisioned and the acceptance checklist has been run on a real project.

A goal for a new or empty repository: the Producer plans, you approve, and the Gameplay Engineer works the tasks within a budget.

Controller logic is covered by automated tests with a stub agent and a simulated GitHub; live end-to-end verification is pending.

The Game Designer role reads a design document from the repository and returns a structured spec and review findings.

Launch path is covered by automated tests; it reads a connected repository, which has only been verified against a simulated GitHub.

Build a Feature with the gameplay option assigns the Gameplay Engineer role and creates a task with acceptance criteria.

Task creation is available. Execution through to a pull request follows the beta GitHub workflow.