Getting Great Results
Roflow builds, then plays your game to check its work. The clearer your request, the better both the build and the checks.
Say what should happen in the game
Describe the outcome a player would see, not the code:
- Weak: "Improve the coins."
- Strong: "Each coin gives 1 coin, disappears for 3 seconds after it is collected, then comes back."
Roflow's reviewer writes its play-test checks from your words. A request with a concrete outcome gets concrete checks; a vague one may leave parts unverified.
Name what must keep working
"Fix the duplicate pickup reward without breaking legitimate pickups." Roflow checks the things you name, before and after the change.
Point at the right place
Name the system, screen or part you mean: "the shop screen", "the JUMP button", "the coin script in ServerScriptService". On a game you already have, this keeps Roflow from changing the wrong thing.
One change at a time
A request that does one thing gets one clear set of checks and one easy undo. For a big game, build in stages: see Building in Stages.
Pick the right effort
Medium is right for most work. Use Low for small tweaks and questions, and Max for big builds or a bug Medium could not fix. See Usage.
Read the report
When Roflow finishes, it says what it checked. Open Progress for the full play-test report. Pay attention to unverified checks: they are things Roflow could not see, not things that passed.
Quick checklist
| Ask yourself | If not |
|---|---|
| Could a player tell whether this worked? | Describe the outcome they would see. |
| Did I say what must not change? | Add "without breaking…". |
| Is it one change? | Split it. |
| Is it a hard bug that keeps failing? | Try Max effort. |