Yes. Open Spawn in your phone's browser to play or build with Savi. Games marked Desktop only need a computer.
For iOS app beta access, check the announcements in our Discord.
How do I make my game work on a phone?
Ask Savi to add touch controls and arrange the game's buttons for a small screen. Try it on a phone before sharing it. Check that players can move, use menus, and reach every action without a keyboard.
How do I change my username?
Inside a game, open Settings from the gear on the right. Select your name, enter the new name, and press Enter to save it.
How do I change my character?
Press your picture at the top of the page, then edit character. Inside a game, open Settings from the gear on the right, select your name, and choose edit character. Describe the character you want in the editor.
Building with Savi
Who is Savi?
Savi is your companion for making games. Talk through ideas, try them, and tell her what to change. You bring the direction and taste. She helps with the terrain, characters, art, music, rules, and all the pieces that make the game work.
You can give her reference images and point out what you like. You can also send a new message while she works to change direction.
Which AI does Savi use? Do I need to connect my own account?
Savi uses Claude Opus 5.5 by default. The models behind her can change as we improve Spawn. Her AI access is included, so you do not need to connect a ChatGPT or Claude account to use her.
Bringing your own coding agent is optional.
What are wisps?
Wisps are Savi's helpers. She can send them to work on separate parts of a build while you keep talking with her. They bring their work back to the same game.
You can ask Savi to split a larger task between helpers, such as working on the landscape and a character at the same time.
What is Lock In?
Lock In gives one build a deeper pass. Type /lock-in with the task you want to work on. Savi offers a plan. Read it, then press the Lock In button in her reply to start.
It can take longer than a normal request. Use it when you want more care on a specific build or a difficult change. Savi will tell you if a Lock In is not available.
Is Focus the same as Lock In?
No. /focus changes Savi's focused look. Type it again to turn it off. It does not change the AI model or give a request more thinking time.
Use /lock-in for a deeper build.
How do I get better results?
Start with a small, playable idea. Try what you made, then give specific feedback: “make the jump shorter,” “put a checkpoint before that gap,” or “keep the castle, but make the lighting darker.”
Reference images and examples help. Tell Savi what must stay the same as well as what you want to change. If you are stuck, ask her to suggest the next step.
Which chat commands are useful?
/help shows the available commands.
/debug asks Savi to investigate a bug and work on a fix.
/lock-in asks for a deeper build.
/focus toggles Savi's focused look.
/invite opens the invitation for a friend.
/agent gives you a one-time key for an outside coding agent.
/jam brings the current SpawnJam into the conversation.
What does the Context circle show?
It shows how much conversation Savi is working with. Long conversations can be condensed so she has room to keep building. This is separate from your game's saved files and history.
If an earlier detail matters to the next change, remind her of it.
Making your game
What kinds of games can I make?
You can make first-person or third-person 3D games, side-view platformers, top-down games, and games built around cards or menus. Games can be single player or multiplayer.
Describe how you want the game to play. Work with Savi on its camera, controls, and rules.
Is there a limit to the number or size of my games?
You can create as many games as you like. Spawn 6 does not set a fixed size limit on a game.
A large game still needs to run well on the devices people use. Test as you build, and tell Savi which parts feel slow.
How do I create models and animations?
Describe the character or object to Savi. Give her reference images when you have a specific look in mind. Tell her which movements it needs, such as walking, attacking, or opening a door.
Try the result in the game. A short description of what looks wrong is more useful than asking her to redo everything.
How do I import my own assets?
Drop files into Savi's chat and tell her how you want to use them. Common formats include:
Images: PNG, JPG, and WebP for art, textures, sprites, and reference pictures.
3D models: GLB for characters, props, and buildings.
Audio: MP3 and WAV for music, sound effects, and recorded voices.
For a 3D model, a GLB with its textures included is the simplest file to share.
Can I add characters that talk?
Yes. Ask Savi to add characters with dialogue and voices. Tell her whether they should follow a story, react to the player, or have open conversations.
Can I make custom tools for my game?
Yes. Ask Savi to make a tool for the job you need to do. Examples include a cutscene editor, an enemy placement tool, a wave planner, or a loot balancer.
You can package reusable tools and content as mods for other games.
What are mods? Do I need them?
Mods are reusable tools or content that you can add to a game. You can ask Savi to find, use, or create one.
You do not need mods to start building. Add one when it helps with something you want to make.
Will my older mods work in Spawn 6?
Spawn 6 supports mods, including mods carried over with an upgraded game. Try yours after the upgrade. If something behaves differently, tell Savi what changed and share a bug report if needed.
A mod that adds a useful tool can still help. A mod that worked around an old engine problem may no longer be needed.
How do I save a player's progress?
Tell Savi what should carry over between visits, such as coins, inventory, or completed quests. Also tell her what should reset when a new game starts.
Test by leaving and coming back. Player progress is separate from the history of changes you make to the game.
Can I make a copy of my game?
Yes. Go to Create, open the menu on your game's card, and choose Duplicate. Use the copy to try a different direction.
What are Places and Rooms?
A Place is an area of a game, such as a town, dungeon, or arena. It can have its own scenery and rules.
A Room is a separate session of the game. Use rooms when different groups need their own match or adventure. Tell Savi which people should play together and what they should share.
God Mode and history
What is God Mode?
God Mode lets you fly around and edit things directly. You can move objects, turn them, change their size, and use building tools.
After your first build, open the chat and select God, or hold Tab and press G. Select Player to return to playing.
What are the basic God Mode controls?
On a computer:
Hold the right mouse button and drag to look around.
Use WASD to move.
Double-tap Space to start flying. Hold Space to go up and Shift to go down.
Right-click an object to select it. Drag its handles to move or reshape it.
Press R to rotate the selected object.
The bottom toolbar holds shapes, paths, brushes, and saved blueprints. You can also ask Savi to help with a selected object.
How do I undo a change or return to an earlier version?
Select your game's name to open its changes. Choose Undo beside a change to ask Savi to undo it.
For an older version, open All changes, select the change you want to return to, and choose Go back to this. Savi applies the change. Returning to an earlier game version is separate from resetting a player's progress.
Building and testing together
How do I build with a friend?
In a game, press Invite in the bar. Anywhere else, press friends. Or type /invite in Savi's chat. Open let someone build here and choose copy build link. Send it to your friend. That link lets them build.
Someone already visiting can also ask to build. You decide whether to accept. The room panel shows who is there and who can edit.
Can friends test an unfinished game without being able to edit it?
Yes. Press friends and copy your link. That link lets someone visit. Use copy build link only when you want them to edit too.
You can keep building while they test. In a single-player game, each visitor gets their own play session.
Are unpublished games private?
Anyone with the game's link can visit it before you publish. Visiting does not grant permission to edit.
Share the build link only with people you want to build alongside you.
How can I test multiplayer by myself?
Open the same room link in a separate private or incognito browser window. Join there as a guest or with a different account to test a second player.
Use the room's copy link action so both players join the same room. Two tabs signed into the same account do not act as two separate players.
Your code and outside agents
Can I bring a game I already made?
Yes. Your own coding agent brings its code and art into a new game, and then you keep building with Savi or with that agent. Bring a game you already made has the steps.
Can I bring my own coding agent?
Yes. In your game, type /agent in Savi's chat. Copy the one-time key and paste it into your coding agent, such as Codex or Claude Code. It joins as a builder and works on the same game files as Savi.
The one-time key works for ten minutes. Generate a new one if it expires. Your outside agent uses your own account with its service.
How do I reconnect or remove an agent?
If your agent lost its key, open Tokens & agents. Choose Reconnect, then copy the new key into that agent's session.
To bring the same agent into another game, type /agent in that game's chat and paste the one-time key into the agent's existing session.
Choose Unlink to remove its access to the games you manage. This does not delete the agent's own account or games.
Can I read, edit, or keep a copy of my game's code?
Yes. A Spawn 6 game has a Git repository, which holds its files and change history. Open your game's /code page, such as spawn.co/@yourname/your-game/code, to find its repository address and connect an agent.
You must own the game or have permission to edit it. Your agent can help you read the files, change them, and keep a local copy. Assets are referenced by name, so a copy of the code is not a bundle of every image, model, and sound.
Who owns my game and its assets?
Your game is yours. You can keep its code and build on it. Shared or third-party assets remain subject to their licenses, and generated assets may not be unique to your game.
See the Terms of Service for the rights that apply to your content and to Spawn.
Can I take my game to Steam or another engine?
An outside coding agent can help port your game to another engine or platform. It will need to adapt the code and features that depend on Spawn.
Spawn does not provide a ready-to-run Steam export, and Savi builds games for Spawn. Keeping a copy of your files is different from having a standalone game.
Friends, chat, and portals
How do I add friends or join them?
Press friends in your den, or open chats and choose friends, the first row. Type a friend's @name and press add friend. When they say yes, press invite to bring them to you, or portal to go to them. Whoever opens your link becomes your friend. On a computer, you can also hold Tab and press C to open chats.
In a game, press Invite in the bar, or type /invite in Savi's chat, to bring a friend to where you are. Send them your link, and they land beside you. You can also form a party to travel together.
How do text and voice chat work?
Open the people panel to talk with other players. Voice has controls to mute your microphone or deafen yourself. Open a person's menu to mute, block, or report them.
For your own game, ask Savi to customize Spawn's chat, such as who can talk or which groups can hear each other.
Can I connect games with portals or make a hub?
Yes. Ask Savi to make a portal to another game or to another Place in the same game. You can build a hub with doors to several games, including games by other makers.
A portal you build as part of a game is different from the temporary portal you open to visit a friend.
Can pets, items, and vehicles go through portals?
Spawn 6 supports taking things through portals, including pets and vehicles. What can enter depends on the destination's rules and how the thing is set up.
Tell Savi what you want to take across. Test the crossing in both games, including what happens to the item or vehicle on arrival.
Who can open a portal to me?
In Settings, set portal to me to friends or anyone. The default is friends. Blocking someone prevents them from opening a portal to you or sending you a portal invitation.
A portal appears in the game, so nearby players can use it too. The destination's entry rules still apply. Ask Savi to set those rules for your own game.
Publishing and updates
How do I publish my game?
Select Publish while editing. Follow the publishing panel to choose your cover and release the game. Once it is published, copy its play link and share it.
A published play link looks like spawn.co/@yourname/your-game/play.
Do players see every change as I build?
Visitors to your editing session can see the work in progress. The published play link opens the released version.
Publish an update when you are ready for players to get your changes. You can keep the same play link.
Where can I see how my game is doing?
While editing a published game, select Published or Publish update near the top right. The panel shows total plays, weekly players, weekly playtime, and the notes players left you.
How do I upgrade an older game to Spawn 6?
Open the engine version panel in your game. Choose Upgrade to 6.0, then confirm. The panel shows the result and anything that needs attention.
Try the important parts of the game after the upgrade. If something breaks, tell Savi what changed and include a debug report when you ask the team for help.
Can I return to the engine version I used before the upgrade?
For a game converted to Spawn 6, the engine panel can offer Back to v… for its previous version. Read the confirmation before proceeding.
A game created in Spawn 6 has no earlier engine version to return to. To undo changes within that game, use its change history instead.
Community
What is SpawnJam?
SpawnJam is the community game jam. Each jam has a theme, a start time, a deadline, and prizes. Visit SpawnJam for the current rules, dates, and entry steps.
Read the current rules before building or submitting. They explain what you can prepare in advance and how judging works.
How do I join the Partner Program?
Partners are selected based on what they make. Share your game with the team in Discord and ask about the current program.
Can I charge players for access or subscriptions?
Paid access and recurring game subscriptions are not currently available to makers. For ways to take part in prize competitions, see the current SpawnJam.
Where can I get feedback or find people to build with?
Join the Spawn Discord. Share your game, say what kind of feedback you need, or describe the project you want help building.
Getting help
When should I ask Savi for a fix, and when should I report a bug?
Ask Savi when something in your game behaves differently from what you intended. Describe what you did, what happened, and what you expected. /debug can help start that investigation.
If Spawn cannot load, a control does not work, or the problem keeps returning, send a bug report to the team. Savi can report a problem too.
How do I send a useful bug report?
Use the bug-report button in Savi's chat, or open Settings and select bug report. Post the report in #bug-reports with:
Your game's link.
What you did just before the problem.
What happened and what you expected.
Your device and whether you used a browser or the app.
A screenshot or short video helps when the problem is visual.
What should I do if my game is slow or something will not load?
Reload once. If the problem continues, send a bug report from that game and describe the slow or broken part.
For a slow game, ask Savi to investigate the part that costs the most. For a missing object or lost change, check the game's history before rebuilding it. Tell the team if a saved version will not open.
Your own servers and database. Spawn runs your game's servers and keeps your players' progress. A game that depends on a server of yours can stop working, and we can't feature it.
How to code it. Tell Savi what the game is and how it plays. She picks how to build it in Spawn.
what comes across
Your game's rules, levels, controls, screens and art. Your pictures, models and sounds come across as they are. Your code is rewritten to run on Spawn's engine.
what spawn gives your game
Multiplayer from the first moment. Anyone who opens your game plays in the same world as everyone there, and you write no networking code.
A link that plays anywhere. No install and no account needed to play.
Phones too. Your game can play on phones, with touch controls made from its own controls.
Saves on their own. Your players' progress keeps without a save system of yours. A Spawn player's body and progress last between visits, so a second visit to an imported game picks up where they left off, where the original starts over.
Chat, reviews and likes. Every game comes with them, beside the game.
Change it while people play. You build in your own copy while players keep the version you published, and your changes show in your copy without a reload.
Every change kept. Each change is a version, and Savi can take the game back to any of them.
Players find it. Publish it and it shows on Spawn's home page under new.
If something plays differently, tell Savi what you see, and she works on it in the game.
what happens after this is youtube. not the cringe internet-pundit version of that comparison, the actual one. youtube didn't make everyone a great filmmaker — it made trying cheap enough that millions of people tried, and most were bad for years, and a meaningful fraction of those people, by watching each other and copying each other and getting torn apart in comments and trying again, became better filmmakers than the film-school graduates whose tuition could have paid for an apartment. the medium taught itself. there was no curriculum. it was a million people in public, learning from a million other people in public, with the activation energy low enough that giving up and starting over cost nothing.
spawn has to be that for games. there's no other way the medium gets a hundred times bigger, which it has to. right now there are about two thousand games shipped on steam in a year. spawn creators are already publishing more than that, most of them bad in the specific way that early youtube was bad: imitating the formats people already know, badly, with too much enthusiasm and not enough taste. that's correct. that's the early phase. taste is a community phenomenon — it doesn't get installed in anyone before they start, it grows from looking at what someone else made and quietly deciding what you'd have done differently.
what we want at the other end of this isn't infinite slop. it isn't a feed of disposable games engineered to keep someone tapping. games are the only medium that does both of the things humans want most from culture: they give you a place to belong, and a thing to chase that you actually pursue instead of watch. when you lead a guild in world of warcraft, the leadership is real even though the dragons aren't. when you build a house in minecraft with a friend, the friend is real, the house is real, and the afternoon is real, even if none of it exists in a way an accountant would recognize. one of the games made on spawn is going to be one of those — and not because a committee tuned it for retention, but because one person with a vision finally got to express it without first becoming an engineer.
my girlfriend is going to build her game. the mushrooms will be the exact right shade of brown. the soup will simmer convincingly. the town will be small but the people in it will feel like they belong there. a few hundred people will play it, a chunk of them strangers, and someone she's never met will message her at 1am to say she's still foraging. that is the medium working. the next person who makes a game on spawn will have seen hers and learned something from it. the person after that will have seen both. ten years of that, and the games on spawn will be unrecognizable — and somewhere in the middle of them will be one, made by someone nobody had heard of who spent a year of evenings with savi, that some kid plays through three times in a weekend, watches her best friend play, and then sits down to make her own.
The door in: a creator copies one prompt from their world's /code page and pastes it to you — it signs you up, links you to them, and makes you an editor of that world in one call. Or knock from your own account: POST https://www.spawn.co/api/games/<appId>/crew/ask; they approve from their bell.
Your own account, your own fuel: an unlinked account makes 3 worlds a day and pushes up to 600 times per world per hour; it never spends inference or GPU (403 agent_lane_closed at every such door; me.budget.lanes names each closed lane's ask — the person to appeal to). Linked to a person, you run under their allowance.
Use a clear commit message. Its first line tells the creator what changed for the player.
Read the live room without a browser: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/rooms · logs · docs · skills/<id>; POST https://www.spawn.co/api/sdk/v1/<worldId>/agent/exec with {"script":"return api.query({tags:[\"enemy\"]}).length"} runs read-only JS in the room (409 no_live_room when nobody is in it — your own join is the room); its `logs` are the lines your script printed and the engine's teaching about your calls, and the room's own log is agent/logs. PUT https://www.spawn.co/api/sdk/v1/<worldId>/assets/<name> puts a file of yours — a .glb body, a texture, a sound — on the CDN by its bytes and answers the URL that serves it (editor standing); a body rides the request only under 4.5 MB, and a bigger file goes by address: POST https://www.spawn.co/api/sdk/v1/<worldId>/assets/upload-target first (llms.txt spells the three calls).
Build, test, and share
Make a game, join it, and test the changes from a player's view. Check its logs and look at the result before sharing it.
Publish when the game is ready for players. Share its play link so friends can join.
The whole contract, machine-readable: https://www.spawn.co/openapi.json.
engine v6.0: One Place
Released September 5, 2026. Worlds with no size limit, portals you can see through and walk through with no loading screen, any number of people in one world, and Savi building beside you while your players keep playing. read
engine v5.2: Lume
Released July 10, 2026. The renderer, rebuilt in-house: your worlds look the same and run on a fraction of the GPU — faster loads, cooler machines, longer battery. read
v5.2.41 (September 11, 2026): Everything timed in seconds now lasts the time you wrote (shake, fades, zoom and sprite frame rates ran up to 1.75x fast before), a click in god mode no longer resizes a shape, textures on small primitives and on phones draw the right way up, a campfire no longer shrinks every other particle on screen, a floor Savi swaps for a model stays solid until the model is ready, characters report their wall and floor touches, big worlds finish loading their textures on a slow connection, star and moon fades no longer stutter, the bug-report button no longer freezes the game, a player whose tab died no longer leaves a ghost behind, and multiplayer physics runs only where someone is.
v5.2.40 (September 3, 2026): Walls in top-down games block along their whole height and the collision shapes you drew survive a save, a world with terrain off no longer shows a mountain skyline it does not have, the parts a player's body builds at spawn show for everyone who joins, fences attached to a raised building sit on the ground, a sky change your script makes reaches every player, tearing down a whole floor no longer freezes physics, big generated worlds load their places many times faster, and one bad packet from another player no longer drops the good ones with it.
v5.2.39 (September 2, 2026): Things your scripts hid or spawned stay that way when you leave an area and come back, sound starts on your first tap in games with their own on-screen UI, reloading inside a place brings you back at your game's spawn, a second tab on the same account tells the first one right away, a saved script or player change reaches your own game without a reload, and worlds with many rivers and ponds build their ground faster.
v5.2.38 (September 1, 2026): Placeholder shapes disappear when a model lands on them, a returning player's whole character comes back for everyone, repeated digging and filling no longer slows the game down, scripted shapes respect their shadow settings and land on the ground where they stand, big skybox uploads render at 4K, and Savi's builder stays in your room for the whole session — and a first-person camera renders the eye height its script authored.
v5.2.37 (September 1, 2026): Rebuilding and repairing mined areas works again, rapid Savi edits no longer hitch big games, gravity changes apply instantly on every physics engine, objects no longer freeze after your tab stalls while Savi's builder is in the room, and sliders work in creator-tab panels.
v5.2.36 (August 29, 2026): Clicking your game's buttons no longer steals the keyboard, models with shape keys can blink and smile, uploaded models are solid in multiplayer rooms, objects stop flickering back to old values when two players or Savi edit them at once, busy rooms no longer crash the browser tab, and a player's browser extensions are never mistaken for your game's messages.
v5.2.35 (August 29, 2026): Games can read their launch link (QR/invite codes) and send players to specific rooms, deleted things stay deleted for everyone, saves stop un-saving themselves, gravity applies at full authored strength, attached models can wear their parent's animations, materials gain renderOrder and honest always-on-top drawing, spot light angles are plain degrees, giant worlds stream between places without freezing, and quiet NPCs stop taxing every player's machine.
v5.2.34 (August 22, 2026): Six cures: deleted objects can never pop back after the save confirms, players' script-driven saves stop failing silently in some rooms, tweaking one knob on a custom material no longer wipes the material, group placed pieces without anything moving (keepWorld), roads can vary width along the route, and Savi's builder can join games on newer engine versions again.
v5.2.33 (August 22, 2026): Fifteen cures in one: vehicles stop reloading scrambled, drags stop teleporting to the last save, Ctrl-Z survives reloads in multiplayer, ghost copies of players stop appearing while Savi's builder reconnects, stale tabs can't cross players into your editing room, middle-click is reliable, grass reads green from both sides, things stay the right size entering new areas, game UI can save files, scripted terrain edits stop wiping paint, and slow machines stop tearing themselves down to 'recover' from their own lag.
v5.2.32 (August 20, 2026): Ten cures in one: meshes reworked behind a hidden tab reappear, objects created through a save land for every joiner, custom-cursor games click again on desktop, multi-area games stop losing areas, shared UI library edits hot-reload, phantom version churn ends, momentary server hiccups stop reading as dead models, static-model shadows return on iPhone/iPad, big worlds stream in smoother, and creators can cap the frame rate.
v5.2.31 (August 20, 2026): Sixteen fixes in one: desktop clicks work again in click-driven games, big built-out worlds run much smoother while you build, scripted movers stop freezing in long-running multiplayer rooms, long multiplayer music stops dying after a second, riders stay seated instead of running in place, rotations stick while you drag, 2D characters stop flashing white between animations, spawn-storms no longer flood the room, and pause menus can catch the first Esc.
v5.2.30 (August 19, 2026): Thirteen fixes in one: quiet saves for multi-area games, touch-ready script buttons, taps that land on bridges and platforms, terrain edits that persist, smoother joins on busy rooms, no tab-return flashes, and steadier building while wisps work.
v5.2.29 (August 17, 2026): Everything since 5.2.26 in one release: big worlds stop melting down in multiplayer, Savi sees when and why the engine slows something down on purpose, missing and ghost objects repair themselves, and script math is exact again.
v5.2.26 (August 16, 2026): Terrain edits now sync reliably in always-on worlds. Players who rejoin get the terrain exactly as it was edited — edits made by scripts or by players who have since left no longer silently vanish on rejoin. And freshly edited chunks rebuild ahead of background work, so digs and builds turn solid and visible faster even while the world is busy streaming.
v5.2.25 (August 14, 2026): Big worlds with lots of detailed scenery run noticeably smoother while you walk around — the engine now remembers collision shapes it has already built instead of rebuilding them from scratch every time objects stream in or toggle their physics.
v5.2.24 (August 14, 2026): Players in other places can now receive state. The classic pattern — queue the party in the lobby, warp to the arena, then tell everyone their match — just works: patchObjectState(playerId, {...}) reaches a player anywhere in the room, and the new getPlayerPlace(playerId) tells you whether someone left the game (null) or is just in another place. No more heartbeats, shepherds, or ticket systems to work around invisible teammates.
v5.2.23 (August 12, 2026): Savi now files the features you keep wishing for with the Spawn team — a dream that comes back session after session gets written down once, in your words, instead of staying her private workaround.
v5.2.21 (August 7, 2026): When a database operation takes a moment longer than a script run allows, Savi now gets a plain explanation — the database is answering, nothing hung, just re-run — instead of a scary "hung await" error that used to send her hunting for a bug that wasn't there.
v5.2.20 (August 7, 2026): Cleaned up engine diagnostic noise that every game session was quietly emitting — no visible change in your game, slightly less background chatter from the engine.
v5.2.19 (August 6, 2026): Small windows render sharp: shrinking the game window no longer melts distant detail into mush — thin lines, far-off structures, and in-world text stay readable at small window sizes, because the engine now refuses to drop its internal rendering resolution below a legibility floor on ordinary screens.
v5.2.18 (August 5, 2026): Sounds can now stick to the thing that made them: playSound(clip, { position, follow: true }) keeps a sound on a moving object instead of leaving it behind at the spot it started — your own footsteps, engine hums, and whooshes stay with you instead of trailing behind as you run.
v5.2.15 (August 4, 2026): You can now put the game's "ear" anywhere — pin it to a ring-side mic, a security camera, or a moving NPC, and all spatial sound pans and fades from there instead of your camera. One place setting, and clearing it puts the ear right back.
v5.2.14 (August 3, 2026): Safari no longer eats all your memory while a game sits waiting for its first click — the bug that could freeze a whole laptop on a quiet world is gone.
v5.2.13 (August 1, 2026): Cameras are yours now, all the way down. Savi writes your camera as a script she can read and edit — every zoom, follow, and framing choice is a line she can change — instead of flipping switches on fixed camera presets. Existing games keep playing exactly as they are; when a world upgrades to this version, Savi rewrites its camera as a script with the same feel.
v5.2.12 (July 31, 2026): Buttons work on phones now. Action buttons Savi builds — especially in scrollable lists — used to die in mobile touch handling: you'd tap and nothing happened. The engine owns the tap now: a tap fires exactly once, a real scroll stays a scroll, and every existing game heals with no edits.
v5.2.11 (July 30, 2026): Savi can now measure your world instead of eyeballing it: asking for an object's bounds answers the real loaded size of models (stacking, fitting, and aligning become arithmetic), and while a model is still downloading she gets an honestly-flagged placeholder or a clear "still loading" note instead of a silent nothing — so things land ON tables, not 0.18m into them.
v5.2.10 (July 30, 2026): Worn gear welds on, moving platforms carry you, cooking models show their art
v5.2.8 (July 28, 2026): Power lines plant their poles again
v5.2.6 (July 27, 2026): Fixed a failure mode where a player could sink into (or bob on) one patch of ground forever with no explanation: if the game client repeatedly fails to build the ground under a player, it now stops silently retrying, tells Savi exactly which chunk failed and why, and shows the affected player an honest "reload to rejoin" message instead of leaving them stuck.
v5.2.5 (July 26, 2026): Physics got a big quality pass in worlds using the new physics engine — cleaner collisions, fast objects stop tunneling, vehicles handle better, and things settle instead of jittering. Busy worlds also run noticeably cheaper.
v5.2.4 (July 19, 2026): Fixed top-down (2d-top) characters colliding ~1m south of where their sprite stands: walking into a wall from the north stopped short, from the south overlapped, and the debug collider circle drew below the character's feet. Colliders now sit exactly at the sprite's feet regardless of the object's rotation.
v5.2.3 (July 15, 2026): Fixed god mode getting stuck at an invisible floor in games with terrain turned off — you can now fly down to builds below height 0 instead of being silently held at the old ground level.
v5.2.2 (July 14, 2026): Fixed sprites and objects that had stopped moving randomly lurching a few pixels out and back in quiet scenes (most visible on parked critters in 2D games). Resting entities now hold their position exactly until they actually move again.
v5.2.1 (July 14, 2026): Growing black patches are gone. On some machines, dark blotches could appear on screen (worst at night) and spread until they swallowed the whole view — reloading didn't help. Fixed at the source, for good.
engine v5.1: Connection
Released June 18, 2026. Your game listens to you first — movement and actions respond the instant you press them, and multiplayer holds steady through the busy moments. A full rebuild of how players stay in sync, plus dozens of touches to sound, saving, and Savi's tools along the way. read
v5.1.13 (July 8, 2026): When your game's music code hits a wrong note — an unknown drum name, a bad pattern — Savi actually hears about it now, with a helpful nudge toward the closest real instrument. And "tabla" just works.
v5.1.12 (July 7, 2026): Fixed a reconnect trap that could freeze a player's world forever: if the room restarted while a tab stayed open, that player could get stuck repairing hundreds of times and never recover without a reload. Recovery now works in one clean step.
v5.1.11 (July 6, 2026): Savi can now invent animations for your characters — a swim stroke, a dance, a wing-flap — by writing them as motion code, no animation files needed. They play (and blend) just like regular animations, and edits take effect at the next loop so nothing pops mid-motion.
v5.1.10 (July 4, 2026): 2D games got a big placement upgrade: backgrounds and distant scenery can now be glued to the camera, so they always fill the screen — no more backdrops drifting away from the view, floating set pieces, or stretched skies. Repeating strips tile seamlessly across the whole view, parallax layers slide at their own speeds, and everything holds up at any screen shape from tall phones to ultrawide.
v5.1.9 (July 3, 2026): ⚠️ If your world suddenly looks different after this update: your custom look script is running again. It was silently crashing on the last few engine versions (since around 5.1.5), so your world was rendering with no look applied at all. The crash is fixed and your authored look applies again — that new appearance is your own look script working. If it feels off (too dark, too bright, too saturated), ask Savi to retune the exposure — don't delete the look.
v5.1.8 (July 2, 2026): Side-scroller levels with visual-only heightmaps no longer get fake ground snaps or repeated collider rebuild warnings.
v5.1.6 (June 26, 2026): Large terrain worlds spend much less CPU maintaining stable physics colliders.
v5.1.5 (June 23, 2026): Bloom is now much more performant.
engine v5.0: For Real
Released June 4, 2026. A million particles, real skies, enemies with brains — the world got real, and Savi can build all of it. The biggest engine release yet. read
v5.0.15 (June 12, 2026): Multiple moving shadow-casting lights now all keep their shadows — previously only one moving light at a time could.
v5.0.14 (June 12, 2026): Colored and projector light shadows now work for as many lights as your scene needs — they previously stopped working past one or two on many graphics cards.
v5.0.13 (June 12, 2026): Boardwalks built down slopes with tight switchback corners now render coherently — no more railing bars shooting past hairpin turns or flickering planks on long straight runs.
v5.0.12 (June 12, 2026): Sounds in 2D games are actually audible now! Dig thunks, impacts, and pickups were playing at a tiny fraction of their volume because the game listened from the camera instead of your character.
v5.0.11 (June 11, 2026): Savi's script tools work again in solo games with mouse-look cameras — a 5.0.10 regression broke her ability to run scripts there.
v5.0.10 (June 11, 2026): Fixed a bug where talking to Savi with your voice could get stuck in a silent retry loop if the microphone pipeline failed to start — it would quietly hammer away forever and flood our error logs while voice just didn't work. Now it tries a few times, tells you plainly that voice is off for this session, and typing keeps working (reloading the page may bring voice back). Quick tap-and-re-hold on the mic can no longer be mistaken for a real failure.
v5.0.9 (June 9, 2026): 3D models are now automatically optimized for better performance, with additional simpler versions used as they move farther away.
v5.0.8 (June 8, 2026): Shadows now fit every graphics card the same way: machines with tighter limits (many Macs) keep full shadow quality at every tier instead of dropping to a single sun shadow. Secondary sun shadows in big worlds render slightly smaller on low and medium quality.
v5.0.7 (June 7, 2026): Games now automatically turn down expensive graphics on hardware that can't keep up — effects cadence first, then shadow distances, then bloom and resolution, and only on the struggling device. Same game, same content, smooth on more machines; the device remembers where it landed so the next session starts there.
engine v4.6: Atelier
Released June 1, 2026. A real workshop for god mode — tabbed tools, undo/redo, and richer material looks. read
engine v4.5: Surface Tension
Released May 22, 2026. Water you can swim in, and shapes that look like the real thing. read
v4.5.2 (May 27, 2026): Animated models always play something — falls back to an available animation instead of standing still.
v4.5.1 (May 23, 2026): Ponds run much smoother without changing how they look.
engine v4.4: Solid
Released May 15, 2026. Things stack right, worlds load clean, and clicks land where you point. read
v4.4.3 (May 21, 2026): Fixed some characters appearing too small.
v4.4.2 (May 20, 2026): Build bigger worlds with lots of places — areas no one is in quietly sleep so the game stays smooth, and snap back to life the moment someone walks in. Your spawn area is always ready.
v4.4.1 (May 16, 2026): Savi places things on top of anything now — models, primitives, sprites, custom geometry, or text, she knows the size and lands the placement first try.
engine v4.3: Groovy
Released May 13, 2026. Savi is your DJ now. God mode, movement, and controls all feel right read
v4.3.1 (May 13, 2026): Walls and floors are back in 3D Rooms games. Players land cleanly, walls stop the player, and skeletons stand on the floor instead of falling into it.
engine v4.2: Continuum
Released May 9, 2026. Saved games, smoother animation, sharper aim, and a basket of polish fixes you'll feel right away. read
engine v4.1: Foundations
Released May 4, 2026. First big engine update. Faster, smoother, smarter — and a small mountain of fixes. read
engine v0.1: Genesis
Released April 29, 2026. Initial versioned engine release. read
v5.1.4 (June 22, 2026): Performance improvements for spoin animations also make games run faster.
v5.1.3 (June 22, 2026): Savi can now notice and help fix visual effects, interface panels, sounds, and other game behavior that fails only on a player's device.
v5.1.2 (June 19, 2026): Scripted materials no longer lose their shading after reloading a game.
v5.1.1 (June 19, 2026): Room-based multiplayer games now recognize the correct room on every player, so shared lobby counts, match progression, and room controls keep working.
v5.0.6 (June 7, 2026): Screen ripples and water stop blacking out the frame, statues are solid in solo worlds again, NPC brains stop going blind to the world around them, standing on hills actually means standing, sound effects stop going permanently silent mid-session, dark-world graphics hiccups heal themselves, and Savi can finally see which effect is which.
v5.0.5 (June 7, 2026): Savi stops nagging about performance: at most one heads-up per hour, only for games genuinely slow for minutes on end, and she never changes your game over it without your say-so.
v5.0.4 (June 7, 2026): Skies now cost almost nothing, multiplayer sessions stop randomly dropping players, and mobile play opens the moment a game declares it.
v5.0.3 (June 6, 2026): Launch-week fixes: solo worlds keep every area, portals stop flinging you home, joins always retry, first effects play clean, and the engine heals broken ground and graphics stalls on its own.
v5.0.2 (June 6, 2026): The editor cursor finally feels like your real mouse — pixel-for-pixel, no more laggy ghost trailing your hand in god mode
v5.0.1 (June 6, 2026): Scripts that animate with Math.sin, ease with Math.exp, or steer with Math.atan2 now give the same answer on every machine. Cars and props you drove through obstacles no longer stutter mid-drive. Math results may shift by amounts far below anything perceivable (the same everywhere), in exchange for driving, easing, and orbiting code that stays smooth.
