Overview

myRP.build is a Windows desktop app that turns a plain-English description into a complete, production-ready ox_overextended FiveM resource — written straight into your server's resources/[local]/ folder and loaded for you.

No copy-paste. No boilerplate. No wrong framework.

How it works

You describe what you want in a sentence. myRP.build generates the entire resource — manifest, server logic, client logic, shared config, and SQL when the feature needs it — following real ox_overextended conventions, then writes it directly to your server and loads it.

"a carwash at the Sandy Shores garage that charges $50"
        │
        ▼
  myRP.build
        │
        ▼
resources/[local]/carwash/
  ├─ fxmanifest.lua
  ├─ config.lua
  ├─ client.lua
  └─ server.lua

ox_overextended only

myRP.build targets the Overextended ecosystem exclusively. There is no ESX or QBCore support — by design. Every generation is built against:

• ox_core — player, character, and account data
• ox_lib — UI, callbacks, zones, and shared utilities
• ox_inventory — items and stashes
• ox_target — interaction targeting
• oxmysql — database access

Generated resources use fx_version 'cerulean' and keep all authoritative logic on the server.

What you need

myRP.build installs the ox stack for you — you don't set up ox_core, ox_lib, ox_inventory, ox_target, or oxmysql by hand. What you bring is a server for it to build on:

• Windows 10/11 (64-bit) to run the desktop app.
• A FiveM server (FXServer) — point the app at one you already run, or have it scaffold a fresh server folder. myRP.build installs the ox_overextended stack onto it for you. The server's folder needs to be reachable on the same machine (or a mapped path).
• A MySQL/MariaDB database for that server, with the connection string and your cfx.re license key set in server.cfg — the same database your FiveM server uses.

Next steps

• Install myRP.build and launch it for the first time.
• Generate your first resource.
• Download the app.