Create the link
- Open the current Build project.
- Play the latest version yourself once.
- Choose Share.
- Choose Get Playtest Link.
- Send the link only to the intended testers.
A playtest link lets you gather feedback before the publishing safety check and initial 16+ audience rules apply to a public release.
Give testers a focused brief
Ask about behavior they can observe:
- Was the goal clear in the first 30 seconds?
- Did the main interaction work every time?
- Where did progress become confusing?
- Could they tell when the round ended?
- Did any control or interface element block play?
Focused questions produce revisions that are easier to turn into a single Build prompt.
Convert feedback into changes
Group duplicate observations, reproduce the issue yourself and request one change at a time. For example:
Testers could not see when the round ended. Add a centered results panel showing score and a restart button. Keep the current arena and controls unchanged.
Use the prompt framework for the revision and playtest again before publishing.
AI allowance during testing
Playing and playtesting do not use AI allowance. Chat messages and AI changes do, so separate observation from revision: test freely, decide what matters, then spend usage on the clearest change.
Common problems
- The link is shared too widely: treat it as a private test link and control recipients.
- Testers see unclear instructions: rewrite the goal inside the game rather than explaining it only in a message.
- Every comment becomes a prompt: prioritize repeated or blocking issues first.
- The project changes after sharing: generate a fresh test pass for the version you intend to publish.