Support & community
Installed, running, supported.
Install guidance, the FAQ server owners actually ask, licence terms in plain language, and a Discord where you can get a real answer instead of a canned reply.
Discord supportLifetime updatesCurrently 12 resourcesResponse target: 24h
Community
Pull up to
the Discord.
Support tickets, release announcements, previews of what's being built next, and a channel where other server owners compare notes. It's the fastest way to reach me.
01
Support hours
Ticket replies are usually inside a few hours; worst case within 24 hours. Installation help is text-based, voice calls by appointment.
02
What's covered
Scripted defects, configuration questions, integration problems with supported resources, and update migrations.
03
What isn't
Framework rewrites, third-party resource conflicts, and fixing code you modified after delivery. Those become custom work.
Before you open a ticket
- Which artifact version is your server on?
- Framework and version: QBCore, QBox or ESX?
- Resource name and version number from the product page
- The full error text, not a screenshot of half of it
- What you changed in the config, if anything
- Steps that reproduce it every time
Tickets with these six things get solved on the first reply. Tickets without them take three.
Check the changelog first →Install guide
Six steps to
a clean install.
Every paid resource follows the same pattern, so once you've installed one you can install them all.
01
Check requirements
Open the product page and read the requirements tab before you buy. Artifact version, database, ox_lib and your inventory resource all matter — the resource will not start without them.
02
Drop the folder in
Unzip the resource into your resources folder. Keep the folder name exactly as delivered — the SQL and config paths assume it.
03
Import the SQL
Import the included .sql file into the database your server uses. Run it once; the migrations are idempotent, so a second import will not wipe your data.
04
Order your server.cfg
Add `ensure <resource>` after your framework, oxmysql and ox_lib. Load order is the number one cause of 'it does nothing' tickets.
05
Configure, then test
Work through the config file top to bottom — economy, cooldowns, permissions, interactions. Restart and check the F8 console and your server console for errors before you let players in.
06
Need a hand?
Open a ticket in the Discord with your artifact version, framework, the resource version and the full error text. That is everything needed to reproduce it.
FAQ
Straight answers.
Licensing, refunds, frameworks, escrow, installs and support — the questions that come up most.
Every script ships for QBCore and QBox, most also support ESX, and tooling like the HUD pack and Jobs Creator run standalone with bridges. The compatibility labels on each product page are exact — if it doesn't say ESX, it isn't tested on ESX.
Checkout sends you to the Tebex store, which delivers the download instantly to your email and dashboard after payment. You get the resource files, SQL, documentation and a link to the changelog.
Yes, forever, on every purchase. Each product has a dated changelog entry for every version and, when a change affects existing installs, migration notes on the product page.
Both options exist. Escrow-protected builds keep the core logic locked while leaving the config, locales, UI and client-side integration files open. Open-source editions are available on request for most products and cost more.
Drop the folder in your resources directory, import the SQL file, add `ensure <resource>` to your server.cfg after your framework and ox_lib, then configure the config file. Every product page has the exact requirements list — check it before buying.
Open a ticket in the Discord with your server artifact version, framework and the error. Support is included with every purchase. Scripted bugs get fixed; misconfigurations get walked through.
Digital resources aren't refundable once the files are delivered, which is standard for this industry. If something doesn't work as described and we can't fix it, you get a replacement or credit — talk to me before opening a dispute, it always resolves faster.
That's half the business. Custom systems, server setups, optimisation, UI redesigns and full server builds. Use the quote builder on the custom work page and you'll get a written scope within 48 hours.
No. Every purchase is a single-server licence. You can edit it for your own server, but redistributing, reselling or leaking the files voids the licence and the update access that comes with it.
Yes — bundles of three or more get a discount, and full build clients get store credit. Ask in the Discord before you buy so I can send the right package.
Licence
In plain language.
You buy the right to run a resource on your server and edit it for your server. You do not buy the right to resell it, leak it, or pass it off as your own product.
Read the full licence →- One purchase = one FiveM server. You may run the resource on a single production server plus a development/staging copy.
- You may edit the files freely for your own server, including the UI, config and client-side integration code.
- You may not resell, sublicense, redistribute or leak the resource, or publish it inside a bundle or a paid server package for sale.
- Escrow-protected files may not be de-obfuscated, dumped or reverse-engineered.
- Updates, support and changelog access are tied to the account that bought the resource. Transfers are not automatic.
- Custom development work is licensed to your server on delivery; the code (or its patterns) may not be resold as a standalone product.
- Breaching the licence voids it and ends update and support access without refund.
Still stuck?
Tell me whatit's doing.
Open a ticket with your artifact version, framework and the error text. If it's a scripted bug, it gets fixed — that's what the support window is for.