Limited time Limited time: 20% off every script
Docs/Getting started/Troubleshooting

Troubleshooting

Fixes for the issues we see most often — check here before opening a ticket.

The resource does not start

  • Confirm the folder name is unchanged and the resource sits in a folder your server.cfg ensures (for example resources/[venom]/).
  • Check the start order: ox_lib → your framework → your inventory → the Venom resource.
  • Look for escrow messages in the console — see Cfx.re asset escrow.
# server.cfg — recommended start order
ensure ox_lib
ensure es_extended        # or qb-core / qbx_core — skip on standalone
ensure ox_inventory       # only if the script uses items
ensure <venom-resource-folder>

The UI does not open

  • Make sure ox_lib is started before the script — the UI callbacks depend on it.
  • Press F8 and read the client console; copy the first red error into your ticket.
  • If you edited files in html/, revert them to confirm the stock UI works, then re-apply your changes one at a time.
  • After an update, clear the FiveM cache if the UI still shows the old version: %localappdata%\FiveM\FiveM.app\data\cache.

Framework not detected

Venom scripts auto-detect ESX, QBCore and Qbox on start. If the console prints framework: none:

  • Start the framework core before the Venom resource.
  • Renamed core resource? Set the framework explicitly in config.lua (see the script's Config page) or point the bridge at your resource name.
  • Standalone servers: select standalone in the config so the script stops waiting for a framework.

Items are not usable or not found

Scripts that use items ship an items list for ox_inventory and QBCore-style inventories. Add the items to your inventory's item file, restart the inventory, then restart the script. Item names must match exactly — they are case-sensitive.

Database errors

  • Scripts that persist data require oxmysql and a valid mysql_connection_string in server.cfg.
  • Tables are created automatically on first boot. If your database user lacks CREATE permission, import the included install.sql by hand.
  • Look for ER_ACCESS_DENIED_ERROR or ER_NO_SUCH_TABLE in the server console — both point at connection string or permission problems.

Performance

Open resmon in-game: idle usage should read 0.00ms. If a Venom resource shows sustained load, disable features you do not use (scheduled announcements, webhooks, leaderboards) and confirm no other resource is spamming its events.

Updating a script

  1. Back up your config, locales and any edited html files.
  2. Download the latest ZIP from Keymaster and replace the resource folder.
  3. Merge your changes into the new config — new options are called out in the changelog.
  4. Restart the server (not only the resource) after major updates.

Warning: Never copy an old config.lua over a new version blindly — new required keys will be missing and the script will fall back to defaults or refuse to start.

Still stuck? Open a ticket with

  • Server artifact version and framework (ESX, QBCore, Qbox or Standalone).
  • Script name and version (from fxmanifest.lua or Keymaster).
  • The first error from the server console and from the F8 client console.
  • What you changed in the config, and the steps to reproduce the problem.

Go to the support page →