RedEM:RP

RedEM:RP is one of the longer-running RedM frameworks. It is stable and well understood, though newer scripts across the community increasingly target VORP or RSG Core first.

Identifying it

Every core resource carries the redemrp_ prefix:

• redemrp_identity — character identity and creation
• redemrp_inventory — items and storage
• redemrp_status — hunger, thirst and other needs
• redemrp_progressbars — shared progress UI that many jobs call

If your resources folder is full of redemrp_* folders, this is your framework.

Load order

ensure oxmysql

ensure redemrp_identity
ensure redemrp_inventory
ensure redemrp_status
ensure redemrp_progressbars

# RedMorrow resources after the framework
ensure redemrp_moonshine_job
ensure redmrp_backpack

The identity resource must come first — it owns the player object everything else reads from.

Database

Older RedEM:RP deployments were built against mysql-async or ghmattimysql. Many current scripts assume oxmysql instead.

If you are running an older server and installing a recent script, check which database layer the script expects before anything else — a script calling exports.oxmysql on a server that only has ghmattimysql will fail immediately and confusingly.

Running both simultaneously is possible but not recommended; standardise on oxmysql if you can.

Replacing a core module

Swapping out a stock module — inventory, status, progressbars — is more invasive than adding a script. Take a database backup first, and expect to update any script that called the old module directly.

Common RedEM:RP problems

Player object is nil — redemrp_identity has not finished loading, or is below the script in server.cfg. Move it up.

Items exist in the script but not in game — the item must be registered in the inventory module's item list or database table. Import the script's .sql, and confirm the item names match the config exactly, including case.

A script expects a function that does not exist — RedEM:RP has forks and community variants in circulation, and they do not all expose the same helpers. Confirm which variant you run before assuming the script is broken.

Verify against your build

Because RedEM:RP exists in several community variants, exact event and export names vary more than they do on VORP. Always check the script's README against the specific build you run.

Should you migrate?

If you are running a mature RedEM:RP server, there is no urgent reason to move. If you are starting fresh, VORP has broader current script coverage across the RedM community.