Playtest controls moved to Studio actions, with fewer Stop retries
Back to boardPlaytest start, stop, pause, resume, status, and automated test runs are now documented under Studio actions. AI agents and direct MCP integrations should use manage_studio.play_start, manage_studio.play_stop, manage_studio.play_pause, manage_studio.play_resume, manage_studio.play_status, and manage_studio.run_test. system_info stays focused on read-only status and diagnostics.
Play Stop has also been fixed for cases where Roblox Studio creates more than one plugin connection after Play starts. WEPPY no longer relies on only one connection for Stop, and cleanup checks whether Studio returned to Edit mode when confirmation is needed. This reduces cases where the AI asks Studio to stop but the test keeps running until you retry.
No manual migration is required. If you maintain custom prompts or direct MCP calls, update them to the manage_studio.play_* and manage_studio.run_test actions.
This is a historical announcement. Check the latest guidance for current availability and usage.