The client has no authority
The NUI sends intent. The server re-resolves the player, the account, the permissions and the balance on every single call then decides.
One build, every framework. Silent Scripts resources detect ESX, QBCore, Qbox, ox_core or ND_Core at runtime — and run standalone when there is nothing to detect. Server-authoritative, documented, and boring in the way infrastructure should be.
Most released resources trust the client, ship one build per framework and leave the database to you. These do none of that.
The NUI sends intent. The server re-resolves the player, the account, the permissions and the balance on every single call then decides.
A bridge layer detects ESX, QBCore, Qbox, ox_core or ND_Core at runtime. No -esx and -qb forks drifting apart across releases.
Start the server once and the tables exist. Additive tables beside your framework’s own, so uninstalling leaves your data untouched. The reference .sql ships for review, not as a step you have to run.
Debits run as a conditional UPDATE … WHERE balance >= ?. Two concurrent withdrawals can never both succeed against the same funds.
Money, vehicles and staff actions all leave a row behind: searchable history in game, and Discord webhooks per event type with rate-limit back-off.
Exports, config descriptors, commands and limits are all written down, including the parts that are deliberately not implemented.
4 released resources that detect each other and link up when they are running together — each one still complete on its own. Six to start with:
Servers, communities and services we work with.
Installation, configuration, exports and the security model — everything you need before you decide whether a resource belongs on your server.