Writing Good Prompts
How to describe a feature so myRP.build builds exactly what you mean — patterns, examples, and the mistakes to avoid.
The prompt is the product. myRP.build turns your description into a complete ox_overextended resource, so the more precisely you describe the behavior, the closer the result is on the first try.
The pattern: name the what and the rules
Every good prompt answers two things:
- What — the feature (a command, a shop, a job, a zone interaction).
- The rules — the specifics that make it yours: locations, prices, items, commands, cooldowns, permissions, limits.
You don't need to mention ox_core, server-side validation, or fxmanifest — the app handles all the ox-native plumbing and keeps authoritative logic on the server automatically.
Specific beats vague
| Vague (generic result) | Specific (what you actually want) |
|---|---|
| "Make a shop" | "A 24/7 shop at Legion Square. Sells water $5, sandwich $8, phone $250. Pays from the player's cash." |
| "Add a robbery" | "Let players rob the Fleeca bank with a lockpick item. 90-second hack, $5,000–$10,000 to the bank account, 30-minute cooldown per player." |
| "A car thing" | "An /engine command that toggles the engine of the vehicle the player is sitting in." |
Examples by feature type
Command
An /armor command that gives the player full armor, costs $500
from their bank, with a 10-minute cooldown.
Job
A garbage collector job. Players sign on at the depot, drive to
marked bins, press the ox_target option to collect, and get paid
$25 per bin emptied at the dump.
Shop / economy
A gun store at the Ammu-Nation in Sandy Shores. Sells a pistol
for $2,500 and ammo for $50, paid from the bank, with a
"you need a weapon license" check.
Zone interaction
A carwash at the Sandy Shores garage. Press the ox_target option
on a marker, pay $50 from the bank, and the current vehicle is
cleaned.
Vehicle / garage
A garage at the airport where players store and retrieve their
owned vehicles using an ox_lib menu.Tips
- One feature per prompt. Build a shop, then build the robbery — don't ask for both at once. You can keep going in the same conversation.
- Say where money comes from — cash vs bank — when a feature charges or pays.
- Name your items. If a feature uses an item (a lockpick, a repair kit), say so. Note that custom items aren't auto-registered in ox_inventory — see Database & Items.
- Don't over-specify the code. You describe behavior; the app decides the ox-native implementation.
When the result isn't quite right, you refine it — see Iterating on a resource.