RedM Reports Troubleshooting

The resource won't start, or ensure can't find it

The folder is pc_report but the manifest name is pc_reports. ensure uses the folder name:

ensure pc_report

Rename the folder to pc_reports if you want them to match — but remember exports follow the folder name too, so anything you have written against exports.pc_report changes with it.

Staff aren't detected — no dashboard, no tools

Work through these in order:

1. Confirm the framework. The console prints Framework bridge: <name> on start. Force it if wrong:

   Config.Framework.force = 'vorp'

2. VORP — the player's user group (not character group) must be a staff group in bridge/vorp.lua.
3. RSG — they need god / admin / mod, or an ACE (pc_reports.*).
4. RedEM / Standalone — grant the ACEs in install/permissions.cfg, and exec that file from server.cfg.
5. After changing any group or ACE while the player is online, run:

   /refresh_report_permissions

"Framework bridge: standalone" but I'm on VORP or RSG

Your framework resource started after this one, or its folder name differs from what the config expects.

• Move the framework above pc_report in server.cfg
• Set Config.Framework.resourceNames if your core folder is named differently

Screenshots don't work

• Install the RedM fork of screenshot-basic — the FiveM build will not work.
• ensure it before this resource.
• Set Config.Media.Webhook.url to a valid Discord webhook.
• Media auto-disables with no errors if screenshot-basic is not started or the URL is empty. That silence is why this is easy to miss.

There is no video on RedM

Bursts are rapid screenshots, by design. This is a platform limitation.

Discord webhooks aren't sending

• Replace the placeholder URLs in server/webhook.lua and Config.Media.Webhook.url — they are separate.
• server/webhook.lua must load before server/server.lua (the default order in fxmanifest.lua) because it defines DispatchHook.
• Check outbound HTTPS is not blocked on your host.

attempt to index a nil value (field 'Locale') on start

You are on an old build. Update — Config.LocaleUI must be a top-level key, which was fixed in the current version.

Reports don't persist after restart

Config.Database = { enabled = true, tableChecker = true }

oxmysql must be running and started before this resource. With tableChecker = true the tables build automatically; otherwise import install/schema.sql.

"You must wait before creating another report"

That is the anti-spam cooldown:

Config.Cooldown = { Seconds = 60 }  -- 0 = off

Spectate won't stop, or I can't rebind the key

Press Backspace, or type /pcr_stop_spectate.

RedM does not expose rebindable keymaps here. To remap, change the hashes at the top of client/client.lua — SPECTATE_STOP_KEY, PREV, NEXT.

Auto-assign isn't assigning

• Config.AutoAssign.Enabled must be true.
• With Config.Duty.Enabled = true, at least one staff member must be on duty (/reportduty).

This is the most common "alerts are broken" report, and it is working as designed.

Anonymous reports still show the name somewhere

Update to the current build. Name and server ID are masked in the queue, webhook, chat and typing indicator. The license is kept server-side only.

Priorities, categories or forms don't show my changes

config.lua is a shared script. Restart the resource:

restart pc_report

Re-opening the menu on the client is not enough for config changes.

RSG / RedEM specifics

Those adapters ship with sensible defaults but were not tested against a live core. If staff detection is off, edit the permission maps at the top of bridge/rsg.lua or bridge/redp.lua.

The UI is stale after an update

RedM caches NUI assets:

1. restart pc_report
2. Have players fully reconnect
3. If it persists for one player, they clear %localappdata%\RedM\RedM.app\data\cache — note RedM.app, not FiveM.app

Still stuck?

Set Config.Debug = true, reproduce the problem, and check the server console for [PlayCraft Reports] lines.

Then open a ticket in Discord with that output, plus:

1. Your framework and version, and the Framework bridge: line from your console
2. Your RedM artifact build
3. The full server console output around the failure
4. The F8 client error, if there is one

Redact your server.cfg credentials and any webhook URLs first.