myRP.build docs

Pointing at Your Server

Point myRP.build at your server's resources/[local]/ folder, and learn how generated resources are named and loaded.

myRP.build writes resources directly into your FiveM server. To do that, it needs to know where your server lives.

Connect your server

In the app, point myRP.build at your FiveM server — it scans your machine for servers, or you can browse to the server folder (the one with your server.cfg). You can also have it scaffold a fresh server. Once connected, myRP.build writes every generated resource into that server's resources/[local]/ folder, and installs any ox resource a feature needs (with your approval).

your-fivem-server/      -- ◀ point myRP.build at your server
  ├─ server.cfg
  └─ resources/
      ├─ [ox]/          -- the ox stack — installed for you
      └─ [local]/       -- your generated resources land here
          ├─ carwash/
          └─ heal-command/

The [local] folder (a cfx.re resource group) is the conventional home for your own server-specific resources. myRP.build keeps all generations together there.

The app must be able to read and write this path. If your server runs in a container or on another box, map the resources folder to a local path first.

How resources are named

Generated resources use lowercase-hyphenated names derived from your prompt:

Prompt ideaResource folder
A carwash zonecarwash
A /heal commandheal-command
Player-owned ATMsplayer-atms

This matches cfx.re resource-naming conventions and keeps ensure lines predictable.

How resources are loaded

You never edit server.cfg by hand. When a generation completes, myRP.build writes the folder into [local]/ and ensures it is loaded on your server. The resource is ready to test in-game without any manual config changes.

If something doesn't appear, see Troubleshooting.

On this page