DISPERSIA INC

DISPERSIA

STUDIO
FIVEM INFRASTRUCTURE · QB · ESX · QBOX

Scripts for servers that outgrew free resources. Every framework supported out of the box. Zero dependencies. 0.00 ms idle.

EXPLORE SCRIPTS
QB · ESX · QBOX
DETECTED AUTOMATICALLY
0.00 MS
IDLE COST
ZERO
DEPENDENCIES
LIFETIME
UPDATES INCLUDED
SCROLL
THE CATALOGUE

Infrastructure your server
actually notices

Each script solves one problem completely. No bundled bloat, no dependency chains, no framework lock-in — every resource detects QB, ESX, QBox and standalone on its own.

BROWSE ALL SCRIPTS
FREE FOREVER

Notify

Your server runs scripts written for three different frameworks, so players see three different notification styles. One line in your core routes all of them through one design — duplicates suppressed, runaway loops rate-limited.

QBCOREESXQBOXOX_LIBSTANDALONE
FREENO ACCOUNT NEEDED
TRY IT LIVE
FREE FOREVER

Interactions

Third-eye targeting that stays out of the way. Zero ticks when nothing is in range, so it costs nothing while your players are simply driving around.

QBCOREESXQBOXSTANDALONE
FREENO ACCOUNT NEEDED
FLAGSHIP

HUD

Most HUDs redraw every frame whether anything changed or not. This one renders only when a value actually moves, and every element is positioned by the player in game — no config file, no restart.

QBCOREESXQBOXSTANDALONE
$29LIFETIME UPDATES
IN TESTING

Chat

Default chat has not changed since 2019. Channels, proximity, staff visibility and a readable log — without replacing anything your existing commands already do.

QBCOREESXQBOXSTANDALONE
$18LIFETIME UPDATES
COMING SOON

Multicharacter

The first thing every player sees. Cinematic camera, character slots, spawn flow — drop-in compatible with the multichar you already have.

QBCOREESXQBOX
$34LIFETIME UPDATES
COMING SOON

Visuals

Weather, timecycle and post-processing tuned for roleplay screenshots — configured live in game while you look at the result.

STANDALONE
$19LIFETIME UPDATES
FREE, AND STAYING FREE

Two scripts cost nothing.
Not a trial. Not a lite build.

The free resources are the complete versions — every feature, every framework, lifetime updates. No account, no key, no license check phoning home.

We would rather you judge the engineering on a server you already run than on a screenshot. If the free ones hold up, the paid ones are built the same way by the same person.

NotifyOne notification style for every framework
FREE
InteractionsThird-eye targeting that costs nothing at idle
SOON
dispersia_libShared settings hub — optional, never required
FREE
WHY DISPERSIA

Built by someone who started out
fixing other people's scripts

I was the person who found the bugs nobody else reported.

Since late 2023 I have been inside FiveM — not as a player, but pulling scripts apart to understand how they work. When something was broken I tracked it down, wrote it up and sent it to the author. Reproduction steps, code snippets, suggested fixes. Unpaid, because the standard mattered more than the credit. That work went into the MenanAK47 team and into RCore, RTX, VVS, Pug, 17mov, Delta District, rytrak, Retry Studio and the qb-core community.

0.00 ms at idle No tick loops. The UI renders when there is something to show and costs nothing the rest of the time. Verified on camera in every trailer, not claimed in a bullet point.
Every framework, no bridge resource QBCore, ESX, QBox and standalone are detected at runtime. There is nothing extra to install first and nothing to keep updated afterwards.
Configured in game, not in files Server owners change behaviour from a panel; players change their own preferences and keep them. Config files hold product settings only. It is 2026 — nobody should restart a server to move a UI element.
Tested on a live server before release Every script runs on a real roleplay server with real players before it reaches the store. We publish v2 — v1 is what the players already broke for us.
Documentation that installs it for you Step-by-step, per framework, per operating system, with the exact line you need and a tool that patches your core file in the browser. Written for someone who has never opened a Lua file.
BEFORE YOU BUY

Questions worth answering honestly

01Which frameworks are supported?
QBCore, ESX, QBox and standalone. Detection happens at runtime — there is no bridge resource to install and no setting to pick. A server running a mix of all three still gets one consistent result.
02Do I get updates after buying?
Yes, for the lifetime of the script, at no extra cost. Updates arrive through the Cfx.re portal like the original purchase. There is no version you have to re-buy.
03How do I receive what I bought?
Instantly, to your Cfx.re account. Sign in with the same account at checkout and the asset appears at portal.cfx.re straight after payment. Assets are granted to the account, not to the email address.
04What if I cannot get it working?
Open a ticket in Discord. Every script also reports its own install state in the server console on boot — which framework it found, which integration points are present and which are missing — so in most cases the answer is already on your screen before you ask.
05When is support actually available?
This is a one-person studio, so we will not claim 24/7. Tickets are answered within one business day, usually much faster. If that is not good enough for your server, that is a fair reason not to buy — we would rather say so here than in a refund thread.
06Can I use one purchase on several servers?
A license covers one server. If you run a second one, buy a second license — or message us first, because for small communities running a test server alongside production we will usually just sort it out.
07Can I edit the code?
Configuration files, colours, locales and the UI stylesheet are open and yours to edit. The logic ships under escrow. Every integration point a normal server needs is exposed as an export or an event — if something you need is not, ask and it usually gets added.
08Payments, invoices and refunds?
Handled by Tebex, not by us — including refunds and missing assets. Their support is at tebex.io/support-customer. We have no control over asset grants, which is exactly why that link is here rather than buried in a ticket reply.