Frequently asked

Buying

How do I buy a resource?

Everything is sold through our Tebex store — use /products to browse, or the store link in #store-links. Checkout takes card or PayPal. Download links appear on your Tebex account page immediately after payment.

I bought a package but did not get my role

Run /link with the email you used on Tebex, then /myproducts to confirm. Roles are granted automatically within seconds of purchase once your account is linked. If it is still missing, open a Billing / Purchase ticket with your transaction id and staff will grant it manually.

Where are my download links?

On your Tebex account page, under your order — not in Discord. Your Discord roles unlock the customer channels and support; the files always come from Tebex.

What is the refund policy?

Digital goods are non-refundable once downloaded, except where required by law. That said, if a resource does not work as advertised, open a Billing / Purchase ticket — we would much rather fix it or refund it than leave you stuck with something broken.

Licensing

Can I use one purchase on multiple servers?

One purchase licenses one server. If you run a second community, that needs its own purchase. Development and test servers you personally own do not count against that — use them freely.

Can I edit the code?

Yes, for your own server. Configs are fully open and most logic is editable. What you cannot do is redistribute the result — edited or not. If your edit breaks something, say so when you open a ticket so staff are not debugging a version they have never seen.

Can I resell or share what I bought?

No. Sharing, reselling, leaking, or handing files to another server is an instant permanent ban and revokes access to every package on your account. See #rules for the full licensing terms.

Installation

How do I install a resource?

Drop the folder into your resources directory, add ensure <resource> to your server.cfg, then install every dependency listed in the resource README. Restart the server fully — a refresh alone will not pick up a newly added resource.

What dependencies do the scripts need?

Every resource lists its dependencies at the top of its README. Most need a recent QBCore or ESX build plus ox_lib. Version mismatches are the single most common cause of start-up errors — check these first.

Does this work with my framework?

Supported frameworks are listed on each product page and in its README. If yours is not listed, open a General Support ticket before buying and ask — a straight answer costs you nothing and saves us both a refund conversation.

How do I get updates?

Updates are free for life. Re-download from your Tebex account page, then replace the resource folder — keep your config.lua and diff it against the new one before overwriting. Update notes are posted in #changelog.

Support

How fast is support?

Usually 30–60 minutes during active hours, and always within 24 hours. Installation tickets move fastest when you include your server console output in the first message.

How do I report a bug properly?

Open a Bug Report ticket and fill in every field: what happens, exact steps to reproduce, and expected vs actual behaviour. Attach your console output and mention any edits you made. A reproducible bug usually gets fixed the same day.

Commissions

Do you take custom work?

Yes. Open a Custom Request ticket with a description, your framework, a budget range and your deadline. The first reply — feasibility and a ballpark — is free within 24–48 hours. Anything past a tweak then starts with a paid design phase. Run /commission for the full process.

What does custom work cost?

Commissions start at $80. Bands: tweaks $80–200, features $350–900, systems $1,200–3,500, suites quoted per milestone. Open-ended work is $65/hour. Anything past a tweak begins with a paid design phase — $450–700 for a feature, $900–1,800 for a system, from $2,500 for a suite — half of which credits against the build.

⚠️ System pricing is under review and a quote may exceed the band above — we are re-measuring the real cost of building to our standard. You always get the real number in writing, from your design, before paying anything.

How long does a commission take?

Tweaks 3–7 days, features 2–4 weeks, systems 6–12 weeks, suites 3–6 months. That is working time from your start date — builds run one at a time, so your slot depends on the queue and is confirmed in writing before you pay. Rush (+40%) buys an earlier start, not a shorter build.

Why is the design phase paid?

Because it is the work, not the sales pitch. It produces a real design document — research, decisions and their consequences, data model, API surface, milestones with test conditions, and what is explicitly out of scope. It is yours to keep, and half of it is credited against the build. If you walk away, you still own the document.

It is priced to what is being designed — a system design is real research, not a form.

What does "done" mean?

Every build ships with an automated test suite, debug and probe commands you keep, benchmarks measured against a budget stated in advance, and milestone gates reported honestly — including when one has not been met. Anything touching existing player data is dry-run by default with a rollback file. That is most of why a system takes weeks rather than days.

Do I own what you build for me?

You get the full source and a perpetual, irrevocable licence to use and modify it on any server you own — it never expires, and it transfers once if you sell your server. But we retain ownership: you are buying a licence, not the copyright, and unless you buy exclusivity (+100%) we may sell a derived version later. Your config, branding and anything unique to your server is never reused. Full terms in #commissions.