Playtest Capture
Playtest Capture is the evidence side of Studio’s taste loop: anchor what you noticed in native play, compare the proposed tune as A and B, make the creative call, and see what actually landed through machine read-back. The live A/B, proof-pack, and reversal path is being proven for early access.
Playtest tune review
goal: Capture the last jump under night lighting and decide whether the landing pad is readable.
- camera
- in-game camera
- captured
- 09:14
- source
- Playtest camera
The tree line eats the path. The landing blocks sit in the shadow under the canopy.
what you felt
- The landing blocks sit in the shadow under the canopy.
- The far bank disappears into the trees.
- camera
- in-game camera
- captured
- 09:16
- view
- in-game camera
Sun on the grove is readable. The far bank still disappears into the trees.
proposal and evidence
checked against the stills- The landing blocks sit in the shadow under the canopy.
- The far bank disappears into the trees.
- Sun on the grove is readable; the cave mouth still sits in hard shadow.
Raise bounce strength and rim-light the flag. Recapture Play from the same camera.
Evidence bundle / proof-pack references
2 pinned / click to expand
09:18:02 Cook started on this machine
09:18:41 Play: Maze
09:19:08 Wrote Binaries/Win64/Bloxiti.exe
09:19:44 Waiting on playtest review
Capture the evidence behind the feeling.
A playtest bundle keeps the run, captured evidence, and review target together. You stay in the game; review happens afterward against the thing you actually played.
Mark what you noticed
Preserve the moment without turning play into ticket writing.
Keep context attached
The run, project state, evidence references, and proposed tune remain together.
Check evidence integrity
Verification checks the captured bytes and their producing receipts; it does not judge whether the game feels good.
Compare A and B in the game—not in a disconnected report.
Switch between the current and proposed values during a configured replay window. You decide whether B feels better or A should remain.
Current value — A
The live value you are judging from before the proposed tune.
Proposed value — B
The candidate change returned for comparison in the same play context.
Live A/B preview
Switch A and B inside a configured replay window so the comparison stays in the game.
Accept B or keep A
Your creative verdict chooses which value should remain after the preview.
One explicit creative decision
The call is recorded as a decision. It is not treated as technical verification of the write.
The result returns with evidence—and a path back when supported.
Machine read-back
Re-read the authoritative value after the write.
Verified outcome
Show requested versus observed before/after state.
Proof pack
Reference the playtest evidence, read-back verdict, checks, and exact change.
Declared reversal
When supported, Reverse starts a new verified attempt through the same route; it is not hidden or universal undo.
You judge the game. Machine read-back judges the write.
Accept B or keep A is your creative verdict. That click never marks the change technically verified. Verification comes from reading back what actually landed. Studio keeps the views and state aligned so you can inspect what changed.
The boundary
Human creative call
Taste stays with you. Accept B or keep A records what felt right.
Technical read-back verdict
Machine read-back shows what landed. It does not substitute for your creative judgment.
Explicit reversal when supported
When reversal is available, it is declared and routed—not implied as instant or universal undo.
Get on the list before Studio opens.
Studio isn’t public yet. Our team uses it today and opens access gradually.