Making wishes: how to ask
How to describe what you want so RoGenie builds the right thing the first time, with examples, attachments and follow-ups.
On this page
A wish is just a message: describe what you want in plain words. RoGenie plans it, writes the Luau, builds it in your place and playtests it. The more useful detail you give, the better the result.
Good wishes say what, where and how you will know it works
| Instead of | Try |
|---|---|
| "make a shop" | "Add a shop GUI that opens when the player touches the shop pad. Sell a speed coil for 50 coins and a gravity coil for 80. Coins are in leaderstats.Coins." |
| "fix my gun" | "The pistol in StarterPack.Pistol fires but never damages NPCs. Fix it so each hit does 20 damage, server-side." |
| "build a map" | "Turn the baseplate into a low-poly desert canyon about 600 studs long with a winding path, a few cacti and a small town at the end. No Toolbox models." |
What helps:
- Where things are. Name the service, folder or script ("in
ServerScriptService.Combat"). - Rules and constraints. "Server-authoritative", "mobile-friendly UI", "no Toolbox", "keep the existing NPC folder untouched".
- What done looks like. "Players should keep their coins after rejoining." RoGenie uses this to decide what to playtest.
- Style. "Low-poly", "neon sci-fi", "match the existing lobby".
You do not need to know the Roblox API names. "When a player joins" is fine; RoGenie works out Players.PlayerAdded.
Quick starts
A new chat offers a few starting points, for example:
- Create a basic obby with checkpoints
- Write a DataStore saving system for player data
- Create an inventory system with GUI
- Make a combat system with sword and abilities
Big requests
You can ask for a whole game ("a tycoon with droppers, upgrades and rebirths"). RoGenie breaks it into a plan, and for independent parts it can run sub-agents in parallel. For anything large or risky in an existing place:
- Turn on Plan mode to review and approve the plan first.
- Write lasting conventions into project notes so every chat follows them.
Attach images and files
Click Attach, paste, or drag files onto the message box. Each file can be up to 10 MB.
- Images: PNG, JPEG, GIF, WebP, SVG and BMP. Use them for references: a UI mockup, a screenshot of a bug, concept art.
- Files:
.txt,.lua,.json,.py,.js,.ts,.css,.html,.xml,.csv,.md,.log, and Roblox files.rbxl,.rbxlx,.rbxm,.rbxmx.
Not every model can see images. If the model you picked cannot, RoGenie says so; switch to a model that can. A message with its files has an overall size limit; if you go over it, RoGenie tells you before sending so you can remove a file or shorten the text.
Follow up
When RoGenie finishes, check the result in Studio and reply with what to change: "make the checkpoints glow", "the shop button overlaps the health bar on mobile". It continues in the same chat with everything it already knows.
You can also send follow-ups while it is still working. See Stop, queue and steer.
Questions RoGenie asks you
Sometimes RoGenie pauses to ask a question, for example which of two layouts you prefer. It shows a card with options; pick one or type your own answer, and the run continues. You can turn this off with the Ask the User tool in Tool access.
When the result is not right
- Say what is wrong, specifically. "The door opens the wrong way" works better than "it's broken".
- Regenerate the last reply to try again. RoGenie offers to revert the Studio changes of the reply first.
- Try a stronger model or a higher effort for hard logic.
- Run a code review to catch security and quality problems in the scripts the chat wrote.