Start with a verifiable core loop
A useful creator request is not a feature pile. It names a loop a player can experience, then lets theme, difficulty, and visuals support that loop.
- Describe the exact intended change and the parts that must remain unchanged.
- Download immutable Builds before and after a revision.
- A new Build needs its own runtime evidence; old evidence stays historical.
A safe revision checklist
Record the current Build ID and download it before changing anything. State the intended change and what must remain unchanged. Review the proposed plan or exact code diff, then approve one bounded change. Compare the new Build report with the previous one. Re-run Studio tests against the new Build because an older passing report cannot prove the new file works. If the revision fails, restore the saved snapshot rather than guessing which files changed.
Copyable revision prompt
In my current Roblox prototype, widen the landing platform after the second checkpoint. Keep the route order, coin count, and finish reward unchanged. Show the exact proposed change before rebuilding, preserve the old Build, and list the Studio tests I should repeat.