Appearance
Trying things without an audience
Your world is always up. That is the good part: there is no file to open, no build to wait for, and the thing you are editing is the thing people are playing.
It is also the problem. You cannot delete half the map to see what happens while somebody is standing in it.
Solo is the answer: a private copy of your world, running on the server, with only you in it.
Opening one
In the editor's top bar, press the fork button. The client leaves the world and comes back into a copy of it.
You will know you are in one: an amber SOLO badge sits next to the world's name in the editor bar, and in the game's header when the editor is closed.
Only the world's owner can open a solo session. Building or moderating somebody else's world does not include copying it.
What is in the copy
Everything, as it was the moment you opened it: every object, every script, the terrain, the world's age, the weather, the tags — and where you were standing.
It is the same kind of world, running the same code, with the same physics and the same permissions. Nothing behaves differently in there, which is the whole point: what you prove in solo is true outside it.
Two things are not copied, both deliberately:
- Other people. Nobody can join; there is no way to invite anyone, and the world directory never lists it.
- Your inventory is not copied — it is the same inventory. A copy of the world is not a copy of you. What you take, wear or store belongs to your account in every world.
Leaving discards everything
When you leave a solo session, the copy is thrown away. Nothing you did in it reaches the real world: not the objects you moved, not the terrain you carved, not the scripts you rewrote.
Write down what worked before you leave. A script you fixed in solo is not fixed in the real world. Copy the text out, or make the same edit again outside.
That is a deliberate trade. A session you can wreck without consequence is only useful if wrecking it really has no consequence, and any "merge back" would put that in doubt every time.
What it is good for
| Destructive tests | delete the floor, drop a hundred crates, set the weather to a whiteout |
| Timing | fast-forward a growth cycle without anybody watching plants pop |
| Weapons | tune recoil and spread without shooting at visitors |
| A rewrite | try a different approach next to the working one, and throw one away |
What it is not
It is not a staging server, and it is not version control. There is no promotion step, no diff and no history. For keeping a version you can return to, keep the text of the script somewhere you control — the VS Code project folder is a reasonable place, since you can put it under your own version control.