spawn
playmake
Ctrl+K
sign in
make a game
PlayMake
← about

Engine v5.2.39

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.

September 2, 2026

A patch to Lume.

  • When Savi previews a custom material and a setting was spelled in a way the material never reads, the preview now says so instead of quietly showing the default look.
  • Objects your scripts spawned at runtime — village props, walls, cove pieces — come back visible when you are the first to rejoin a room everyone had left. Before, they stayed solid but invisible until a script touched them.
  • In god mode, clicking into the toolbar's search box while holding a movement key no longer leaves the camera flying on its own.
  • If your own character was removed from the world by a script and you press the god-mode key, the message now says what happened and that a reload brings you back — instead of wrongly saying you lack permission.
  • If your world's water uses the low-level liquid.overrides settings — depth tint distance, wave frequency, foam coverage, caustics strength — a change to only those settings now shows up right away. Before, the water kept its old look until some other water setting changed too.
  • When the player hosting an area of your world walks out of it, the things you built there no longer vanish for someone who joins right after. Before, a new player could arrive to an empty area for a few seconds.
  • A change Savi makes to your player shows up in your own game right away, not just in other players' games.
  • Sound now starts on your first tap in games with their own on-screen UI, on phones too.
  • When something your script spawned vanishes a few seconds later because a write to another player's character was refused or never answered, Savi's logs now say so — which write, why, and how many things it took with it — instead of nothing.
  • When the game drops an effect because the thing that sent it had already left the room, Savi's log reads now say that. Before, the same line read like a rule about who may do what.
  • Reloading while inside one of your game's places no longer drops you at another place's start spot, falling through the dark. You come back the way a reload has always been meant to work: at your game's spawn, unless your game saves and restores position itself.
  • When the same account opens a game in a second tab or on a second device, the first one now says so right away ("This game was opened in another tab or window…") and stays put, instead of going quietly stale and cutting back in every time you switch to it.
  • Worlds with many rivers and ponds build their ground faster. Each piece of ground no longer redoes the river and pond water math that an earlier piece already did.
  • When Savi saves a script from inside the game, the objects running it pick up the new version right away — including in the world that ran the save.
  • When the server turns down one of a sprite's animation clips, Savi's logs now name that clip and show the server's reason and when the engine will ask again. Before, the log said the clip was "still generating" and left out the reason.
  • When a sprite setting such as its named animation is removed from a game's spec, sprites already in the world drop the old value when that edit is applied, instead of keeping it until a reload.
  • After you leave and come back to a part of your world, the things your scripts hid stay hidden and the things they spawned stay.
  • In worlds on the Mantle physics engine, walls and floors your scripts shaped with their own collider are now solid for players who join after they were built. Before, only the player whose game built them could stand on them.
  • When things your script spawned vanish a few seconds after it wrote to a player whose tab was in the background, Savi's logs now say that the background tab is the cause instead of only "no answer in time".
  • An arena your game creates on the fly keeps running when the player who opened it tabs away.

more from spawn

  • what spawn is
  • frequently asked questions
  • bring a game you already made
  • the spawn bet
  • One Place
every engine update →