First Generation

This is the core loop: describe a feature, and myRP.build writes a complete ox_overextended resource to your server.

Write your first prompt

Describe what you want in plain English. Be specific about the behavior — locations, prices, items, and commands all help.

Add a /heal command that fully restores the player's health
and armor, with a 5-minute cooldown per player.

Good prompts name the what and the rules. The app fills in the ox-native plumbing.

What gets generated

myRP.build produces a complete, self-contained resource. For the /heal example:

resources/[local]/heal-command/
  ├─ fxmanifest.lua    -- fx_version 'cerulean', ox dependencies, file list
  ├─ config.lua        -- cooldown duration, command name
  └─ server.lua        -- registered command, server-side cooldown + heal

Every file follows real ox conventions:

• fxmanifest.lua declares fx_version 'cerulean' and the ox dependencies it actually uses.
• Authoritative logic (the cooldown, the heal) lives on the server — clients can't bypass it.
• ox_lib callbacks and notifications are used where appropriate.

How it deploys and loads

You don't touch server.cfg. When generation finishes, myRP.build:

1. Writes the resource folder into resources/[local]/<name>/.
2. Ensures the resource is loaded (the app handles the loading for you).
3. Reports success in the app so you can test in-game.

A worked example: carwash

Prompt:

A carwash zone at the Sandy Shores garage. The player presses the
ox_target option on a marker, pays $50 from their bank, and their
current vehicle is cleaned.

Generated layout:

resources/[local]/carwash/
  ├─ fxmanifest.lua
  ├─ config.lua    -- zone coords, price ($50)
  ├─ client.lua    -- ox_target zone, vehicle wash effect
  └─ server.lua    -- charges the player via ox_core/oxmysql, validates funds

The payment is validated server-side — the client only requests the wash, never deducts money itself.

Next: make sure the app is pointed at the right server folder.