ROOST2DSTUDIOINVITE BETABuilder guide
Create a project, describe the result you want, choose a Build Mode and keep playing while Studio prepares a verified Candidate.
Help
Create a project, describe what you want and let Studio build a Candidate.
Choose Auto, Economy or Deep Build, then keep playing while Studio works. Only a verified Candidate replaces the current version.
Back to topicsDescribe the game or change in ordinary language and include what success should look like.
Mention controls, visual style, platform and rules that matter. Start with the desired result; Studio can ask for missing details.
Back to topicsHelp
Build mode controls how much autonomous work Studio may consider, not which provider or model is used.
Auto is recommended and chooses the least expensive path likely to verify. Economy avoids a full external coding agent. Deep Build permits deeper autonomous work for complex requests, always within account and server limits.
Back to topicsYour verified game remains mounted and playable while a new change builds.
Build status and Stop remain available. A successful request closes the change sheet; an error or question keeps it open without reloading the current game.
Back to topicsConversation and playable preview remain separate so the current game stays usable.
On wide screens chat is beside the game; on narrow screens it opens as a roomy overlay above the game. Hide or reopen it without reloading the verified preview.
Back to topicsA requested change does not immediately replace the game you can play.
Studio checks a Candidate first. Only one that passes the configured typecheck, tests, build and browser verification becomes current; failure keeps the last known-good game.
Back to topicsA failed Candidate never replaces the last known-good version.
Review the safe error and make a narrower request or try again later. If external AI, sandbox or asset work already started, the attempt may still consume part of the Beta allowance.
Back to topicsReturn to an earlier verified immutable version without promoting a failed Candidate.
Open the project's version history, select a verified version and restore it. Your source export follows the restored current version.
Back to topicsVoice adds recognised words to the same prompt used by typing.
Studio receives the recognised text and does not upload or store microphone audio. Your browser or operating system provides recognition and may use its own online speech service.
Back to topicsHelp
Studio combines authored playable foundations and deterministic tools with approved AI systems and independent verification.
Automatic routing considers task, expected success, cost and privacy. AI-generated source changes are promoted only after configured verification succeeds.
Back to topicsStudio accepts ordinary descriptions for familiar, hybrid and unfamiliar 2D or 2.5D games.
A genre is verified only when an authored foundation has scripted controls and a test that reaches its objective. Other requests use the isolated custom-code route and remain experimental until that mechanic family earns the same evidence; a genre label never substitutes a generic game loop.
Back to topicsBuild Mode and AI Provider are separate concepts.
Managed AI uses Studio-approved providers and counts against Build Balance. BYOK uses your encrypted provider key and your provider account pays the model cost; Studio still orchestrates and verifies the build.
Back to topicsBuild Units represent the Studio creation capacity available to your account, not an invoice amount.
Different requests can use different amounts. Studio shows available balance before work; a failed request can consume allowance when external AI or compute already ran.
Back to topicsHelp
Studio projects, previews, source and assets are private by default.
Playable previews run on an isolated origin. Remix permission does not publish source, and public publishing remains separately gated.
Back to topicsYour project source is portable, while engine code, packages and assets can have separate licences.
Studio preserves known asset provenance. You remain responsible for checking rights before publication; Chikn Community content is labelled non-commercial and includes its notices.
Back to topicsAfter a first game or visual edit, Roost may offer up to two concrete ways to improve its presentation.
Effect suggestions use authored rendering and add no image-generation cost, though the change uses the normal build allowance. Image suggestions appear only when useful and available, show an estimate, use one low-cost routed draft, and run only after you select them. Suggestions expire when the playable version changes.
Back to topicsDownload the complete portable project source from the project.
The export includes applicable engine, dependency and asset notices. Account-data export is separate and does not replace the game-source download.
Back to topicsProject and account deletion are separate controls in Studio.
Archive keeps a project safely out of your active library. Trash is restorable for 30 days, with permanent deletion available immediately; technical queues, detached audit records and backup retention are explained in the Privacy Notice.
Back to topicsHelp
Studio accounts are created from personal invitations, not public sign-up.
A magic link is the first-access and recovery path. Invitations and accounts are not transferable, and access remains subject to Beta limits.
Back to topicsA passkey signs you in with your device or password manager instead of an email link.
It can use biometrics, a device PIN or security key. Passkeys are optional; magic-link recovery remains available after the last passkey is deleted.
Back to topicsStudio records the exact active legal-document versions accepted before the first build.
You must be at least 18. A changed active document can require renewed acceptance; accepting never makes a project public.
Back to topicsDownload personal, account, acceptance, project and build metadata in a machine-readable form.
Project source is downloaded separately. Private passkey material and stored provider-key values are never returned in an export.
Back to topicsHelp
Use product support for Studio bugs, build behaviour and account-access questions.
Email support@roost2d.com with the project or build identifier and a short description. Do not send passwords, passkey material or provider keys.
Back to topicsThe report form is for privacy, licensing, illegal-content or other legal and safety concerns.
It is separate from ordinary product support. Public publishing is disabled during the closed Beta.
Back to topicsUse Account for export or deletion, or contact the privacy address for a data-protection request.
Email privacy@roost2d.com. Depending on legal requirements, access, correction, erasure, restriction, portability or objection may apply.
Back to topicsFor product help or a bug, email support@roost2d.com. For privacy requests, email privacy@roost2d.com. Use the legal and safety report for licensing, illegal-content or other legal concerns.