Notify

One notification style for every script on your server — without rewriting a single one of them.

QBCOREESXQBOX OX_LIBSTANDALONE

FREE No account. No key. No license check.

INSTALLATION GUIDE

Delivered to your Cfx.re account. Already got it? Open your assets

One line in your framework core. Nothing else changes.

0.00 ms idle. No tick loops, ever.

Players set their own scale, position and sound in game.

Turn interception off and your original notifications come back.

Reports its own install state in the console — no guessing.

THE PART NOBODY ELSE HAS

A notification script is easy.
Surviving other people's code is not.

Anything can draw a box on screen. What breaks a server is the fifth resource firing the same message in a loop while the third one sends a type that does not exist. Three gates sit between your scripts and the player's screen.

GATE 01

Duplicate suppression

Two resources reacting to the same event send the same message twice. Anything identical inside 750 ms is dropped, and a repeat later collapses into the card already on screen as a counter — never a second card.

GATE 02

Rate limiting, per resource

Repeats collapse, but a resource sending thirty different messages cannot be deduplicated. After 12 in 2 seconds that one resource goes into slow mode — on its own, while every other script keeps working normally.

GATE 03

Nothing is ever malformed

Twenty-plus type aliases are normalised, an unknown type falls back to info instead of failing, and duration is clamped to 500–30000 ms. A badly written script cannot produce a broken notification.

AND THE PLAYER

Their screen, their rules

Players open /notify and set scale, corner, sound and manual dismiss for themselves — saved locally, kept through reconnects. Anything important can wait for a Y or N instead of timing out while they were driving.

HONEST COMPARISON

Against a typical paid notify script

The common feature set is genuinely good and most stores ship it. These are the rows where the approach differs — and the reason this one is free.

CAPABILITY	TYPICAL $6 SCRIPT	NOTIFY
Types, colours, sound, progress bar	Yes	Yes
In-game scale, position, sound, persistence	Yes	Yes
Works on QBCore, ESX, QBox, standalone	Yes	Yes
Intercepts the calls your scripts already make	You replace them by hand	One line
Interception can be switched off, original returns	—	Yes
Duplicate suppression	—	750 ms
Rate limiting per resource	—	12 / 2 s
Duration clamping	—	500–30000 ms
Type alias normalisation	—	20+
ESX advanced notifications	—	Yes
Install self-test in the console	—	Yes
Idle cost	0.01 ms	0.00 ms
Price	$6.00	Free

Figures for the comparison column are taken from a publicly listed competitor's own store page. We are not naming it — the point is the shape of the difference, not the shop.

WHAT LANDS IN YOUR RESOURCES FOLDER

Open where it counts. Locked where it matters.

dispersia_notify

select a file

open — yours to edit escrow protected ships as built

No dependency folders. No shared library to install first, no version of a bridge to keep in sync. If it starts, it works.

Everything meaningful is in game. The config file holds colours and the command name — four settings. Everything else is set from a panel in game, not a file.

Open where it matters. The config file and the whole NUI folder — HTML, stylesheet, fonts — ship readable. Restyle it to match your server without touching a line of logic.

Reversible. Delete the one line from your core and every original notification comes back exactly as it was.

A notification script is easy.Surviving other people's code is not.