Work / FiveM
Gameplay systems for FiveM roleplay servers: casino games, property, a dealership, a shop, a robbery. Lua on the client and the server, NUI in HTML/CSS/JS, MariaDB behind it.
How it's built
Who can do what, what it costs and how it ends are decided on the server. The client only asks and shows; it never sends a price or a result.
One server handler per money movement
The logic of a feature is plain Lua with no framework and no networking inside, so it runs under a test runner on a laptop before it ever runs on a server.
Unit tests and simulators before the first in-game run
Every flow has a path for a disconnect, a resource stop or a crash: nothing is lost, nothing is paid twice, and a restart puts things back where they were.
Refunds, cooldowns and locks kept in SQL
A config for the server owner, SQL migrations that bring the backend up on first start, admin tools that work live, and a written test guide run on a dev server before release. The interfaces are checked in headless Chrome, since FiveM's browser is its own kind of Chromium.
Config · migrations · admin tools · test guide
Frameworks
Most of this work shipped on ESX; the rest on QBCore, Qbox or with no framework at all. A framework only covers a thin layer: money, jobs, player data and a few exports. The gameplay, the NUI, the SQL and the game API calls are the same whatever core a server runs.
Where it ran
All projects
Tenants and key holders buy furniture from a database-backed catalogue, in cash or coins, then place each piece with an in-game editor built on Three.js. Staff run the catalogue from an admin tab with no restart.
244 models in 13 categories · coin shop · admin tab, no restart
A Game Master runs the table as croupier while up to four players bet against one dealer hand. The dealer's hole card doesn't leave the server until the reveal.
4 players per round · 6-deck shoe · 125 + 144 test assertions
A candy slot in the Sweet Bonanza style, played against the house. Every spin is drawn, evaluated and paid on the server, and the maths is calibrated by simulation like a real machine.
~95% RTP · two 500,000-spin runs · 6×5 tumbling grid
Player-run Texas Hold'em. A Game Master opens a physical table, players sit down with in-game money, and the whole hand plays out server-side so it can't be cheated from the client.
8 seats + 16 spectators · 25 s turn timer · rising blinds
The solo game of the set. By the time you hit Spin the server has already drawn the number, checked every chip and settled the payout. The wheel on screen just catches up.
37 pockets · 2.70% house edge · 25,000 $ cap per spin
The biggest job so far. Agents place buildings on the map, attach apartments, then sell or rent them. Owners and tenants get keys, storage, a doorbell and control over who comes in.
5 interiors · 10 database tables · leases up to 365 days
The server's premium shop. Players buy coins through Tebex and spend them on vehicles, weapons, packs and loot boxes. Rebuilt after the original paid resource broke beyond repair.
React NUI · try before you buy · server-side drop draws
A safe in the back room of every player-owned convenience store, cracked on a 6-digit dial against a 5-minute timer. The combination never leaves the server, and the money comes out of the store company's real account.
6-digit dial · 5-minute timer · 5-hour cooldown kept in SQL
Three venues under one job and one company account. Pressing E takes you into a private showroom with the vehicle in front of you: orbit camera, live colour and plate, a timed test drive. No buy button: every sale is billed by an employee from a tablet.
201 models in 16 categories · 3 venues, 1 company · seller-billed sales
Smaller fixes
Players were using emotes to clip through locked doors. Emotes are now blocked near doors, with a per-door toggle so normal roleplay isn't hurt.
Full-time or long-term, not only one-off scripts. Based in Malta, so CET/CEST hours.