Games You Already Have

Roflow works on existing games as well as new ones. Open your game's place in Roblox Studio and ask for a change. Roflow notices that the place already has scripts and treats every request as a change to this game, never as a fresh start.

Roflow reads your game first

New in Roflow 2.0.4. The first time Roflow changes a game you already had, it reads the place, its instances and scripts, and describes the game as it plays now: how players spawn, what they do, how they progress, the controls, the devices it supports and whether it saves data. That description becomes the game's brief, and it shows in Progress as Read from your game. Anything you have set yourself stays yours.

It plays your game before fixing it

For a fix ("coins are counted twice"), Roflow plays your game before changing anything and runs the checks for your request. If the bug shows up, you see "Roflow played your game and saw the problem" with what it observed. After the fix, the same checks run again, so you can see the before and the after.

For a refactor or a speed-up, the checks should pass before the change. Roflow runs them before and after to show that what worked still works. If a fix's checks already pass before the change, Roflow tells you they may not test the problem instead of claiming a fix.

It reviews its own code

New in Roflow 2.0.4. When a change passes its play-test, Roflow also reads the scripts it changed, before and after, and posts a short review in the chat: what changed, whether it touched anything you did not ask for, and any risk it sees, such as a value the server trusts from the player's client. Anything likely to be broken is marked Problem.

Checkpoints

Roflow saves a checkpoint before every change it makes in Studio. Open Undo & checkpoints in the left list to see them, and Review restore to see what a restore would put back before you apply it.

Restoring puts scripts and property values back as they were. It does not remove parts added later or bring back deleted parts. Roflow saves a new checkpoint before restoring, so a restore can be undone too. If you edited something yourself after the checkpoint, Roflow warns you before overwriting it.

Tips

• Name the thing that must keep working ("without breaking legitimate pickups") and Roflow checks it.
• One change per request gives the clearest checks and the easiest undo.
• Places set up by Roflow on another computer or account belong to that Roflow. Open a copy of the place to work on it here.