
24-layout character select
A multicharacter screen with 24 switchable layouts, from cinematic to data sheet, built on the same data underneath.
Scripts that hold up when players try to break them.
Tufan Studio writes custom FiveM resources in Lua by hand: gameplay systems, React NUI and the framework bridges that let one script run on Qbox, QBCore and ESX. The server decides what is allowed, never the client.

RegisterNetEvent('heist:claim', function() local src = source -- The client asks. The server decides. local ped = GetPlayerPed(src) local spot = GetEntityCoords(ped) if #(spot - VAULT) > 3.0 then return end if not HeistIsOpen(src) then return end PayReward(src)end)3
Frameworks plus standalone
24
Character select layouts
v1.12
Our own framework bridge
Tebex
Sold in our own store
Jobs, heists, crews, garages and whatever your server's roleplay needs, built around your rules and not a resold pack.
React and TypeScript menus, HUDs and character screens, kept light enough to stay smooth in the in-game browser.
Move a resource between Qbox, QBCore and ESX, or put one API in front of all three so it stops caring which one it runs on.
A clean Qbox or QBCore base on your VPS: database, ox stack and resources configured, with the install explained so you can run it.
These are systems we built and run on our own Qbox and QBCore development servers, plus the script we sell on Tebex.

A multicharacter screen with 24 switchable layouts, from cinematic to data sheet, built on the same data underneath.

Our standalone heist script, with cutscenes and server-side validation, on sale now in our Tebex store.
See it on TebexOne API across Qbox, QBCore and ESX for money, items, jobs, housing and more, so feature code never calls a framework directly.
Gang management, a Qbox garage and a spawn selector, each with its own React interface over validated server events.
Tell us your framework, your resources and what the script must do. We read how your server is set up first.
We check every export and native against the installed code, because guessing is how FiveM scripts break.
Every client event gets validated on the server, then tested on our Qbox and QBCore development servers.
You get the resource, the config and install notes, with support on Discord if something needs another look.
Qbox, QBCore and ESX, plus standalone scripts. If your server runs the ox stack, we build for it directly.
Often, if the code isn't locked by escrow and you have the right to change it. Send it over with the problem and we'll tell you what's realistic.
Lua and FiveM are the part we write by hand. It is the platform where a guessed API costs the most, so we read the source and test on our own servers.
The client is never trusted. Money, items and permissions are checked on the server, so a modded client can only ask, not decide.
It depends on the scope, so we quote per project. Use the form below with your budget range and we'll tell you what fits.