Common Issues

The problems that come up most often, across every RedMorrow resource. Check the script's own README too — it is the authority on anything specific to that resource.

The resource will not start

Work through these in order:

• Not ensured — confirm ensure <resource> is actually in server.cfg, and that you saved the file.
• Wrong folder name — the folder name is the resource name. If you renamed the folder, your ensure line no longer matches.
• Nested folder — check for script/script/fxmanifest.lua. The server only finds the manifest one level down from a category folder.
• Missing dependency — look for could not find dependency in the console. It names exactly what is missing.
• Not refreshed — after adding a new folder, run refresh before ensure, or restart the server.

rdr3_warning errors on start

Creating script environments for <resource> failed: rdr3_warning is missing

Every RedM resource manifest must declare game 'rdr3' and include the rdr3_warning acknowledgement line, verbatim. A resource missing it will not start.

This usually means the resource was written for FiveM, or the manifest was edited and the line was dropped. The exact required text and a full working manifest are in The RedM fxmanifest.

attempt to index a nil value

Nearly always framework related. In order of likelihood:

1. Load order — your framework starts after the script. Move vorp_core (or rsg-core, or your core) above the script in server.cfg.
2. Wrong framework — you installed a VORP script on RSG Core, or similar. Check the frameworks listed on the product page against what you actually run.
3. Framework not running at all — confirm the core resource actually started, without its own errors, earlier in the console.
4. Version mismatch — the script targets an older or newer core than you run. The export it calls no longer exists under that name.

The console line above the error usually names the file and line number. That tells you which resource is at fault, even when the error text does not.

The UI does not appear

• Clear the client cache — %localappdata%\RedM\RedM.app\data\cache, then reconnect. Note it is RedM.app, not FiveM.app.
• Check the NUI console — press F8 in game and look for red errors from the resource.
• Check the manifest — every HTML, CSS, JS, image and font file the UI loads must be listed under files in fxmanifest.lua, with ui_page pointing at the entry HTML. Assets not declared there are never served.
• Did you rename the folder? — scripts with a NUI often reference their own resource name in asset paths. Rename it back to what the README specified.

The UI still looks old after an update

RedM caches NUI assets aggressively. After updating a resource:

1. restart <resource> on the server.
2. Have players fully reconnect.
3. If it persists for a specific player, they clear %localappdata%\RedM\RedM.app\data\cache.

Database errors

• oxmysql not started, or started too late — it must be ensured before the framework and before any script that queries.
• SQL never imported — if the download shipped a .sql file, import it. See Database & SQL.
• Bad connection string — check set mysql_connection_string in server.cfg. Wrong password, wrong database name and wrong host all surface as connection errors at boot.
• Table already exists — harmless on re-import. It means that part was already installed.
• Unknown column — the resource was updated and expects a new column. Re-import the current .sql, or add the column manually.

A streamed map or prop does not appear in game

Streamed content fails differently from scripts — the resource starts fine, reports no error, and simply nothing is there. Check, in order:

• The manifest declares this_is_a_map 'yes' — see Map resources.
• Every asset is inside a stream/ folder, not loose in the resource root.
• The client cache was cleared and the player fully reconnected.
• No second resource is replacing the same location. Two resources fighting over one interior produces flickering geometry, and which one wins can change between restarts.

Everything worked yesterday and now nothing starts

Check whether the server updated its artifacts. A new artifact build occasionally changes manifest or native behaviour. Roll back to the previous artifact version to confirm, then report it so the script can be updated.

Before you open a ticket

Collect all of this:

1. The full console output around the failure — not one cropped line.
2. Your framework and its version.
3. The resource name and the version you downloaded.
4. Your RedM artifact build number.
5. What you already tried from this page.

Then head to Support.