Answers before
you open a ticket.
Buying, installing, integrating, supporting. If it's not answered here, Discord is open — our tickets are run by our developers and by our AI assistant, Fiv3Devs Support.
Buying
01 Where do I buy your MLOs?
All purchases go through our official Tebex store at https://fiv3devs.tebex.io. Each product page on this site links directly to its Tebex listing.
02 What currencies and payment methods are accepted?
Prices are displayed in EUR (VAT-inclusive where applicable). Tebex handles the checkout and supports credit/debit cards, PayPal, and other regional payment methods depending on your country.
03 Do I need a CFX.RE account?
Yes. Tebex signs you in with your CFX.RE account at checkout, so a CFX.RE account is required to purchase. Your order history and download links live in your CFX portal at portal.cfx.re — not inside Tebex itself.
04 Can I get a refund?
Digital goods are non-refundable once downloaded, but we replace any file that fails to install and we actively work with buyers to resolve compatibility issues. Open a ticket in our Discord if you hit a problem.
05 Do prices include VAT?
Prices shown on product pages include VAT for EU customers. If you're ordering from outside the EU, or as a VAT-registered business, Tebex applies the correct treatment at checkout.
Installation
01 How do I install an MLO on my FiveM server?
After purchase, download the ZIP from your CFX portal at portal.cfx.re. Extract the folder into your server's resources/ directory, add the ensure line shown on each product page to your server.cfg, and restart the server. Detailed steps ship with every release.
02 Do I need the mapdata companion resource?
Many of our MLOs require fiv3devs_mapdata — but not all of them. Each product page lists whether the companion is needed. fiv3devs_mapdata is a lightweight shared dependency that coordinates map-level edits across our catalog, and it's free on the Tebex store.
03 Which FiveM artifact should I run?
Run a recent FiveM artifact. Every release is verified against the current artifact before shipping, and breaking-change updates are free for the lifetime of the product. FiveM Enhanced is not supported yet.
04 My map conflicts with another resource — what now?
Open a ticket on our Discord with the exact conflict symptom and the other resource's name. We publish compatibility notes for the common cases in each product's install README.
05 Can I use an MLO on multiple servers?
The Tebex license is per-server. One license covers your production server and its staging/dev instance at no extra cost; additional separate communities need their own licenses.
Compatibility
01 Do your MLOs work with ESX and QBCore?
Yes. Every MLO ships as a standalone FiveM resource with optional bridge configs for ESX Legacy and QBCore. Most releases also work on QBox without modification.
02 What target system do you use?
Interactions prefer ox_target when present, fall back to qb-target, and fall back again to a raycast prompt on servers without either. Your players don't have to install anything beyond what they already run.
03 Do you support VORP / Red Dead Redemption 2?
No. Our catalog targets GTA V + FiveM exclusively.
04 What about RedM?
Not yet. If that changes, it will be announced on Discord first.
Support
01 How do I get support after purchase?
Join our Discord at https://discord.gg/fiv3devs. Verified buyers get a role and can open tickets for install help, conflicts, or bug reports. Tickets are answered by the developers who ship the products, backed by our AI assistant Fiv3Devs Support — which also exposes self-fix commands and published compatibility patches for popular community resources.
02 What's your update policy?
Lifetime updates are included in the purchase price of every product. Artifact-breaking changes are patched as soon as we can validate the fix. Feature updates ship periodically — every product page carries its own full changelog so you can always see what's current.
03 Do you take custom commissions?
Not at this time.
04 I found a bug. What do I do?
Open a ticket on Discord with the product name, version, your framework, and a clear reproduction. If it's a real bug, it lands in the public known-issues list on that product's page with a planned-fix tag.
Still stuck?
Open a ticket on Discord — a developer or our AI assistant will get back to you.