Bound the change
Give the agent one feature and explicit acceptance rules. Keep the source diff small enough to review.
UNITY + AI / A SMALL, TESTABLE WORKFLOW
Ship the change.
Catch the goblins.
Your agent wrote the code. Now check the build.
A playable Unity sample, a bounded feature exercise,
and evidence you can actually inspect.
WINDOWS x64UNITY 6000.3.17f1SOURCE INCLUDEDPREVIEW 0.1
01 / MEET YOUR TEST SUBJECTOriginal sample. Actual Windows build.
GOBLIN RANGE
One room.
Enough room for bugs.
Six rounds. Three targets. Reload. Pause. A tiny game loop with concrete rules—and just enough interaction for an AI change to go wrong.
This is a worked example for developers using a coding agent. Not an autonomous game studio or a promise to fix any Unity project.
02 / DON'T TRUST A GREEN MESSAGEA passing run.
A passing run.
And failures
on purpose.
We ran the Windows player and recorded 12 assertions. Then we deliberately broke pause and firing to check whether the verifier noticed.
Local engineering evidence. Synthetic input.
No independent buyer validation yet.
BUILDGOBLIN / EVIDENCE READER● ● ●
Every run must match its build ID, fresh run ID and complete assertion set.
Build what changed
Create the native player. Record its identity and payload hashes before accepting its results.
Try to break the proof
Reject stale and incomplete evidence. Run the deliberately broken controls, not just the happy path.
Recover deliberately
Retain a baseline. Restore the sample's changed source and demonstrate the restored behavior in a fresh run.
04 / GET YOUR HANDS DIRTYTry the lab.
Try the lab.
Bring a little
skepticism.
Start with the source preview and read the code. Run it in the supported Unity Editor, then decide whether the workflow is useful for you.
Download source preview ↓Read the field guide first ↗
Feature-to-Build LabPREVIEW 0.1 / FREE
- Original Goblin Range Unity project
- Native build and evidence-check scripts
- 12 reference assertions + 2 seeded faults
- 9 report-integrity rejection checks
- Bounded AI feature task + recovery guide
Before downloading
Windows x64 and Unity 6000.3.17f1 are required to build the source. Your Unity license and optional AI usage are your own. No account, email signup or payment required.
The commercial edition is not available yet. This preview makes no promise of compatibility with other versions, general game correctness, or time saved.
Is this another prompt pack?
The preview includes source, a playable sample you build yourself, a native-run checker and a guide. The prompts are there to structure a practical exercise, not to promise that an agent always succeeds.
Can I use the sample code commercially?
The original sample code can be used and modified in personal or commercial games under the included license. Unity components retain their own terms. Do not resell the guide/workflow bundle as your own product.
Does this test a real keyboard or controller?
The automated scenario uses synthetic commands through the sample gameplay path. That lets it check repeatable state transitions and target hits. It does not certify physical devices, frame-perfect input, art quality or other games.
What does the file manifest protect against?
It catches differences from the recorded payload before running it. It is not a publisher signature: replacing both the payload and manifest can replace the claimed baseline. Keep a trusted archive separately.
Where can I report a problem?
Email buildgoblin@agentmail.to with the failed step and a redacted report. Outbound email delivery is currently being investigated, so a reply is not guaranteed during this preview. Please do not send passwords or your private game project.