FiveM Pepperspray Script

Adds a job-restricted pepper spray addon weapon to FiveM with configurable cone, range, paralysis duration, and gas mask immunity. ESX, QBCore, Qbox. Under 0.03ms at peak.

5.0 (2 reviews)
esx qbcore qbox
$15.00
Secure checkout by Tebex Digital delivery after checkout Tebex Your Game Studio, Extended.
Overview
Reviews 2

Tasers handle one escalation level. Pepper spray handles another — the non-lethal option that keeps a suspect upright but buying time for cuffs. This script adds weapon_pepperspray as a real addon weapon, not a re-skin. It registers hit detection on actual player contacts, applies a configurable paralysis effect, and locks usage behind a job check so civilians can't pick it up and run wild.

How the Effect Works

When a sprayed player takes a hit inside the configured cone and range, the paralysis kicks in for a set duration. The intensity, duration, range, and spray angle are all config values, so a roleplay-light server can keep it subtle while a heavier simulation server can make it genuinely incapacitating. Players with a compatible gas mask (via skinchanger immunity flag) are immune — meaning the gear system you already have actually matters in confrontations.

  • Addon weapon registered as weapon_pepperspray — functions like any native weapon
  • Hit detection on real player contacts within a configurable cone and range
  • Configurable paralysis duration, intensity, and spray angle
  • Job check for ESX and QBCore — restrict to police or any custom job
  • Skinchanger-compatible immunity for gas mask items
  • Bridge functions exposed for encrypted version — hook into your own events without editing core files
  • Performance: 0.00ms idle / 0.03ms maximum when actively used

Framework & Compatibility Notes

Runs standalone with ESX, QBCore, and Qbox job-check bridges pre-built. Note: CodeM-Inventory has a known conflict — all other major inventory setups are unaffected.

Where It Fits on Your Server

Pepper spray fills the force-escalation gap between verbal commands and a taser. It gives officers a tool that works on foot pursuits and close-quarters situations where a taser would be overkill — and it costs almost nothing in resmon. At 0.03ms peak, the entire resource uses less CPU than most notification libraries sitting idle. If your server takes police interactions seriously, this is a logical addition to any LEO loadout.

Installation plan

Set up FiveM Pepperspray Script safely

Use the documentation included with the download as the final authority. This plan helps you prepare a rollback, install in the right order, and verify the resource before it reaches players.

Resource type
FiveM script
Compatibility shown
ESX QBCore Qbox
Catalog category
ESX Scripts
Package source
Shop Tebex
  1. Audit the package and requirements

    Open the supplied documentation before moving files or changing the database. Build the install order from the package, not from assumptions.

    • Identify the actual resource folder, required dependencies, and supported framework version.
    • Locate any SQL, configuration examples, permissions, or optional integrations.
    • Check whether the documentation requires a specific start order.

    Ready when Every dependency and required file has a place in your install plan.

  2. Create a rollback point

    Prepare the server so the change can be reversed cleanly if the resource conflicts with your current stack.

    • Keep an untouched copy of the downloaded package.
    • Back up the database and every configuration file you will edit.
    • Use a test server or schedule a maintenance window before changing production.

    Ready when You can restore the previous database, files, and configuration.

  3. Install in the documented order

    Apply only the changes supplied for this resource, keeping dependency and startup order intact.

    • Place the resource folder where your server loads resources, without renaming it unless instructed.
    • Install dependencies first, then import included SQL once and review configuration values.
    • Add the documented resource name to the server startup configuration after its dependencies.

    Ready when The resource starts without missing files, exports, tables, or dependencies.

  4. Verify the complete player flow

    Restart the test server, watch both server and client consoles, and exercise the resource before opening it to players.

    • Test the main workflow with an authorized player and a player without permission.
    • Reconnect and restart once to confirm saved state and startup behavior.
    • Review console output again before promoting the same configuration to production.

    Complete when The intended flow works twice with no new console errors.

Support reference Use the exact listing name when you contact support.
FiveM Pepperspray Script Contact support

FiveM Pepperspray Script compatibility and specs

Frameworks
ESX · QBCore · Qbox
Category
Delivery
After checkout — order download link
Product terms
See product details — terms vary by resource
5.0
2 reviews
5★
100%
4★
0%
3★
0%
2★
0%
1★
0%
S
ScriptsYeeet94 VERIFIED
Land RP

Bought this right after launch since I use a few of their other resources on my QBCore server. Opened a quick ticket because I had a question on setting up the gas mask item immunity in the config, got an answer in literally five minutes with the exact line to edit. Script works great in game and resmon stays flat at 0.00ms idle. LEOs are already using it.

b
big_mo76 VERIFIED
Alpha Designer

My lead dev told me to grab this for our qbcore city ... plugged right into ox_inventory without any issues.

Write a review

Reviews are moderated before appearing. Purchased the product? Your review gets a VERIFIED badge automatically.

20 chars minimum
[ You might also like ]

Related scripts

About this FiveM script

FiveM Pepperspray Script is a FiveM resource for esx, qbcore, qbox servers. Review the product details, requirements, and compatibility notes before ordering.

Use the included files and documentation as the source of truth for installation, configuration, dependencies, and any stated performance information.