Install Your First Script

Almost every RedMorrow script installs the same way. Learn this once and it applies to the whole catalog.

Before you start

You need:

• A running RedM server (see Server Basics)
• To know which framework you run — see Which one am I on?
• Access to your server files and server.cfg
• Database access, if the script ships a .sql file

Check the framework first

A VORP script will not run on RSG Core, and an RSG script will not run on RedEM:RP. Every product page lists the frameworks it supports — check it against your server. Installing a mismatched script is the number one cause of attempt to index a nil value on first boot.

1. Download and extract

Download the archive from your Tebex order. Extract it somewhere local first — never extract straight into a live resources folder.

You should end up with a folder containing at minimum an fxmanifest.lua. If you see a nested folder (script-name/script-name/fxmanifest.lua), use the inner one.

2. Name the folder correctly

The folder name becomes the resource name. Two rules:

• If the script's README specifies an exact name, use it exactly. Scripts that ship a NUI interface often hardcode their own name in asset paths, and renaming breaks the UI.
• Otherwise, avoid spaces, capitals and special characters. redm_shops is safe; RedM Shops v2 (final) is not.

3. Drop it into resources

Group your purchases in a category folder so they are easy to find:

resources/
├── [redmorrow]/
│   ├── redm_shops/
│   ├── vorp_phone/
│   └── redm_animation_menu/
├── [vorp]/
└── [standalone]/

Any folder in [brackets] is a category — it is not a resource itself, but everything inside is discovered automatically. Category folders cannot be nested more than one level deep.

4. Import the SQL

If the download contains a .sql file, import it into your server's database before first start. Use phpMyAdmin, HeidiSQL or the MySQL CLI. Full walkthrough: Database & SQL.

Skipping this step produces a resource that starts cleanly and then fails the moment a player interacts with it.

5. Add it to server.cfg

ensure redm_shops

Order matters. Your database resource and your framework must come first:

ensure oxmysql
ensure vorp_core
ensure vorp_inventory

# RedMorrow resources after the framework
ensure redm_shops

See Server Basics → Load order for the full rule.

6. Start and verify

Restart the server and watch the console as it boots. You are looking for:

• The resource name appearing in the start list without a red error
• No Failed to load resource or could not find dependency lines
• No attempt to index a nil value during startup

Then join and test the actual feature — a resource that starts is not the same as a resource that works.

Faster iteration

While tuning a config you do not need a full restart:

restart redm_shops

Run it in the server console (txAdmin's live console works). If you added or renamed files, run refresh first so the server re-reads the manifest.

When it does not work

Copy the full error from the server console — not a screenshot of one line — and check Common Issues. Most first-install failures are one of four things: wrong framework, wrong load order, missing SQL import, or a manifest problem.