WNT GSRW | Interactive GSR & Fingerprint Reader | ESX / QBCore / Qbox

WNT GSRW is an interactive Gunshot Residue (GSR) and fingerprint reader designed for police and law-enforcement roleplay.

Instead of handling GSR checks through a simple command or instant notification, GSRW turns the process into an interaction between the officer and the person being tested.

An officer uses the handheld reader on a nearby player. The target is presented with the fingerprint scanner interface and must hold their finger on the scanning plate while the device processes the sample. Once the scan is completed, the officer receives the final GSR Positive or GSR Negative result through the reader interface.

The system tracks gunshot residue after weapon use and can keep a player positive until the residue is properly removed, allowing GSR checks to become part of investigations, traffic stops, arrests and other police RP situations.

Preview:

Video Preview:
Youtube

Purchase:
TEBEX

How It Works

When a player fires a weapon, GSRW can mark that character as GSR positive.

Later, an authorized officer can use the GSR reader while standing near the player.

The process is interactive:

1. The officer starts the GSR test

The reader searches for a nearby player within the configured distance.

2. The suspect receives the fingerprint scanner

The tested player sees the fingerprint interface and is instructed to hold left click on the scanning plate.

3. The fingerprint sample is processed

The player must continue holding the scanner for the configured scan duration. The test can be cancelled or expire if it is not completed.

4. The officer receives the result

After the fingerprint scan is completed, the officer’s reader displays either:

GSR POSITIVE
Gunshot residue particles were detected.

or

GSR NEGATIVE
No gunshot residue was detected.

The reader can also display character identity information obtained from the selected framework, including the character’s first name, last name and available nationality/country information.

Gunshot Residue System

GSRW includes its own gunshot residue tracking.

When a player fires a weapon, the system can register them as GSR positive.

You can configure whether GSR remains positive until cleaned or use a duration-based setup.

With the default configuration:

Config.GSR.PositiveOnceUntilClean = true
Config.GSR.PositiveDuration = 0

the residue remains until the player successfully cleans it.

Certain weapons can also be excluded from GSR detection.

The default ignored weapons include:

WEAPON_UNARMED
WEAPON_STUNGUN
WEAPON_FIREEXTINGUISHER
WEAPON_PETROLCAN

Law-enforcement jobs can additionally be excluded from normal GSR application while on duty.

This is useful for preventing officers from constantly becoming GSR positive during normal police activity.

Water Cleaning

Players can remove gunshot residue through the built-in water cleaning system.

When enabled, entering water starts the configured cleaning process.

By default, the player must remain in the water until the cleaning process has finished. Leaving the water before completion prevents the GSR from being removed.

Example configuration:

Config.WaterCleaning.Enabled = true
Config.WaterCleaning.Duration = 10000
Config.WaterCleaning.RequireStayInWater = true

The cleaning duration, progress text, cancellation behavior and controls can all be configured.

Fingerprint Reader UI

GSRW includes a custom NUI designed around a portable forensic reader.

The interface has separate states for both participants.

Officer

While the suspect is providing the sample, the officer sees that the sample is pending.

After the scan finishes, the reader displays the final positive or negative result.

Suspect

The suspect receives the fingerprint scanning screen and must hold left click over the scan plate until the sample is completed.

The interface includes configurable:

• Department header

• Agency name

• Device name

• Device serial

• Accent color

• Positive result color

• Negative result color

• Panel colors

• Alarm

• Alarm volume

• UI labels and text

This allows the reader to be adapted to the visual identity of your server or police department.

Character Information

The reader obtains identity information directly from the configured framework.

QBCore / Qbox

GSRW uses available character information such as:

charinfo.firstname
charinfo.lastname
charinfo.nationality

ESX

The resource uses the available ESX identity name information and can use nationality or country metadata when available.

Framework Support

GSRW supports:

• QBCore

• Qbox

• ESX

The framework is selected directly from config.lua.

Example:

Config.Framework = {
    Name = 'qbcore',
    CoreObject = 'qb-core',
    QboxObject = 'qbx_core',
    ESXObject = 'es_extended',
    UseFrameworkNotify = true
}

You do not need separate versions of the resource for each supported framework.

Item & Command Usage

The reader can be used as an inventory item.

Default item:

Config.Item = {
    Enabled = true,
    Name = 'gsrw'
}

A command-based option is also included and can be enabled from the configuration.

Config.Command.Enabled = false
Config.Command.Name = 'gsrw'
Config.Command.AdminOnly = true

This allows server owners to use the physical inventory item for normal gameplay while optionally keeping command access available for administrators.

Job Restrictions

Access to the reader can be restricted by job.

Default configuration:

Config.Access.EnableJobCheck = true

Config.Access.AllowedJobs = {
    police = true,
    sheriff = true
}

Additional jobs can be added or the restriction can be disabled depending on your server setup.

Configurable Scan System

Server owners can configure the interaction itself, including:

Config.Scan.MaxDistance = 2.0
Config.Scan.HoldDuration = 4500
Config.Scan.RequestTimeout = 30000
Config.Scan.AllowSelfScan = false
Config.Scan.ServerDistanceCheck = false

This gives control over:

• Maximum testing distance

• Fingerprint hold duration

• Request timeout

• Self scanning

• Server-side distance verification

• NUI focus behavior

Device Animation & Prop

GSRW includes configurable officer animation support.

The resource can also use a handheld prop if enabled.

Example:

Config.DeviceProp.Enabled = true
Config.DeviceProp.AnimationEnabled = true
Config.DeviceProp.PropEnabled = false

The animation dictionary, animation name, bone, model, offset and rotation are configurable.

Languages

GSRW currently includes:

English
Spanish
Turkish
French

Language can be selected with:

Config.Locale = 'en'

The locale system covers the reader interface, notifications, command help and water-cleaning text.

Main Features

• Interactive handheld GSR reader

• Player-to-player fingerprint scanning

• Hold-to-scan fingerprint interaction

• GSR positive / negative results

• Automatic gunshot residue detection

• Persistent GSR until cleaning

• Optional duration-based GSR

• Water-based GSR cleaning

• Character identity information

• Job-restricted access

• On-duty law-enforcement exemptions

• Item-based usage

• Optional admin command

• Configurable scan distance and duration

• Configurable device animations

• Optional handheld prop

• Customizable reader NUI

• Configurable alarm and UI theme

• English, Spanish, Turkish and French locales

• ESX support

• QBCore support

• Qbox support

• Client export for custom integrations

Export

The reader can also be opened from another resource:

exports['wnt-gsrw']:UseReader()

This can be used to integrate GSRW with another inventory, police system or custom interaction.

Installation

1. Place wnt-gsrw inside your server resources.

2. Make sure your framework and inventory are started before GSRW.

3. Add:

ensure wnt-gsrw

to your server.cfg.

4. Select your framework inside config.lua.

5. Add the gsrw item to your inventory.

6. Copy the included gsr.png item image to your inventory’s image directory when required.

Item examples for QBCore/QB Inventory, Qbox/Ox Inventory and ESX are included with the resource documentation.

Configuration

The accessible configuration allows server owners to modify the main behavior of the resource, including:

• Framework

• Locale

• Item name

• Command access

• Admin groups

• Allowed jobs

• Scan distance

• Scan duration

• Request timeout

• Self scanning

• GSR behavior

• Ignored weapons

• On-duty job exemptions

• Water cleaning

• Device animation

• Device prop

• Department information

• Reader labels

• UI colors

• Alarm behavior

• Notifications

• Locale text

Required Information

WNT Development