Publish your game and track your versions
Any project member can record a release. Maintenance mode and rollbacks are reserved for the project owner.
VibeStarter does not publish your game. Publishing is still something you do in Roblox Studio. What the app does next is record which version is live, so you always know what your players are playing and what has changed since.
The assistant sums it up this way: “A release records which version of your game is live on Roblox — so you always know what players are playing, and what has changed since.”
Before you start
Section titled “Before you start”- Your place must be open in Studio and linked to your project.
- Your latest code must compile, or Studio keeps showing the previous version.
- If you have several worlds, each one is published from its own Studio window.
Publish, then record the release
Section titled “Publish, then record the release”- In VibeStarter, open the Versions panel, then click Record my first release…. Once a release is recorded, the button becomes Publish a release…; it disappears when nothing has changed since (“Up to date with the live version”).
- On a project saved online, the assistant first checks that the team’s work is included, and confirms “All team work is included — you’re releasing the latest version.”
- It then checks that Studio has your latest code: it sends the build, then confirms “Studio is showing your latest code.”
- Wait for these confirmations, then follow the Publish from Studio step: in Roblox Studio, open the File → Publish to Roblox menu. The assistant repeats the path and the shortcut.
- Click I’ve published — record it. The app records the release and its number.
If team work was still missing when you record, the app merges it in and says so: “Check the game, publish again from Studio, then record the release.”
If a sync is already running, the assistant waits for its result. As long as the save or the merge of changes is still pending, it does not confirm that the project is ready. Finish the sync, then click Retry.
If a check fails, the app tells you which one:
| Message | What to do |
|---|---|
| “Studio isn’t connected — open the place to publish your latest code.” | open the project’s place in Studio |
| “Your latest code doesn’t compile — Studio still shows the previous working build. Ask an agent to fix the error.” | a code agent is running in the project: ask it to fix the error, then try again |
| “Your latest code doesn’t compile — Studio still shows the previous working build. Launch an agent to fix the error, or fix the file yourself.” | no code agent is running: start one or fix the file yourself, then try again |
If the project’s release history cannot be read, the app refuses to record a release rather than starting from scratch. “The release history could not be read”: try again in a moment. “The release history file (.vibestarter-releases.json) is damaged”: fix or restore it before recording a release. Maintenance mode is blocked in the same way.
Fix the live version without breaking your work
Section titled “Fix the live version without breaking your work”Your players play the published version; your project, meanwhile, has kept moving forward. To fix a problem in production without shipping everything you’ve done since, the app offers a maintenance mode.
When you enter maintenance, the app explains what it does: “Studio will show the game exactly as players see it. Your dev work is saved first, and team sync is paused.” A banner stays visible the whole time: “You’re fixing the live version. Sync is paused until you cancel or publish the fix.”
When it’s over, the app goes back to your work in progress and sends you back to Studio: “Back to the dev version — Studio is resyncing your dev code.”
Several worlds: publish each one
Section titled “Several worlds: publish each one”Publishing one world does not put the others live. If a change affects two worlds in your game, open each affected Studio window and publish it, then record the release. See Several worlds in one game.
Limits
Section titled “Limits”- Publishing cannot be triggered by the app or by an agent. It is always your action, in Studio.
- Entering maintenance mode and going back to an earlier version are reserved for the project owner.
- During maintenance, team sync is paused: let your teammates know.
Frequently asked questions
Section titled “Frequently asked questions”I pushed my code but players don’t see anything. Sync brings your code to Studio, not to the players. You still need to publish from Studio, on each world you changed.
How do I publish an update without breaking players’ ongoing games? Publish from Studio, then record the release. Servers that are already running keep running the old version: they have to restart for your players to get the new one.
What’s the difference between a backup and a release? Your code is backed up continuously, separately from all this. See Your code is saved automatically. A release, on the other hand, marks the exact point your players are playing.
Can I go back to an earlier version? Yes, from the versions panel, and it is reserved for the project owner. See Go back to an earlier version.