Skip to content

FAQ / Troubleshooting

Here are the answers to the most frequently asked questions about using and installing the script.


The script does not start on my server, what should I do?

Section titled “The script does not start on my server, what should I do?”
  • Check that the script folder is placed in resources and that it is named intense_smoke_grenade.
  • Make sure you added ensure intense_smoke_grenade to the server.cfg file.
  • Check that OneSync is enabled on your server.
  • Check the server logs for any error messages.

The script says I have no bomb even though I have the item

Section titled “The script says I have no bomb even though I have the item”
  • The item name in your inventory must be identical to Config.Inventory.item in shared/config.lua (default: intense_smoke_grenade).
  • The item export in ox_inventory/data/items.lua must be intense_smoke_grenade.<item name>.
  • Restart ox_inventory then intense_smoke_grenade after any change.

No such export ... in resource ... error in the console

Section titled “No such export ... in resource ... error in the console”
  • The resource or item name in the ox_inventory export is wrong. It must be intense_smoke_grenade.intense_smoke_grenade (resource . item).

The bomb is invisible or a red Model not found message appears

Section titled “The bomb is invisible or a red Model not found message appears”
  • Check that the stream/ folder contains the 3 files intense_smoke_grenade.ydr, .ytd and .ytyp.
  • Fully restart the server and clear your FiveM client cache.
  • As a last resort, use the vanilla model prop_bomb_01 in Config.Prop.model.

  • Adjust Config.Prop.zOffset in shared/config.lua.

  • Yes, the script is 100% standalone: it works with ESX, QBCore, Qbox or without any framework. The ox_inventory integration is native, and the server exports let you integrate it with any other inventory.

  • Contact us via Discord, open a ticket if needed.