Getting started
From an idea to a game you can play.
Start with one small idea. This guide takes you through your account, AI connection and first playable browser game, then shows you how to keep a copy and share it.
- EoC access: try Regular for seven days with a credit card. No charge or automatic renewal. Regular is $29.95/month if you choose to subscribe afterwards.
- AI connection: bring a supported API key and provider balance. AI API usage is billed separately, including during the trial.
- Your browser: no installer is required for API builds. The optional Claude Code or Codex connection has its own setup and availability.
Connect your AI
Choose Connect AI, then API key. Select your provider and model, enter the key in the connection form, and choose Use for this tab. This temporary connection does not need a vault password. Your key is forgotten when you disconnect, refresh or close the tab.
Your provider bills your API usage. A ChatGPT or Claude subscription is separate from API access. Set a spending limit with the provider. Open the dollar-limit control beside your prompt and set Limit (USD) for your build budget. AI turns sets the maximum builder steps; increasing it does not raise your spending limit. EoC does not automatically switch to another provider or paid credits.
To keep a connection on this computer, open Saved connections and advanced setup and create or unlock your vault. Saved keys are encrypted for your account in this browser; EoC does not save these keys on its servers. Keep your vault password and an encrypted backup. Saved connections do not synchronize across devices. OpenRouter sign-in is also available in saved connection setup.
Already use Claude Code or Codex?
Choose Claude Code or Codex in Connect AI to see the supported connection options for your account. Companion builds require a paired Windows PC or Mac that stays online. Sign in through the official provider client on that computer; never paste a provider password into EoC. Availability and setup instructions appear in the connection panel and on the Companion downloads page. A provider subscription does not automatically fund API-key builds.
Describe a small, playable game
Tell the agent what the player does, how they win, and the style you want. For example: “Make a neon space game. Dodge enemies, collect shields, and fight a boss every ten points. Include touch controls.” Then choose Create game.
The agent reads project files, edits the code, and tests the preview. Its activity appears in the chat. When the game is ready, continue with a focused request such as “Make the enemies slower” or “Add a second weapon,” then choose Make change. Each build uses your selected provider.
Game-development guidance is selected per project. Connecting a service never enables its MCP globally. Advanced project MCP access requires an explicit project selection and a task that needs it.
Play your game, then refine it
Successful guided builds are checked and saved on this device automatically. Open Playto try the result, or use Undo to return to the previous working version. The Checks panel has the test results. Automated checks cannot prove every game rule, so play a round yourself before sharing.
Files imported from a terminal or recovered from an interrupted build need a separate review and check. When a draft is shown, choose Keep this version to save it or Go backto keep your existing game. A failed attempt does not replace the last saved game. Read the error before continuing; another AI request may use more of your provider balance.
Adjust game feel without an AI call
When a game exposes tuning settings, open Settings to adjust them while playing. Choose Save tuning to keep the values in your source. Ask the agent to expose tuning settings when building a different game.
Open History to review and restore an earlier version. EoC keeps up to twenty checkpoints per project on this computer.
Keep your source
Projects save in this browser. Choose Download game to download the version you are playing. For supported browser games, unzip it and open play.html; editable files are in source/. Downloading does not publish your game. Keep a backup before clearing browser data or changing computers. Signing in does not automatically upload private drafts or synchronize your local vault. Use Backups and recovery to save an optional private cloud copy, download a JSON backup, or import one. Cloud backups retain five previous versions and detect conflicting saves from other devices. Open Project recovery to download backups even after your plan expires.
For development outside Studio, keep secrets in a private .env.local, exclude it with .gitignore, and commit only an empty .env.example. The Connections screen provides a private .env kit for the selected service. Never place a key in game code, a prompt or a public repository.
Explore templates and the separate Unreal tools
Remix Autobattle Shooter to edit its gameplay code. The original stays unchanged. Other template previews show their available source and integration paths.
Studio source editions and the Studio Team Unreal plugin have separate repository permissions and license terms in Source access. The Unreal plugin must be compiled and installed in your own Unreal Editor. A browser prototype is not automatically converted into an Unreal project.
Need help? Contact nick@enginesofcreation.xyz with the page and error message. Never send API keys, vault passwords or .env files.