Host a useful playtest

Use a playtest when you need players to try a specific part of a game and tell you what happened. Open Create a playtest to prepare the listing.

Choose the format before publishing

Choose Open feedback for a test anyone can try without reserving a spot. Include the game link, supported devices, what to focus on, and where players should leave feedback.

Choose Signup when you need a selected group or a scheduled session. Add the session details and number of tester spots. Explain any access requirements before people apply.

The mode cannot be freely changed once applications exist. Decide whether you need a roster before collecting signups.

Write a focused request

Give players an achievable task, such as finishing the tutorial on a phone or trying the new trading screen with another player. Explain what feedback would help and how long you expect the test to take.

If you offer a reward, state what qualifies and how you will deliver it. Granting a playtest spot does not create a paid deal or automatically send a reward.

Manage a signup roster

Open Hosting to review your tests. Grant spots to the people you need, individually or in a batch. Bloxstack checks the capacity you set and will refuse a selection that goes over it.

You can release a participant's spot when needed. The participant can sign up again if the test is still accepting applications.

Use the roster's update action for the available session notices. These are structured Bloxstack notifications, with a 15-minute cooldown between roster pings. They are not a free-form message sent privately to every player.

Close the feedback loop

Review the feedback against the original goal and turn useful findings into work for the team. A Studio task can keep the issue, owner, and next revision together.

When the test is finished, close it so the page no longer invites new participation. Existing open-feedback discussion can remain available for reference.