Attract Mode / Developers
Find out where players get stuck. Plan a focused playtest.
Request a managed browser-game playtest with clear goals, devices, multiplayer concurrency, timing and proposed rewards. Learn what happens after review.
Can Attract Mode arrange a playtest for my game?
You can request a managed playtest through the developer workspace. Tell the team what you need to learn and what a tester needs to join. The team reviews the build, scope and availability before agreeing a session. Submitting a request does not recruit testers or commit a reward.
The public /playtests area serves testers applying to available managed campaigns. It is separate from developer intake. A game listing, a sign-in integration and a playtest each have their own review; none automatically creates the others.
Prepare a request the team can act on
Choose Request a playtest in the developer workspace. Include the game and studio names, playable URL, two or three concrete questions, supported devices and account or access requirements. State the number of simultaneous players, expected session length, preferred dates and timezone, and any proposed reward.
For a multiplayer typing race, for example, explain how a host creates a public room, how invited testers join by code or link, whether you need two players or a full eight-player room, and what you want observed: room joining, race starts, input latency or results. Those details help the team assess a coordinated session. They do not establish that your game has been tested.
Use notes for build-version information, known issues, room-reset instructions and the existing listing URL. Share public or safely accessible test builds. Do not include account passwords, private player records or payment details.
Agree the session before inviting testers
After review, the team may request changes, decline the request or approve further planning. Agree the scope, time, timezone, participants, host responsibility, feedback format and any reward terms before a campaign is arranged. A proposed budget is not a payment authorization.
Approved does not mean a session is scheduled or that the requested player count is available. The review note and eventual fulfillment record state what was actually arranged. There is no guaranteed recruitment, concurrency, turnaround, positive review or commercial result.
Track a draft, review and outcome
Draft: saved privately, not sent for review. Submitted: waiting for the team to review. Changes requested: read the review note, edit the same request and submit it again. Approved: the request passed review, but delivery still needs to happen. Declined: read the explanation before deciding what to do next. Fulfilled: the team has recorded the actual outcome. Check the outcome link and review note.
Approval alone does not put a listing online, create OAuth credentials or schedule testers. The recorded outcome explains what was delivered. Keep each request focused on one game and one goal. You can send separate listing, sign-in and playtest requests for the same game.
Cannot use the workspace?
Cannot use the interactive workspace? Download the text or JSON request template, fill in the relevant section and email it to hello@attractmode.io. Keep fields you cannot verify marked unknown and explain them in notes. Do not invent screenshots, player counts or ownership evidence. Email is a review route, not automatic publication; the team will reply about missing information and next steps.
The templates work without an account. A coding agent can prepare a file or email draft for you, but there is no anonymous submission API and the documentation MCP cannot send it. Ask the agent to show you the completed request before you send it. Never put passwords, OAuth secrets, player data or payment details in the request or a public GitHub issue.
After the test
Use the agreed feedback and session observations to decide what to fix. A managed feedback session is not a promise of a public rating, favorable coverage or a Featured Game of the Day post. Keep tester contact and payout details private.
If the scope or build changes before the session, contact the team through the agreed coordination route. Do not treat an old approval as approval of a new reward, schedule or testing requirement.