Home / Scripts / Interactions
LIVE — THIS IS THE ACTUAL UI, NOT A VIDEO
TRY IT Press a button. Everything you see runs the shipped UI.
0ROWS ON SCREEN
0SOURCES
0OVER THE CAP
0KEYS PARSED
THE PART NOBODY ELSE HAS

Drawing a prompt is easy.
Owning the one that is already there is not.

A server runs one target system, but its text prompts come from everywhere: ox_lib text UI in one script, qb-core DrawText in another. Two styles, two positions, in one minute. Interactions draws both on one rail — and it can be your target system too.

01

One line, and it returns a boolean

The inserted line ends in then return end. That return value is the whole design: true means we drew it and the original stops, false means we did not and the original draws exactly as it always did. A prompt is rendered once — by us or by them, never both.

02

Half-installed is a state we report

ox_lib needs two lines: show and hide. One without the other leaves a prompt stuck on screen, which looks exactly like our bug. The server reads the file and says “HALF installed, 1 of 2 lines found” instead of letting you find out from a player.

03

An update cannot break you quietly

When ox_lib updates and overwrites the file, the lines go with it. Every vendor has this problem. The difference is the console tells you on the next boot, and it tells never installed apart from was active before, missing now.

04

Ownership per resource

A row is keyed by the resource that registered it, automatically. Two scripts cannot overwrite each other, and when one stops, its rows go with it — without that script having to remember to clean up.

05

Your target or ours. Never both.

A server runs one target system. Native (the default): stop qb-target, ox_target or qtarget and restart the server — we answer their exports, so your scripts work without a single edit. Want to keep yours? Set Target mode to Intercept in Dispersia Hub and we only restyle its list.

06

Nothing runs when nothing happens

With the marker off — the default — nothing looks for targets until the key is pressed, then one search runs. Turn the marker on and the search wakes ten times a second; the drawing thread exists only while a marker is on screen.

HOW THIS IS NORMALLY DONE

Against a typical prompt replacement

Not a feature count. These are the four things that decide whether it is still working six months from now.

The usual wayInteractions
Getting your style in Replace the whole function with theirs Wrap the one call, original untouched
After a framework update Silently reverts — you find out from a player Console says so on the next boot
Half-applied patch Prompt sticks on screen, blamed on the script Reported by name as half installed
Two scripts, one panel Last one wins, the other disappears Each resource owns its own row
WHAT LANDS IN YOUR RESOURCES FOLDER

Open where it counts. Locked where it matters.

dispersia_interactions
select a file 
open — yours to edit escrow protected ships as built
One free dependency. Dispersia Hub (dispersia_lib) holds the settings for every Dispersia script. Nothing else to install first.
No config file. Server rules — target mode, reach, vehicle parts, tackle — are set in game in Dispersia Hub. Size, position and list length are set by each player with /interaction.
Open where it matters. fxmanifest.lua and the whole NUI folder — HTML, stylesheets, scripts — ship readable. Nothing hidden about how it is drawn.
Reversible. Remove the block and every original prompt comes back exactly as it was. Stopping the resource alone is enough to fall through.

It costs nothing to find out
whether it beats your target system.

Everything on this page runs the shipped UI. Stop your old target, start this one, restart the server — and if it does not earn its place, start the old one again.

READ THE GUIDE